-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 14 May 2014, Reindl Harald wrote:
Am 14.05.2014 16:56, schrieb Charles Marcus:
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...
wrong way - there are standards for not-to-repsond messages
- null sender
- Precedence: bulk
- Precedence: list
- Auto-Submitted: auto-generated
these are typically ignored
Then there are standards, implemented by one big software creator:
http://msdn.microsoft.com/en-us/library/ee219609%28v=EXCHG.80%29.aspx
I've seen messages with X-Auto-Response-Suppress only, but neither Auto-Submitted nor Precedence.
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBU3SJSXz1H7kL/d9rAQLAKAf/ZqaOLNEejUcG9nXXY1D7JHCZSmL/R/Ux ygy7L31PBQ5DdxniS6yJvuDyRkL+aum0yFy0GlusOgJhG331s+frw7tMHPZLPPru LqDRGVlJN54ot71f6gDPixJo42WrAt9tKAhXm6ySon3S32+rp2Z2GKGQ18aQ7TR9 B+2F+asHsyNIM5TiJvOkOxagmfI3sKdfE4hEr2O4uaSixGMOYqSVovQr4swFedSR mFRhfkEszTbpDMEegbaLBpMZ9UTAPNggzkq4LYjVE2qISrTiHE0uTIEXiw+2gKPL PYanoP4gnAbgrXkP5eNSB44FphotLNMf/0Ebz2Ea25SPQAOJ2o/MTQ== =I82K -----END PGP SIGNATURE-----