Steve Shockley writes:
I posted this a few days ago, but I think it might have gotten lost in
the
shuffle. I'm still unable to get mail to send out from my queue to
servers
that are known to be up, and I'm at a loss on how to diagnose it.
You "know" that they're up? How do you know that?
One is a machine I admin, and another is used for this account. I can
telnet from the machine with Courier to port 25 on both, and the mx records
appear to be correct.
Since you're trying to help me actually debug it rather than just help me
figure out what piece is likely broken, you'll probably find it useful to
know that I'm trying to build a port/package for OpenBSD for Courier, and as
such it's not unlikely that some file isn't someplace Courier expects it to
be. I'm just trying to get a feel for how Courier processes the mail once
it gets into the queue, which'll probably tell me which process is returning
"Invalid argument" in the control file.
Sending mail via esmtp is handled by courieresmtp. It gets the message to
send, and its recipients, from courierd; looks up MX records for the
recipient domain; connects to the first available MX, and talks SMTP to it.
7 messages in net.sourceforge.lists.courier-users[courier-users] Re: Mail still stuck
