-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 14 May 2014, Charles Marcus wrote:
On 5/13/2014 3:02 PM, Stephan Bosch <step...@rename-it.nl> wrote:
If you know what you are doing (think twice about that!), you can override
this behavior using the sieve_vacation_send_from_recipient setting (if your
Pigeonhole is recent enough):
http://wiki2.dovecot.org/Pigeonhole/Sieve/Extensions/Vacation#Configuration
Regards, Stephan.
Just be sure you understand why...
I recommend you read the pertinent RFC which explains the reasoning as to why
the null sender is recommended, and if you are going to use another/real
address, only use one that will never auto-respond to *anything*:
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. :-)
http://tools.ietf.org/html/rfc3834#section-3.3
Specifically:
The primary purpose of the MAIL FROM address is to serve as the
destination for delivery status messages and other automatic
responses. Since in most cases it is not appropriate to respond to
an automatic response, and the responder is not interested in
delivery status messages, a MAIL FROM address of <> MAY be used for
this purpose. A MAIL FROM address which is specifically chosen for
the purpose of sending automatic responses, and which will not
automatically respond to any message sent to it, MAY be used instead
of <>.
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBU3OBT3z1H7kL/d9rAQKGhggAxXOPt5UGUeSiZk/mc+2CvcKkmO5oIrDD
Z/mTligp6LOzJC3WnkXgra+mBwBlr/6WBE0Qze/7/z6arbG/3kQLaRhGexLJ630J
Z/f1uDNh6ntziw5yiix9QiW241UaDf9kVWrhKjPSchiLMF8GS874jSW7Ox/siMOu
+QcFIiTGXeFdUmqNb6F0rDKJLdGShLULh+EfOh26JRMkPiPpdzWXdgIHA8xqB5iN
pvD23uB/Hm+gSrj6hwFZjGBI0jxqyIdo3prtqO7Iw6zs7dvvGR45GmVAiVe1KsSl
mDNmxXpTtLPO4g3AlgVg98VinTC8BGACStS5zQvvhnwHjqd/0CgtQA==
=e7tc
-----END PGP SIGNATURE-----
