From: mouss (mlist.onlyfree.fr)
Date: Thu Jul 19 2007 - 07:00:39 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Uwe Dippel wrote:
> I'm sure that I am only overlooking something here; I have checked the
> archive and google, but somehow don't get the non-delivery messages
> that I'd like to have.
> My only interest are messages bounced from the inside, from my users,
> who use the box as relayhost. [the non-delivery is due to the TLD abc]
>
>> Jul 17 11:32:45 metalab postfix/smtp[4947]: 4A7D435A58:
>> to=<myusercompany.uk.abc>, relay=none, delay=0.7,
>> delays=0.31/0.1/0.29/0, dsn=5.4.4, status=bounced (Host or domain
>> name not found. Name service error for name=company.uk.abc type=AAAA:
>> Host not found)
>> Jul 17 11:32:45 metalab postfix/cleanup[20600]: E2E1935A5D:
>> message-id=<20070717033245.E2E1935A5Dmetalab.uniten.edu.my>
>> Jul 17 11:32:45 metalab postfix/bounce[25232]: 4A7D435A58: sender
>> non-delivery notification: E2E1935A5D
>> Jul 17 11:32:45 metalab postfix/qmgr[9907]: E2E1935A5D: from=<>,
>> size=2671, nrcpt=1 (queue active)
>> Jul 17 11:32:45 metalab postfix/qmgr[9907]: 4A7D435A58: removed
>> Jul 17 11:32:45 metalab postfix/smtp[28888]: warning: numeric domain
>> name in resource data of MX record for docu1.coit.uniten.edu.my:
>> 172.16.0.4

The MX must be a name, not an IP. then add an A record for the name to
point to the IP.

... MX foo.example.com
foo.example.com A 172.16.0.4

but there is no need for an MX here. just use transport_maps:

domain.example relay:[172.16.0.4]

>> Jul 17 11:32:46 metalab postfix/smtp[28888]: E2E1935A5D:
>> to=<docu1docu1.coit.uniten.edu.my>, relay=172.16.0.4[172.16.0.4]:25,
>> delay=0.08, delays=0.05/0.01/0.01/0.02, dsn=5.7.1, status=bounced
>> (host 172.16.0.4[172.16.0.4] said: 554 5.7.1
>> <docu1docu1.coit.uniten.edu.my>: Relay access denied (in reply to
>> RCPT TO command))

The remote host does not handle mail for docu1.... .edu.my, so it
rejects it. If that host should handle such mail, you need to configure
it to do so (in postfix, add the domain to mydestination or other domain
classes). if the host does not handle such mail, then you should not
send this mail to that host.

PS. do you know what "coit" means in french?
>
> I think that I understand all the details here. Of course, it cannot
> reach the internal host for which it works as relayhost. In order for
> it to not yell, I put a fake, but reachable address as MX record for
> this internal domain, and in the end it bounces at that fake IP and dies.
>
> All this doesn't bother me, but it doesn't produce what I want,
> neither. I need to know (to postmaster), whenever a mail from the (not
> reachable) inside box bounces. Like in this case: I'd like to see a
> mail to postmaster, stating that the inside box
> (docu1.coit.uniten.edu.my) could not deliver a message to
> myusercompany.uk.abc
where is output of 'postconf -n'.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]