Re: [courier-users] can't get esmtproutes to work

2008-03-07 Thread Gordon Messmer
Bill Long wrote: I know why it's rejecting the mail. It's because courier is sending the DATA command immediately after sending the RCPT TO command and not waiting for the 250 response, and the k2 server is thinking the DATA command is part of the RCPT TO data. That seems unlikely, since

Re: [courier-users] can't get esmtproutes to work

2008-03-07 Thread Bernd Wurst
Hi. On Friday 07 March 2008, Bill Long wrote: It's because courier is sending the DATA command immediately after sending the RCPT TO command and not waiting for the 250 response If that is true, why does the destination server announce the PIPELINING feature? To behave like courier does is

Re: [courier-users] can't get esmtproutes to work

2008-03-07 Thread Sam Varshavchik
Bill Long writes: It doesn't matter if I understand it or not, Sam. What matters is that I need a mail server running and pointing a finger to and fro isn't going to make that happen. I know why it's rejecting the mail. It's because courier is sending the DATA command immediately after

Re: [courier-users] can't get esmtproutes to work

2008-03-07 Thread Bill Long
You are correct Sam. I was in error. It doesn't have to do with the DATA being followed immediately by the RCPT TO. Additionally, the k2 server appears to deal with pipelining just fine. (as seen from the postfix session). Here is a dump of 5 mail sessions. 1 from courier sending mail to

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
Sam, I think there might be a small problem with courier. I'm only guessing here. Let me put out my information. Maybe you can make more sense of it since you are so much more familiar with the code and operations of courier than I am. First, I tried to manually connect and send an email to the

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Gordon Messmer
Bill Long wrote: CentOS root /root telnet k2smtpout.secureserver.net http://k2smtpout.secureserver.net 25 ... Using the capture file, I opened it up in ethereal and did a follow stream. here's the output of that. 220 k2smtpout02-01.prod.mesa1.secureservEHLO mail.longboys.net

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
BODY=7BI250 Sender accepted. RCPT TO:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] DATA 553 Sorry, that domain isn't in my list 503 You must send RCPT TO: first Comparing the output of ethereal and your telnet log, I can see two things: 1: the host you're reaching is different in each

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
On Thu, Mar 6, 2008 at 2:16 PM, Bill Long [EMAIL PROTECTED] wrote: BODY=7BI250 Sender accepted. RCPT TO:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] DATA 553 Sorry, that domain isn't in my list 503 You must send RCPT TO: first Comparing the output of ethereal and your telnet log, I

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Gordon Messmer
Bill Long wrote: 2: your dump file is garbage. Those packets are definitely truncated and possibly out of order. You should capture the stream with ethereal/wireshark if possible. If not, try: tcpdump -s0 -w/tmp/smtp.dump host k2smtpout.secureserver.net

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Sam Varshavchik
Bill Long writes:  Here's the dump: 220 URL:http://k2smtpout03-02.prod.mesa1.secureserver.netk2smtpout03-02.prod. mesa1.secureserver.net ESMTP EHLO URL:http://mail.longboys.netmail.longboys.net URL:http://250-k2smtpout03-02.prod.mesa1.secureserver.net250-k2smtpout03-

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
Gotcha. That's what I'm looking for. Thanks much. This was instructive. :) Thanks Sam (and Gordon) for your help and feedback. On Thu, Mar 6, 2008 at 4:25 PM, Sam Varshavchik [EMAIL PROTECTED] wrote: Bill Long writes: Here's the dump: 220

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
Okay. one more quick question, if you don't mind. In order to get up and running until GoDaddy get's back to me, I want to turn of the pipelining in couriers esmtp client. Since the k2 relay is going to be my only outbound connection for now, I figure that's okay for now. I tweaked the

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Sam Varshavchik
Bill Long writes: Okay. one more quick question, if you don't mind. In order to get up and running until GoDaddy get's back to me, I want to turn of the pipelining in couriers esmtp client. Since the k2 relay is going to be my only outbound connection for now, I figure that's okay for now.

Re: [courier-users] can't get esmtproutes to work

2008-03-06 Thread Bill Long
It doesn't matter if I understand it or not, Sam. What matters is that I need a mail server running and pointing a finger to and fro isn't going to make that happen. I know why it's rejecting the mail. It's because courier is sending the DATA command immediately after sending the RCPT TO command

[courier-users] can't get esmtproutes to work

2008-03-05 Thread Bill Long
Hi all, I'm having a bit of a problem getting my courier to use a relayhost/smart relay. I need all mails not delivered locally to be forwarded on to a different smtp server. the to smtp server doesn't have an MX record and I have no control over setting it. I'm using Courier 53.3 I've poured

Re: [courier-users] can't get esmtproutes to work

2008-03-05 Thread eculp
Quoting Bill Long [EMAIL PROTECTED]: Hi all, I'm having a bit of a problem getting my courier to use a relayhost/smart relay. I need all mails not delivered locally to be forwarded on to a different smtp server. the to smtp server doesn't have an MX record and I have no control over

Re: [courier-users] can't get esmtproutes to work

2008-03-05 Thread Sam Varshavchik
Bill Long writes: When I try to send emails, I get the following error in my maillog Mar  5 13:43:04 CentOS courieresmtp: id=002E6F36.47CF0337.64F4,from=EMAIL PROTECTED,addr=EMAIL PROTECTED: 553 Sorry, that domain isn't in my list of allowed rcpthosts. Mar  5 13:43:04 CentOS courieresmtp: