|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: "mail loops back" problem
From: Marcelo P. Lima (mpl4
cornell.edu)
Date: Wed Feb 25 2004 - 12:45:35 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wietse,
You were 100% right -- it was the DNS that was screwed up! Somehow,
balka.com had a DNS entry on that hosting facility, when it shouldn't.
Now the email goes through.
Thank you so much for your help. I'm having another small problem which
I'll post under a separate thread.
Best regards,
Marcelo
On Feb 24, 2004, at 10:01, Wietse Venema wrote:
> Marcelo P. Lima:
>> Well, the same exercise for balka.com comes back blank, of course,
>> since balka.com is not a local domain on this machine:
>
> Good. The domain isn't local, it is not listed in the transport
> map, and therefore Postfix gives the mail to the SMTP client.
>
>> balka.com is just a domain to which I want to send email... the same
>> way I would send email to postfix-users
postfix.org or to
>> someone
yahoo.com, etc... but the email loops back :(
>
> Right. The Postfix SMTP client looks up the MX record for balka.com:
>
> balka.com. 1D IN MX 10 smtp.balka.com.
>
> and the A record for smtp.balka.com.
>
> smtp.balka.com. 23h58m9s IN A 209.15.32.137
>
> Postfix reports "warning: mailer loop: best MX host for balka.com
> is local" when the IP address matches $inet_interfaces or
> $proxy_interfaces.
>
> So either your DNS is screwed or your inet_interfaces or
> proxy_interfaces
> settings are.
>
> Wietse
>
>>
>>
>> On Feb 23, 2004, at 21:16, Wietse Venema wrote:
>>
>>> Marcelo P. Lima:
>>>> That is correct: mail for user
joesao.com (local users) are given to
>>>> maildrop.
>>>>
>>>> But I'm trying to send email to user
balka.com (user at another
>>>> domain
>>>> on another box in another network) and that mail is looping back...
>>>> how
>>>> do I fix that?
>>>
>>> OK, so we repeat the same transport mapping exercise for
>>> user
balka.com.
>>>
>>> What is the output from:
>>> postmap -q balka.com mysql:/etc/postfix/mysql_transport_maps.cf
>>> postmap -q user
balka.com
>>> mysql:/etc/postfix/mysql_transport_maps.cf
>>>
>>> And we'll take it from there.
>>>
>>> Wietse
>>>>
>>>>
>>>>
>>>> On Feb 23, 2004, at 20:16, Wietse Venema wrote:
>>>>
>>>>> Marcelo P. Lima:
>>>>>> mydestination = $mydomain, $transport_maps, localhost.$mydomain,
>>>>>> transport_maps = mysql:/etc/postfix/mysql_transport_maps.cf
>>>>>
>>>>> Marcelo P. Lima:
>>>>>> [root
localhost admin]# postmap -q joesao.com
>>>>>> mysql:/etc/postfix/mysql_transport_maps.cf
>>>>>> maildrop
>>>>>
>>>>> Then mail for user
joesao.com is given to the pipe delivery
>>>>> agent as specified in your master.cf file:
>>>>>
>>>>> maildrop unix - n n - - pipe
>>>>> flags=DRhu user=maildrop argv=/usr/bin/maildrop -w 90 -d
>>>>> ${recipient}
>>>>>
>>>>> This is not consistent with your observation that mail is given to
>>>>> the Postfix SMTP client.
>>>>>
>>>>> Wietse
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]