[Bug 3171] wishlist: Add flag to mark recipient as unique to allow duplicate delivery

Exim Bugzilla via Exim-dev <[email protected]>
Newsgroups gmane.mail.exim.devel
Message-ID <[email protected]/>
https://bugs.exim.org/show_bug.cgi?id=3171

--- Comment #2 from [email protected] ---
(In reply to Jeremy Harris from comment #1)
> I think this can be done with existing facilities:
> 
> 
> local_sender:
>         # copy the message to senders "Sent" folder
>         driver =                redirect
>         # this restricts to a "local" source
>         condition =             ${if def:authenticated_id}
> 
>         # this spots a suffix attempt
>         local_part_suffix =     -sent
>         local_part_suffix_optional
> 
>         data =                  ${if def:local_part_suffix \
>                 {:fail: Denied delivery to Sent folder} \
>                 {${quote_local_part:$local_part}@$domain, \
>                  
> ${quote_local_part:$sender_address_local_part}-sent@$domain} \
>                                  }
> 
>         # this avoids reprocessing either target
>         redirect_router =       local_users
>         
> local_users:
>         # this is specific to unix-login users
>         # replace with the existing local-user routing
>         check_local_users =     yes
> 
>         # handle both non- & suffixed variants
>         # use def:local_part_suffix to direct to the Sent folder
>         # $local_part will have the suffix stripped
>         local_part_suffix =     -sent
>         local_part_suffix_optional
> 
>         debug_print = T: \$local_part_suffix <$local_part_suffix>
> 
>         ...

Hi! I've thought about this approach, and there is still a minor downside: if I
send a mail to [email protected], it still wouldn't work. Adding this
flag would also make it simpler. I'm willing to submit a pull on this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.