El vie, 05-12-2003 a las 21:37, Jeffrey Stedfast escribi�: > On Fri, 2003-12-05 at 21:49, Oscar A. Valdez wrote: > > I am running Evolution 1.4.5 > > > > My default outgoing mail is configured to use login authentication against my > > ISP's SMTP server (iPlanet Messaging Server). > > > > Mails I write contain this header: > > > > X-Evolution-Transport: smtp://myusername;[EMAIL PROTECTED] > > > > When I try to send mail, this is the dialogue between Evolution and the SMTP > > server: > > sending : EHLO [10.5.193.214] > > received: 250-mta01 > > received: 250-8BITMIME > > This server supports 8bit MIME > > received: 250-PIPELINING > > received: 250-DSN > > received: 250-XDFLG > > received: 250-ENHANCEDSTATUSCODES > > This server supports enhanced status codes > > received: 250-EXPN > > received: 250-HELP > > received: 250-SAML > > received: 250-SEND > > received: 250-SOML > > received: 250-TURN > > received: 250-XADR > > received: 250-XSTA > > received: 250-XCIR > > received: 250-XGEN > > received: 250-XLOOP 71EA245D54E21694ACEB8538CA77D3B7 > > received: 250-AUTH LOGIN PLAIN > > received: 250-AUTH=LOGIN > > received: 250-ETRN > > received: 250-RELAY > > received: 250 SIZE 0 > > sending : AUTH LOGIN <<mime-encoded-username>> > > received: 334 UGFzc3dvcmQ6 > > sending : <<mime-encoded-password>> > > received: 235 2.7.0 LOGIN authentication successful. > > sending : EHLO [10.5.193.214] > > received: 250-mta01 > > received: 250-8BITMIME > > This server supports 8bit MIME > > received: 250-PIPELINING > > received: 250-DSN > > received: 250-XDFLG > > received: 250-ENHANCEDSTATUSCODES > > This server supports enhanced status codes > > received: 250-EXPN > > received: 250-HELP > > received: 250-SAML > > received: 250-SEND > > received: 250-SOML > > received: 250-TURN > > received: 250-XADR > > received: 250-XSTA > > received: 250-XCIR > > received: 250-XGEN > > received: 250-XLOOP 71EA245D54E21694ACEB8538CA77D3B7 > > received: 250-AUTH LOGIN PLAIN > > received: 250-AUTH=LOGIN > > received: 250-ETRN > > received: 250-RELAY > > received: 250 SIZE 0 > > sending : MAIL FROM:<[EMAIL PROTECTED]> > > received: 250 2.5.0 Address Ok. > > sending : RCPT TO:<[EMAIL PROTECTED]> > > received: 550 5.7.1 Relaying not allowed: [EMAIL PROTECTED] > > sending : QUIT > > received: 221 2.3.0 Bye received. Goodbye. > > > > After getting the response to the first EHLO, Evolution authenticates > > succesfully, then sends a second EHLO, after which it doesn't authenticate, and > > the messages get bounced. > > > > Any clues on how to solve this will be greatly appreciated. > > it seems that your SMTP server mis-implements the SMTP AUTH extension. > According to the specification, after a client successfully > authenticates, it MUST re-EHLO if it plans to use any of the extensions > (which we do). > > You should complain to your ISP to get their software fixed. >
Thank you for your response. I believe you are referring to RFC 2554, #4: "Restrictions: After an AUTH command has successfully completed, no more AUTH commands may be issued in the same session. After a successful AUTH command completes, a server MUST reject any further AUTH commands with a 503 reply." "...The client SHOULD send an EHLO command as the first command after a successful SASL negotiation which results in the enabling of a security layer." I will inform my ISP about this situation, but I think most of the burden on how to fix it will fall on me (after all, 99.999% of their customers must be using Outlook Express). Do you have any pointers on how they should reconfigure their server? -- Oscar A. Valdez _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
