On Thu, Oct 26, 2000 at 11:31:01PM -0400, Hubbard, David wrote:
> 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...
You're right, I grepped my source for it but I forgot that I had modified the
source to produce a permanent error code instead of a temporary one to avoid
the exact problem you are describing (M$ S(hitty)MTP service hammering my
server.)
> 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?
It's the MTA.
--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_
12:18am up 138 days, 21:33, 9 users, load average: 0.02, 0.01, 0.00
