Phil Vandry wrote:
On Tue, Jul 01, 2008 at 11:54:46AM +0200, Jeroen Massar wrote:
The magic keyword: REJECT-ON-SMTP-DATA.
[snip description on how to reject during DATA phase]
Unfortunately there is also a side-effect, partially, one has to have
all inbound servers use this trick, and it
I think the problem that was being raised here was that past the DATA phase, if
one recipient is going to receive the message and another is going to reject
it, you have lost the ability to communicate this back to the sender (at least
without an NDR). Thus the problem of mails disappearing
one note about whether to filter at receiving SMTP server or later.
The receiving SMTP server is the one that has the conversation with the
sender.
Rejecting mail from servers having an un-backtranslatable IP is best
done right away by the receiving server right after the HELO command by
issuing
Jean-François Mezei wrote:
Blocking messages as early as possible also greatly reduces the load on
your system, disk storage requirements etc.
Rejecting during the SMTP dialog but before you signal that you've
accepted the DATA output also also pushes the responsibility for sending
a DSN to
Chris Owen [EMAIL PROTECTED] wrote
It is because, if someone reports (by telephone, IRC or IRL) that he
sent an email and I did not receive it, I regard as VERY IMPORTANT to
be able to check the spam folder (with a search tool, not by hand) and
go back to him saying No, we really did not
Chris Owen wrote:
The lack of a spam folder is one of the problems with such a solution.
Having a middle ground quarantine is actually quite nice.
However, the biggest problem is these solutions are global in nature.
We let individual customers considerable control over the process. They
6 matches
Mail list logo
