10 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: EHLO/HELO
FromSent OnAttachments
Holmström LarsJul 21, 2004 11:49 am 
Martijn LievaartJul 21, 2004 12:40 pm 
Sam VarshavchikJul 21, 2004 4:08 pm 
Holmström LarsJul 22, 2004 1:20 am 
Holmström LarsJul 22, 2004 12:06 pm 
Phillip HutchingsJul 22, 2004 1:17 pm 
Gordon MessmerJul 22, 2004 1:48 pm 
Sam VarshavchikJul 22, 2004 4:28 pm 
cour...@gmx.netJul 23, 2004 2:53 am 
Holmström LarsJul 24, 2004 12:41 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] Re: EHLO/HELOActions...
From:Holmström Lars (lars@essnet.se)
Date:Jul 24, 2004 12:41:39 pm
List:net.sourceforge.lists.courier-users

Well, the problem was a PIX that did a fixup on smtp, which actually block EHLO
messages. Thanks for your help. /Lars

________________________________

From: cour@gmx.net [mailto:cour@gmx.net] Sent: Fri 7/23/2004 11:53 AM To: cour@lists.sourceforge.net Subject: RE: [courier-users] Re: EHLO/HELO

--On Donnerstag, 22. Juli 2004 21:06 +0200 Holmström Lars <lars@essnet.se> wrote:

I am using the same (identical) client device for both accounts. This device (Qtek 2020) runs PocketPc 2003 and has no virusscanner capabilities.

Do you send the mail via ActiveSync ? Use a 'real' socket instead. Chat from mail sent with a IPAQ/WM2003:

Jul 23 11:45:01 <mail.info> smtp courieresmtpd: started,ip=[10...] Jul 23 11:45:01 <mail.info> smtp courieresmtpd: EHLO Inbox

^^^ Something munges this line, search and destroy the broken proxy, format c: may help too ;)

Jul 23 11:45:01 <mail.info> smtp courieresmtpd: STARTTLS Jul 23 11:45:02 <mail.info> smtp courieresmtpd: MAIL FROM:<roland@...> Jul 23 11:45:02 <mail.info> smtp courieresmtpd: RCPT TO:<support@...> Jul 23 11:45:02 <mail.info> smtp courieresmtpd: DATA

In order to isolate the problem I used the account that actually is working, and changed the SMTP servername and the login information. I can then see the error as before. This makes me believe the solution to the problem is to be found in the courier configuration.

There is nothing courier could do about.

Roland