Hi Sam,

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.

Sam Kuper wrote: