[Spambayes] Re: SMTP Errors using Eudora

Meyer, Tony T.A.Meyer at massey.ac.nz
Fri Aug 29 14:28:22 EDT 2003


> That did get rid of the extra space, but not 
> the problem. 

That doesn't bode well for the cvs version.  (Although these are fixes
that I should be making anyway; it's not just for this problem).

> 1. The "500 Unrecognized command message" does not seem to 
> come from a Python module

It's an error from the smtp server.  If you telnet to your smtp server
and simply hit return, you'll get the same message.  (Mine gives
'Unrecognised command, ""', but it'll always be something similar).

> 4. Norton probably doesn't know about SMTP on any port except 
> 25, therefore is most likely sitting between smtpproxy and the server.

I really don't know anything about what Norton is doing.  I wonder if
it's actually sitting between the smtpproxy and the server, or if it's
integrated into Eudora (through the plug-in architecture).  Either way,
at least in theory ;), it shouldn't make any difference, since our
smtpproxy is (or should be) passing on the command verbatim.  If you
telnet to the smtp server (i.e. bypass Eudora), then everything should
still work - this is all the proxy does, really.

> 6. The other difference between you and I (at least as far as this is 
> concerned <wink>) is I'm using Eudora 5.1 and you're on 5.2. 
> I'm not sure what version of Python you're using. I have 2.2.3.

I have both 2.3, which I use by default, and 2.2.3; I've tried both.

> Given all the above, the actual error response is probably 
> coming from Norton, and not the SMTP server. If 1.12 doesn't fix it,
> how can I dump smtpproxy's port 25 data? I tried some prints in
> asynchat and asyncore, but I'm exactly sure which data I was looking
at.

Well, the print statements print everything that is sent to port 25 by
Eudora, and sent from the proxy to the smtp server.  I'm not sure how to
get hold of the data coming back in the other direction, or how easy it
would be, but I don't think that would necessarily tell us anything.

One other thing is maybe this is a '\r\n' or '\n' issue.  SMTP data
should be terminated with '\r\n', not just '\n' (or '\r'), and that's
what we do on sending.  Maybe Eudora is only sending '\n', though, and
that's what your smtp server expects.  This seems unlikely, though, and
I think it would cause problems earlier on than QUIT.

(I'm not sure what to do if 1.12 doesn't work...hopefully I'll come up
with something!).

=Tony Meyer



More information about the Spambayes mailing list