> I'd like to hear a valid reason you actually want these messages. And a
> serious example of when you might, not just quoting RFCs again.
I can't. But sorry: I really do not feel an urge to break RFCs in
the qpsmtpd core. After all we still do not know whats the reason
for that broken mails, and i don't believe we will see an increase
in that because i can't image how this can be exploited.
As long a empty messages are totally valid in regarding to RFC2821
i'm in no position to reject such messages addressed to my
customers. Regarding to german law this could even bring me into
trouble for supressing mail (which is the major reason why i feel
the urgent need for a per-user config, i'm only on a sure legal
ground if my customers agreed).
> Honestly, the RFCs for mail have gone out of the window in many
> places. We're under constant attack, and qpsmtpd was created
> specifically to ease the burden of those attacks. In a war you
> don't follow the rules.
The other attacks aren't handled in the qpsmtpd core either. The
task of the core is to implement a clean, RFC2821 compliant
implementation of SMTP, at least thats my feeling about it.
Every diversion from RFC2821 and every filter until now is
implemented as a plugin. I would like to have it stay that way.
But as always thats just my 2 EUR-Cents.
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
