dovecot - Jun 2017 - +vnd.dovecot.duplicate for Bogofilter duplication shortcomings

Hello,

Sorry for a bit offtopic but it seems the bogofilter community is just 
as dead as dspam is.

I trying to switch from DSPAM to bogofilter on a server where if I turn 
bogofilter on I run into the following issue: Certain users have sender 
and recipient bcc maps setup in postfix.

This is for forwarding copy of an email to other address for example:

Incoming
lclude at company.com -> info at company.com

Outgoing
lclude at company.com -> info at company.com

This way whatever lcalude sends or receives a copy will be sent to the 
info mailbox. When bogofilter is enabled the bcc recipient (info) 
receives a dupe of every email.

Did anybody run into this?

virtual_destination_recipient_limit = 1
dspam_destination_recipient_limit = 1

was a working fix for me for the old system, however

bogofilter_destination_recipient_limit = 1

does not work in this case so if this issue is not possible to fix by 
configuration an alternate solution like making dovecot delete duplicate 
messages by message ID would be a viable option.

I have +vnd.dovecot.duplicate plugin enabled but it seems to be 
ineffective. Any other tips for a workaround?


Thank you.

Claude

Op 6/15/2017 om 12:19 PM schreef Luescher Claude:
> I have +vnd.dovecot.duplicate plugin enabled but it seems to be
> ineffective. Any other tips for a workaround?
>
Enabling that extension does nothing by itself. You need to add a
corresponding rule to your Sieve script.

Also, that is the deprecated name for that extension. It is explained
fully here:

https://tools.ietf.org/html/rfc7352

Regards,

Stephan.

Hello,

Yes but how to activate this for all users, not on a per user basis or 
without writing out thousands of sieve files to users directories.

Thank you.

On 2017-06-15 13:33, Stephan Bosch wrote:
> Op 6/15/2017 om 12:19 PM schreef Luescher Claude:
>> I have +vnd.dovecot.duplicate plugin enabled but it seems to be
>> ineffective. Any other tips for a workaround?
>> 
> 
> Enabling that extension does nothing by itself. You need to add a
> corresponding rule to your Sieve script.
> 
> Also, that is the deprecated name for that extension. It is explained
> fully here:
> 
> https://tools.ietf.org/html/rfc7352
> 
> Regards,
> 
> Stephan.