Re: [exim] Extrange behavior with smarthost and routers

Top Page
Delete this message
Reply to this message
Author: W B Hacker
Date:  
To: exim users
Subject: Re: [exim] Extrange behavior with smarthost and routers
Jonathan GF wrote:
> Hi Dave,
>
> first of all i have to say that...yes.. i was? obfuscated. I tried to post
> as much information as posible and i only casused noise. You got reason.
>
> What i tried to state in the previous mail is that, even if the smarthost
> works, and the server behind works also, the bold lines shows an anormal
> activity.
>
> The logs, without the bold lines represent a normal behavior:
>
> Gmail -> smarthost -> server    (and vice-versa)

>
> But the bold lines show something like this:
>
> Gmail -> smarthost -> server -> call back to the smarthost     (let see the
> lines again)

>
> 2008-02-04 01:05:48 H=mail.surestorm.com [89.128.3.108] F=<> rejected RCPT <
> jonathangf@???>: Relay Not Permitted
> 2008-02-04 01:05:48 unexpected disconnection while reading SMTP command from
> mail.surestorm.com [89.128.3.108]
>
> This lines appears in the smarthost log, so it tell me the server, after put
> the message in the correct inbox tried something else. This sounds to me
> lika a loop.....What do you think?
>
> Cheers,
>
> Jonathan GF
>
>
>
> On Feb 4, 2008 9:47 PM, Dave Evans <exim-users-20071221@???> wrote:
>
>> Firstly, please carefully read http://wiki.exim.org/DontObfuscate ,
>> including
>> the "Why was I sent this URL?" section.
>>
>> On Mon, Feb 04, 2008 at 09:29:58PM +0100, Jonathan GF wrote:
>>> Unless the architecture work i can see weird messages in the logs,
>> something
>>> i want to fix because they sound like a loop between the exim smarthost
>> and
>>> exim mail server.
>> Doesn't look like that to me. To me, it looks like the smarthost receives
>> the
>> message <a50c1e90802031605p2bf68fd1l26e54a85b7216a0e@???> from
>> 66.249.82.231; it sends the message to 89.128.3.108 using the
>> send_to_mailserver router. The mail server then receives the message
>> (from
>> 64.79.209.162), and sends it to a maildir (virtual_user router).
>>
>> Is that not what's meant to be happening? If not, please try explaining
>> again
>> what the problem is (and take heed of the advice on DontObfuscate).
>> Thanks!
>>
>> --
>> Dave Evans
>> http://djce.org.uk/
>> http://djce.org.uk/pgpkey
>>


Check also if you are asking one Exim instance to attempt a sender
verify, but not configuring its sibling to be aware of what consitutes a
valid sender - i.e. one it 'knows about' and respond accordingly.

Bill