| 1 |
Why does Cyrus set the MAIL FROM address of the sender of vacation responses to '<>'? |
| 2 |
------------------------------------------------------------------------------------- |
| 3 |
|
| 4 |
Because many of the Sieve features are autoresponders, Cyrus tries to be |
| 5 |
a good network citizen by adhering to the appropriate RFCs: |
| 6 |
|
| 7 |
From :rfc:`2821`:: |
| 8 |
|
| 9 |
This notification message must be from the SMTP server at the relay host |
| 10 |
or the host that first determines that delivery cannot be accomplished. |
| 11 |
Of course, SMTP servers MUST NOT send notification messages about |
| 12 |
problems transporting notification messages. One way to prevent loops in |
| 13 |
error reporting is to specify a null reverse-path in the MAIL command of |
| 14 |
a notification message. When such a message is transmitted the |
| 15 |
reverse-path MUST be set to null (see section 1.5.5 for additional |
| 16 |
discussion). |
| 17 |
|
| 18 |
|
| 19 |
A MAIL command with a null reverse-path appears as follows: |
| 20 |
|
| 21 |
``MAIL FROM:<>`` |
| 22 |
|
| 23 |
Also from draft-moore-auto-email-response-02.txt:: |
| 24 |
|
| 25 |
The primary purpose of the MAIL FROM address is to serve as the |
| 26 |
destination for delivery status messages and other automatic responses. |
| 27 |
Since in most cases it is not appropriate to respond to an automatic |
| 28 |
response, and the responder is not interested in delivery status |
| 29 |
messages, a MAIL FROM address of <> MAY be used for this purpose. |
| 30 |
|
| 31 |
This is of course slightly more applicable to reject than it is to |
| 32 |
vacation, but there isn't a very strong argument why they should be |
| 33 |
treated differently. |
| 34 |
|
| 35 |
Note that draft-moore-auto-email-response-02.txt also states:: |
| 36 |
|
| 37 |
A MAIL FROM address which is specifically chosen for the purpose of |
| 38 |
sending automatic responses, and which will not automatically respond to |
| 39 |
any message sent to it, MAY be used instead of <>. |
| 40 |
|
| 41 |
Therefore, it may be reasonable to have this be a configurable fixed |
| 42 |
address in the future. |
| 43 |
|
| 44 |
|