Hi,
for some stuipid reason a customer sent out a message containing 1500 (!)
','-seperated entries in the bcc: header using AK-Mail with a qmail 1.03
smtp server for outgoing mail.
qmail-header(5) says
qmail-inject deletes any Bcc field
and RFC822 says there is no length limit on the header
On Tue, May 18, 1999 at 10:43:30AM +0200, Eike Kiltz wrote:
> Hi,
>
> for some stuipid reason a customer sent out a message containing 1500 (!)
> ','-seperated entries in the bcc: header using AK-Mail with a qmail 1.03
> smtp server for outgoing mail.
> qmail-header(5) says
>qmail-inject del
Chris Johnson <[EMAIL PROTECTED]> writes:
>
> When you say "with a qmail 1.03 smtp server for outgoing mail," do
> you mean that this message was injected with SMTP? If so, then
> qmail-inject never saw the message. qmail-smtpd doesn't look at the
> headers, and execs qmail-queue to queue the mes
s data stream is by definition the
> DATA part of the session. At that time all envelope sender and
> recipient specifications have been completed anyway.
Uh... I didn't say that at all, though I was intentionally vague when I said it
was the responsibility of "the software" on the remote
The only program in the qmail suite that looks at headers is
qmail-inject. If the message was submitted via SMTP, nothing in
qmail ever looked at those Bcc: headers. The submitting client
(AK-Mail?) *should* have stripped bcc fromt the headers and built
the correct envelope.
My guess is this: 1
Thomas Neumann wrote/schrieb/scribsit:
> Chris Johnson <[EMAIL PROTECTED]> writes:
> >
> > qmail-inject never saw the message. qmail-smtpd doesn't look at the
> > headers, and execs qmail-queue to queue the message as is. It's the
> > responsibility of the software on the remote end to strip the