On Tue, 20 Nov 2007, Gerrit E.G. Hobbelt wrote: > Hi, > > There's still a bug lurking in the code, but now for a fault situation > only fortunately, far as I can tell. > > How to reproduce: > > - use Outlook Express > - create account > - FORGET to check the checkmark 'Outgoing (SMTP) server requires > authentication' > - start XMAIL server and have SMTP-after-POP# ENabled (by default) > - send email from OE to XMAIL > > ==> OE will receive a non-compliant error line from XMAIL reading > "(null)" ( oops! :-( ) instead of "nnn yada yada" where "nnn" is a > 3-digit number conform SMTP RFC. > > Why? Because OE _first_ does the SMTP access, THEN does a POP3, so > SMTP-after-POP3 MUST fail as this is really a client setup failure which > LOOKS LIKE a possible SMTP-after-POP3 attempt. > > > As the "(null)" already suggests, this failure is due to the fact that > an error string has not been initialized where expected. And indeed it > hasn't: see the new > > pszSMTPError = SysStrDup(...) > > code lines. > > > Fix diff shown below. Basically the fix mimics the behaviour of other > similar sections of the code, while a '504 internal server error' > (number should be checked, I pulled that one out of my hat at 01:00 AM ! > ) is reported when the 'uninitialized error string' recurs ever again.
Ok, you made me waste *A LOT* of time, for a totally wrong analysis, probably linked with your own compiler of XMail code additions. The pszSMTPError string is printed only after a failure of one of SMTPCheckReturnPath() and SMTPCheckForwardPath(), and both these functions sets pszSMTPError in every error path out of them. This makes me think (pretty clearly) that you modified the XMail source, and the problems you're seeing comes from your changes. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
