relaying denied

Alexander Dalloz alexander.dalloz at uni-bielefeld.de
Thu Jun 24 20:04:08 UTC 2004


Am Do, den 24.06.2004 schrieb olga at urbantimes.net um 21:42:

> So for those entries (with higher and lower MX) in the DNS setup to work
> correctly, I would need to configure /etc/mail/relay-domains and
> /etc/mail/mailertable and setup mailboxes for the users on Y to allow mail
> to be picked up by the lower priority MX in case something is wrong with
> the primary MX, otherwise the lower priority entry of the MX record does
> not do anything -- is this correct?

Correct, that you would have to configure your secondary MX server named
X to accept the domains of server Y for relaying to server Y. You do not
need to create the users of Y on X as local users.

You last sentence is incorrect: the lower priority MX record host is not
without consequences! Imagine what happens: a foreign MTA speaks to the
secondary MX server called X and tells him that he wants to pass him
mail for userfoo at domain_at_server_y.tld. What happens? Server X checks
whether the domains is local - no, it is not - or to be relayed - no, no
such instructions set, nor permissions for the foreign MTA to relay
through server X. Consequence? The incoming mail is rejected with
message "Relaying denied". You remember this sentence? ;)

Alexander
 

-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.6-1.435 
Serendipity 21:58:42 up 1 day, 20:36, load average: 0.41, 0.50, 0.37 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040624/fc5eca58/attachment-0001.sig>


More information about the fedora-list mailing list