Peer,
> If reinjection of mail fails, Amavis will send a DSN back to the sender to
> notify him about this failure.
>
> But if D_REJECT is active this leads to *2* DSN back to the user: One DSN
> from the sending MTA (because Amavis blocks that mail to the feeding
> MTA), second DSN from Amavis hi
Peer Heinlein wrote:
> Am Donnerstag 09 Juli 2009 schrieb Thomas Gelf:
>
>> As far as I remember all docs I used long time ago to set up my first
>> Amavis boxes clearly state that it is absolutely necessary to avoid
>> REJECTs by the postfix instance Amavis is reinjecting the mail to. It
>> shoul
Am Donnerstag 09 Juli 2009 schrieb Thomas Gelf:
> As far as I remember all docs I used long time ago to set up my first
> Amavis boxes clearly state that it is absolutely necessary to avoid
> REJECTs by the postfix instance Amavis is reinjecting the mail to. It
> should NOT do any checks that did
Hi Peer,
I followed the related thread on your German Postfix ML - and while
I agree with most of your mail (I'm pretty sure Mark will give a more
detailed answer here ;-)) in this special case there is IMO also the
user (who configured the system) to blame for his issues, even if he
ran into a re
If reinjection of mail fails, Amavis will send a DSN back to the sender to
notify him about this failure.
But if D_REJECT is active this leads to *2* DSN back to the user: One DSN
from the sending MTA (because Amavis blocks that mail to the feeding
MTA), second DSN from Amavis himself.
In my
