Re: [9fans] smtpd inserting nulls

Re: [9fans] smtpd inserting nulls

[erik quanstrom]

On Mon Oct  6 20:47:42 EDT 2008, rminnich@gmail.com wrote:
> This is a great thing. I've been assuming that the rest of the world
> sent around bogus email, it never occured to me that the mta would be
> blowing it.
>
> Thanks for this, it's a big help
>
> ron

you're welcome!  that bug had been driving me bats for
about 15 months.  (that'll be a lesson to you, boys and girls:
never let 'em know you know anything about smtp.  that
goes double for imap.)

btw, the nupas stuff is coming along.  i have
a couple users with ~2500 messages in their inboxes.
now if i could just teach them where the delete button is.

you may be interested in the nupas version of smtpd.
i've added some spam control that's been pretty effective.
the -E option demands a valid ehlo domain *or* authentication.
this is good for imap users who can auth but feed us garbage
ehlo strings.

☺

- erik

Re: [9fans] smtpd inserting nulls

[ron minnich]

On Mon, Oct 6, 2008 at 12:49 PM, erik quanstrom <quanstro@coraid.com> wrote:
> i've been having a problem with nulls popping up
> in the middle of emails for some time.  normally,
> this isn't something one would notice but imap4d
> makes nulls in email extra annoying by sending the
> client 4 reformattings of the same bogus message.
>
> i never did catch it red handed, but it finally be
> came obvious on (not exactly the first) inspection.
> the dot destuffing code didn't reduce the length
> of the line to account for the elided dot and thus
> added a null at the end of lines starting with a dot.
> (but only after the first 16k of the message.)
>
> fun times!
>
> because i was there, i also added protection against
> nulls in the actual data.
>
> there's a patch on sources.
>


This is a great thing. I've been assuming that the rest of the world
sent around bogus email, it never occured to me that the mta would be
blowing it.

Thanks for this, it's a big help

ron

[9fans] smtpd inserting nulls

[erik quanstrom]

i've been having a problem with nulls popping up
in the middle of emails for some time.  normally,
this isn't something one would notice but imap4d
makes nulls in email extra annoying by sending the
client 4 reformattings of the same bogus message.

i never did catch it red handed, but it finally be
came obvious on (not exactly the first) inspection.
the dot destuffing code didn't reduce the length
of the line to account for the elided dot and thus
added a null at the end of lines starting with a dot.
(but only after the first 16k of the message.)

fun times!

because i was there, i also added protection against
nulls in the actual data.

there's a patch on sources.

- erik