Re: [exim-dev] [Bug 938] 'smtp' transport does not assert '\…

Top Page
Delete this message
Reply to this message
Author: Jakob Hirsch
Date:  
To: exim-dev
Subject: Re: [exim-dev] [Bug 938] 'smtp' transport does not assert '\n' before sending '.' in DATA transmission
J R Binks, 2009-12-22 11:55:

my few cents on this:

- on MailScanner: If you fiddle with some applications data, take care
to not break something. This is clearly a MS bug, so the MS people are
the ones that have to fix this.
And no, this has nothing to do with holiness. You cannot mess around
with other people's stuff, break it and expect them to fix it.

(I really wonder why MS has to fiddle with the queue at all. Aren't
there better ways to receive mail, like using a standard interface, e.g.
smtp or lmtp. And AFAIK, most MTAs offer a interface, e.g. milter or
Exim's local scan API.)

- on Exim: If there is an easy way to do sanity checking, we should
probably do it. And if we detect that something is broken, we should at
least warn about it. I would even tend to freeze the message, but that's
not possible in this case, unless do some extra checking before handing
the message over to smtp_out.