Thanks Sam, I was under the understanding that it is possible to exclude indiidual mailservers to be contacted without encryption option, but adding the suggested line to esmtproutes.
May this be a workaround for sending mail to their broken mailserver ? Brgds, Lars -----Original Message----- From: Sam Varshavchik [mailto:[EMAIL PROTECTED] Sent: 18 September 2004 20:09 To: [EMAIL PROTECTED] Subject: Re: [courier-users] Error sending to specific domaim Holmstr�m Lars writes: > 2) I assume the smtp status code (500) means the problem is on my side. > Correct or not ? No. It's their mail server that's broken. > 3) What is causing the problem ? Their broken mail server. Connected to mail.folkbildning.net. Escape character is '^]'. 220 mail.folkbildning.net FirstClass ESMTP Mail Server v8.0 ready EHLO default 250-mail.folkbildning.net Hello default (216.254.115.84), pleased to meet you 250-PIPELINING 250-AUTH=CRAM-MD5 LOGIN PLAIN 250-AUTH CRAM-MD5 LOGIN PLAIN 250-STARTTLS 250 8BITMIME Right there, in plain sight, their mail server claims support for the STARTTLS command. However: STARTTLS 500 Command not recognized: STARTTLS You can't possibly know what else could be screwed up with this broken mail server, so I wouldn't waste any more time on it, and write it off as a lost cause. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
