14 May
2014
14 May
'14
5:56 p.m.
On 5/14/2014 10:44 AM, Steffen Kaiser <skdovecot@smail.inf.fh-brs.de> wrote:
Yep, those using different <> null senders should be aware, that there envelope sender rewritings, such as BATV and SRS0, that make the address unique each time by adding hashed timestamps or something like that. Those rewritings undermine the vacation database. I hope that those implementations generate an unique address per day and not per message.
Best would be if there was a way to code sieve such that it could ignore the BATV/SRS0 junk, as well as plussed addresses...
Is there enough rhyme/reason to these schemes that would make that feasible?
--
Best regards,
Charles