Thanks, I hadn't seen that link before. I'm sorry, I meant
that the 256 was the status code I see in my smtpd log.
But, in searching the archives, I saw reference to people
saying the bare LF generates a 451 and not a 553. I can't
verify that since I don't have a mailer to try it with
but it seems that you'd never want the 451 in this case
because obviously it will be the same mailer that will
retry each time and it will continue to be broken for each
try...
Is the bare LF a function of the MTA or the user agent?
I found out that one of the systems that is hitting me and
getting the exit status of 256 is, of course, a server
running the Microsoft SMTP service. (Not Exchange) Is
it their SMTP service that is broken or the user agent?
Thanks,
Dave
-----Original Message-----
From: Adam McKenna [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 26, 2000 8:34 PM
To: '[EMAIL PROTECTED]'
Subject: Re: What to do about these barelinefeeds?
qmail doesn't return an error code of 256 for the bare lf problem, it
returns
553.
> 2) The important question now is, what kind of error
> does the user get when their mail server finally
> gives up? Does it look like the mail was just
> undeliverable? I know qmail issues the error code
> that causes the mail server to try again. After that
> time on the remote server expires, I'm worried that
> users who may be mailing someone at a domain I
> host will be getting an error message that makes it
> look like a problem with my mail server, pissing my
> customers off at me.
Did you actually read any of the online documentation about this, including
but not limited to http://cr.yp.to/docs/smtplf.html, the FAQ and relevant
RFC's?
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> | "No matter how much it changes,
http://flounder.net/publickey.html | technology's just a bunch of wires
GPG: 17A4 11F7 5E7E C2E7 08AA | connected to a bunch of other
wires."
38B0 05D0 8BF7 2C6D 110A | Joe Rogan, _NewsRadio_
8:31pm up 138 days, 17:47, 9 users, load average: 0.07, 0.07, 0.02
