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 and not waiting for
the 250 response, and the k2 server is thinking the DATA command is part of
the RCPT TO data. Regardless of whether that's proper behavior or not is
irrelevant to me right now. I need my mail server running. So what I need
to do is have courier NOT send the DATA command immediately after sending
the RCPT TO command and to wait for the 250 response then send it. My, most
likely incorrect, understanding, was that courier was doing this because the
k2 server advertised PIPELINING capabilities and courier was playing.
Clearly, that is not the case, which is why I sent my last email. I figured
some kind soul (namely you) would take pity on me and perhaps save me a few
hours so I didn't have to dig through the code to find out how to get it to
work the way I need it to.
The idiots at Go-Daddy can't begin to tell me why their server is rejecting
the email. For that matter, they don't even know the difference between an
MTA and a MUA or MDA. They say it's a configuration problem with my mail
server.
So I have you saying it's their problem and them saying it's courier's
problem, and I'm stuck in the middle.
No worries though. I got it working by forwarding the courier mail to a
postfix server running locally on a different port, then having the postfix
server use the k2 server as a relay. Not ideal, but at least it's working,
which is more than I had earlier. Now I have some breathing room. I'll get
it figured out.
I thank you for your time and all the effort you have put into courier.
On Thu, Mar 6, 2008 at 7:20 PM, Sam Varshavchik <[EMAIL PROTECTED]>
wrote:
> 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.
> >
> > I tweaked the esmtpclient.c file in courier/module.esmtp. Around line
> > 1282, I commented out these two lines:
> >
> > if (strcmp(hellobuf, "PIPELINING") == 0)
> > haspipelining=1;
> >
> > at around line 2008 i commented out the
> > if(!haspipelining)
> > and replaced it with a
> > if(1)
> >
> > then just to be sure I added this line down around line 1359
> > haspipelining=0;
> >
> > I then did a make distclean, reconfigured then did a make and make
> install.
> > However, courier is still pipelining the commands sent to the relay.
> >
> > Did I get the wrong place(s) to turn it off?
>
> What part of "this has absolutely nothing to do with pipelining, only the
> receiving mail server's administrator can tell you why its rejecting your
> mail" you do not understand?
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
