[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Re: Relaying denied problem
- Subject: [cobalt-users] Re: Relaying denied problem
- From: Bruce Timberlake <bruce@xxxxxxxxxx>
- Date: Sun Mar 7 18:58:01 2004
- Organization: BRTNet.org
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
> I think he was talking about your dns server.
No, I was talking about the site settings on the RaQ. You generally need to
make two additions to the default entries: example.com in the web server
alias field (so that people entering example.com instead of www.example.com
will still reach your site; it adds a ServerAlias
to /etc/httpd/conf/httpd.conf) and example.com in the mail server alias field
(it's generally blank by default; adding an alias makes an entry
in /etc/mail/local-host-names telling sendmail it's ok to accept mail
addressed to example.com domain (vs www.example.com which is all it will
answer for by default).
If you already have an entry in the mail server alias field, then your
relaying denied problem lies elsewhere. But that missing entry is generally
the root of many email issues (esp the dreaded "max recursion" error), so I
thought I'd try there first.
The next test would be to, in a shell session, run "sendmail -bt" and try some
local rules to see what various incoming addresses "resolve" to according to
sendmail - i.e., make sure bob@xxxxxxxxxxx is ultimately pointed to the local
username "bob" (or whatever) on the server.
I think the rule to try is "3,0 username@xxxxxxxxxx" or "0,3
username@xxxxxxxxxx" - it should end up pointing at a local username. If not,
then your problems lie with an alias definition.
Oh yeah, you have to press ^D to get out of the sendmail "interactive" mode.