What about have the feature configurable:
onExpires=off // default
onExpires=drop // discard expired mail without notice (my patch)
onExpires=bounce // or other actions??
...
i think only the 'off' and 'drop' actions make sense!
If we 'bounce' an expired mail, other MTAs would/could drop it (as it is
expired),
so the behavior would be unexpected - thus remains the 'drop' action to
be the only
useful.
regards,
Marcel
Stefano Bagnara wrote:
Marcel Ruff wrote:
Hi,
is it possible to add the "Expires" patch (according to
http://www.faqs.org/rfcs/rfc2156.html)
to the new james release 2.3?
(I had posted it already on 2006-02-21)
As you can read from the rfc you linked:
--------------
Expiry Date Indication
Supported as new RFC 822 header (Expires:). In general, no
automatic action can be expected.
-----------------
No automatic action can be expected.
Furthermore the proposed patch act like it delivered the message
without returning bounces or anything else.
So, before deciding wether to include this or not I would like to at
least know what other mail servers support this header and how do they
handle the expiration.
Stefano
PS: I already added an issue and comments for this request:
http://issues.apache.org/jira/browse/JAMES-444
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
