|Sam Kuper||Oct 25, 2008 4:59 pm|
|Jérôme Blion||Oct 25, 2008 5:19 pm|
|Sam Kuper||Oct 25, 2008 6:17 pm|
|Sam Kuper||Oct 25, 2008 7:08 pm|
|Sam Kuper||Oct 26, 2008 5:14 am|
|Sam Varshavchik||Oct 26, 2008 6:58 am|
|Tim Lyth||Oct 26, 2008 7:35 am|
|Sam Kuper||Oct 26, 2008 9:04 am|
|Sam Kuper||Oct 26, 2008 9:18 am|
|Gordon Messmer||Oct 26, 2008 11:24 am|
|Subject:||Re: [courier-users] Difficulty sending mail via Courier from Mutt on Ubuntu 8.04.1|
|From:||Tim Lyth (tc...@tcl.homedns.org)|
|Date:||Oct 26, 2008 7:35:53 am|
I most certainly don't mind - I thought I'd changed the To: field to be the list - whoops.
Yes, the 504 line is the significant line in all that output - I think your server doesn't know who it is.
What do (assuming config files in same location on yours as they are on mine) /etc/courier/defaultdomain and /etc/courier/me have in them? /etc/courier/defaultdomain is what is added after the @ if nothing is there already. /etc/courier/me identifies to courier who is it - I think this is used in the SMTP HELO/EHLO greeting and response. If /etc/courier/me doesn't exist, then I think courier reverts to the output from `hostname`. If nothing gives courier a FDQN then you'll get that error.
On my system, /etc/courier/me has "tcl.homedns.org" as that's my domain, output from `hostname` is "five-hundred.tcl.homedns.org" (LAN name appended in front of the domain). When I telnet in to my email server with /etc/courier/me present, I get "220 tcl.homedns.org ESMTP" as the first message from courier. When I move /etc/courier/me out of the way (eg: mv me ~ ), I get "220 five-hundred.tcl.homedns.org ESMTP".
In your instance, I'd set /etc/courier/me (or equivalent) to be the domain name.
The other possibility is the email address that it appears to be coming from - sam@shelleysoldbox - that's not a valid email address as it's not an FQDN after the @. Might need to set up some internal DNS system (or /etc/hosts if you've got a small number of systems) to resolve LAN IP's in to FQDNs - this will mean that your email client (as well as courier) will have an FQDN for every system it will speak to.
HTH again, Tim Lyth
Sam Kuper wrote:
I hope you don't mind that I've taken the liberty of copying your reply back to the list.
2008/10/26 Tim Lyth:
You should also have /var/log/mail.log and maybe /var/log/mail.err. `tail -n50` those - that'll at least show you a bit more history of what's been going with email. AND that might give the clue needed - especially if you have a timestamp for when the email was sent via mutt.
id=00027AE8.4904593F.000031D0,from=<sam@shelleysoldbox>,addr=<sam....@uclmail.net>: 504 Need Fully Qualified Address Oct 26 11:49:21 shelleysoldbox courieresmtp: id=00027AE8.4904593F.000031D0,from=<sam@shelleysoldbox>,addr=<sam....@uclmail.net>,status: failure <snip>
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users