relaying denied

[olga at urbantimes.net]

No, server X does not relay for the domains hosted on server Y (I do not
have relay-domains file on X for for those domains that are on Y). Should
I have it? May it cause any problems -- a lot of unwanted mail, spam?
X is only backup MX for the domains that are on Y. It has its own domains
it handles.
I do not have a mailertable file either (well, I do but, nothing is in
there).

>
> Are you sure that server X (your backup MX as I understand your post) is
> configured to allow relaying for all your domains listed on server Y? In
> other words - if server Y has 3 domains listed for local delivery
> (/etc/mail/local-host-names), then server X (your backup MX) would not
> list
> these domains as local, but rather list them as domains accepted for
> relaying to the primary MX when spammers deliberately connect to the
> backup
> MX first.
>
> Example: On server X (your backup MX)
>
> # cat /etc/mail/local-host-names
>
> # cat /etc/mail/relay-domains
> Domain1.com
> Domain2.com
> Domain3.com
>
> # cat /etc/mail/mailertable
> Domain1.com	esmtp:[primary_mx.mydomain1.com]
> Domain2.com	esmtp:[primary_mx.mydomain2.com]
> Domain3.com	esmtp:[primary_mx.mydomain3.com]
>
> FWIW: Running a backup MX introduces a whole set of new problems. The main
> one being keeping the backup MX's configuration regarding what is
> accetped/rejected/relayed/rbl's identical to that of the primary MX. In
> addition, the backup MX must be bale to lookup (like with LDAP) or contain
> a
> list of valid mailboxes on the primary MX so that, it too, can reject
> attempts to deliver e-mail to unknown accounts instead of generating a DSN
> back to a non-existant account. Thus clogging up your queues.
>
> Steve Cowles
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>