Gary Kline wrote:
On Friday 25 January 2008 17:12:35 you wrote:
On Jan 25, 2008, at 4:50 PM, Gary Kline wrote:
The problem with t rying to use mutt, even when I reach my
mailserver on, is that *somehow* -- I do not understand how
-- but
for some reason, mutt tacks on the FDQN rather than simply my domain
[ ... ]

it never reached me at  Can anybody clue me in?
Sure.  If you want to masquerade a local machine's FQDN to just your
domain name, follow the happy instructions from the FAQ:

        well, i tried what was in the; I put the
MASQUERADE_AS() into both mc files.  Below is the evidence that
it didn't work.   Any other pages you can suggest...?

MDeferred: 450 4.7.1 <>: Helo command rejected: Host not found
$_localhost []
MDeferred: 450 4.7.1 <>: Helo command rejected: Host not found

Yes, you should either set up working DNS for all of your machines which send email (if you control the DNS for, consider using DynDNS or equivalent so that is resolvable) or (depending on whether you have administrative control over the destination SMART_HOST mailserver) look into the access map:

...or, failing that, enabling these with caution:

                Normally, MAIL FROM: commands in the SMTP session will be
                refused if the host part of the argument to MAIL FROM:
                cannot be located in the host name service (e.g., an A or
                MX record in DNS).  If you are inside a firewall that has
                only a limited view of the Internet host name space, this
                could cause problems.  In this case you probably want to
                use this feature to accept all domains on input, even if
                they are unresolvable.

                This option allows any host in your domain as defined by
                class {m} to use your server for relaying.  Notice: make
                sure that your domain is not just a top level domain,
                e.g., com.  This can happen if you give your host a name
                like instead of

You can also define your local host name (aka class w) to be something which the other machine can resolve. By the way, an excerpt from the mail logs (/var/log/mail.log) are the best source of info for relaying issues, although it is possible to figure out some of the issues from a stuck message in the spool.

It's also possible that if you set your SMART_HOST to your ISP's mailserver, and configure authentication with them, they will let you relay even if your mail submission is using local/invalid DNS hostnames.


_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to