Hi there,
on our firewall, I have a smtproutes file like this:
<---snip>
# Mail to Rog1 must be directed to ROG1
rog1.rog.rwth-aachen:rog1.rog.rwth-aachen.de
# Mail to CIP mail hosts uses central RWTH mail relay
cip.rog.rwth-aachen.de:mail.rwth-aachen.de
cip1.rog.rwth-aachen.de:mail.rwth-aachen.de
berlin.rog.rwth-aachen.de:mail.rwth-aachen.de
# Qmos is internal Mail host for eecs and rog domain
eecs.rwth-aachen.de:qmos.rog.rwth-aachen.de
rog.rwth-aachen.de:qmos.rog.rwth-aachen.de
# Qmos is internal Mail host for mail to any other *.rog host
.rog.rwth-aachen.de:qmos.rog.rwth-aachen.de
# Any other mail uses standard MX routing
:
<---snap>
Everything works fine, well, except for mails to <user>@rog1.rog.rwth-aachen.de,
which is still relayed to qmos.rog.rwth-aachen.de, our internal mail host.
Especially forwarding for hosts cip, cip1 and berlin works fine, so my first
guess of problems with the wildcards in the last but one rule was nil.
Split DNS's MX entries for rog1 are
IN MX 10 rog1.rog.rwth-aachen.de.
IN MX 15 qmos.rog.rwth-aachen.de.
Our firewall host is definitely allowed to connect to rog1's SMTP port.
Any hints ?
GRTX
Juergen
