On Fri, 07 Sep 2001, Alex Pennace wrote:
> Like it all not, qmail needs at least a "stub" hostname it can
> consider local.
The names are all there, but qmail is not supposed to do local delivery
in my setup. There's nothing that prevents this configuration. There's
nothing that makes this setup strange.
> > See my other mails for more information, particularly is qmail-send
> > trusting qmail-qmqpd to inject proper mail, but qmail-qmqpd can inject
> > mail without the terminating LF. qmail-inject does not. qmail-smtpd
> > cannot.
>
> qmail-send only trusts qmail-queue, which is one way to check for
> proper mail.
qmail-queue is invoked by qmail-qmqpd, so qmail-send eventually trusts
qmail-qmqpd. qmail-queue does not enforce mail formats (apart from
prepending a Received: line) and it's not the proper place to do so
either.
qmail-qmqpd is supposed to transfer binary data, so it's not the place
to enforce formats.
Two places remain: qmail-send, qmail-remote. qmail-remote is an SMTP
interface, it has to choose from: modify the mail or reject if it can't
be sent. Dan chose to not modify the mail.
One place remains: qmail-send. QSBMF, that qmail-send implements,
predates QMQP, and from the choices we have, it's the only place that
can help us out, generate bounce messages in a format that can always be
sent through SMTP. At least the 2bounce should be SMTP clean, even if
that means adding LF and replacing 0x00-0x08,0x0b,0x0c,0x0e-0x1f and
high-bit stuff by ? or _ (like the logs do).
Until that is done, qmail's binary-clean interface is not worth much
because users will still need to use 7bit/SMTP clean mail if they value
non-delivery notifications.
--
Matthias Andree
Outlook (Express) users: press Ctrl+F3 for the full source code of this post.
begin dont_click_this_virus.exe
end
