Auteur: tim harding Date: À: Giuliano Gavazzi CC: exim-users Sujet: Re: [Exim] Receive Fails for Certain Hosts
oh, bugger.
thought that was an incoming attempt from mobile.att.net to me.
i'm having difficultly receiving from mobile.att.net and etrade's
mailer.
both wind up going to server on a lower priority MX record that is
configured and maintained by my DNS provider.
just tailed the exim log again and sent mail from my mobile account.
nothing registered in the logs so i've nothing to go on at all.
thanks though, -tim
On Monday, January 27, 2003, at 04:14 PM, Giuliano Gavazzi wrote:
> At 15:57 -0600 2003/01/27, tim harding wrote:
>> Philip,
>>
>> Ignore the MX stuff about gatezero.org. I was merely providing
>> context.
>>
>> What do the log lines mean and how can I tweak exim to accept delivery
>> from that host?
>>
>> Thanks,
>
>
> I think Philip was lost because you log does not seem to indicate any
> problem. It is a delivery (an outgoing authenticated smtp transaction)
> from you to this indietim.
> What host are you talking about anyway? There are two hosts in that
> log.
>
>
> Giuliano
>
>>
>> -tim
>> On Monday, January 27, 2003, at 04:07 AM, Philip Hazel wrote:
>>
>>> On Sun, 26 Jan 2003, tim harding wrote:
>>>
>>>> i have the mx record for gatezero.org pointed at my cable modem's ip
>>>> address and this doesn't reverse resolve to gatezero.org.
>>>> i have a lower priority mx record pointed to my dns hosting provider
>>>> as
>>>> a fallback.
>>>>
>>>> 2003-01-26 14:20:06 18ctGA-0007dw-00 <= tim@???
>>>> H=(gatezero.org) [12.162.1.71] P=asmtp A=fixed_cram:tim S=566
>>>> id=20062852-316C-11D7-AC86-0003937B741E@???
>>>> 2003-01-26 14:20:07 18ctGA-0007dw-00 => indietim@???
>>>> R=lookuphost T=remote_smtp H=mta01.cdpd.airdata.com [199.88.234.33]
>>>> 2003-01-26 14:20:07 18ctGA-0007dw-00 Completed
>>>>
>>>> any ideas what the problem might be. all other mail seems to
>>>> deliver
>>>> fine and i hope to tweak my side include deliveries from those two
>>>> senders.
>>>
>>> I am afraid I have lost you here. What is the problem? The MX record
>>> for
>>> mobile.att.net does point to 199.88.234.33.
>