Re: [exim] Very weird e-mail problems

Top Page
Delete this message
Reply to this message
Author: Patrick - South Valley Internet
Date:  
To: Patrick - South Valley Internet
CC: exim-users
Subject: Re: [exim] Very weird e-mail problems
Okay, reading up on Exim, I tried to resend everything in the queue using:

exim -q -v

And I got a bunch of these:

LOG: queue_run MAIN
Start queue run: pid=3520
delivering 1GqBX7-0004ZP-Cd (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <postmaster@???> R=lookuphost T=remote_smtp
defer (-53): retry time not reached for any host
delivering 1Gpkfr-0004Re-KS (queue run pid 3520)
LOG: skip_delivery MAIN
Message is frozen
delivering 1GqEA0-0007bb-Ik (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <jacobs@???> R=lookuphost T=remote_smtp
defer (-53): retry time not reached for any host
delivering 1GqFRE-0000GJ-8G (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <sales@???> R=lookuphost T=remote_smtp defer
(-53): retry time not reached for any host
delivering 1GqBMz-0003OS-HD (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <andy@???> R=lookuphost T=remote_smtp defer
(-53): retry time not reached for any host
delivering 1Gp0xO-0008QH-9e (queue run pid 3520)
LOG: retry_defer MAIN
== martych@??? <martyc@???> R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
delivering 1Gp2N8-0000Ae-3R (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <matt@???> R=lookuphost T=remote_smtp defer
(-53): retry time not reached for any host
delivering 1Gq0T3-0008Se-IW (queue run pid 3520)
LOG: skip_delivery MAIN
Message is frozen
delivering 1GqFiC-0002et-E3 (queue run pid 3520)
LOG: retry_defer MAIN
== enyedy@??? <enyedy@???> R=lookuphost T=remote_smtp
defer (-53): retry time not reached for any host
delivering 1GqEWi-0001mG-R0 (queue run pid 3520)


What does that mean? Is there a problem with Exim or Postfix?

Thanks again.

Patrick




Patrick - South Valley Internet wrote:
> I found the problem! Kinda...
>
> It turns out it is the Exim server. I just ran the Exim command to see
> how many e-mails are in the queue:
>
> exim -bpc
>
> And it kicked back 2292...
>
> how the heck is there all that e-mail, and why? I just set up another
> forward that forwards to my gmail account, and it forwards instantly.
>
> Now that I've tracked the culprit down, what to do next?
>
> Thanks again everyone!
>
> Patrick
>
>
>
>
>
>
> Patrick - South Valley Internet wrote:
>
>> I thought it had to do with the load issues on the box, but I'm not too
>> certain about that. I just did another test - this time I emailed my
>> garlic.com email address directly (which is on the Postfix server) and I
>> received the e-mail instantly. However, emailing my patrick@???
>> email forward that should forward to my garlic.com e-mail address, I
>> still haven't received it. And I sent that before I sent the e-mail
>> directly to my garlic.com email address.
>>
>> What should I look for to troubleshoot this problem, and how should I go
>> about it?
>>
>> Thanks again for all the help.
>>
>> Patrick
>>
>>
>>
>>
>> Patrick - South Valley Internet wrote:
>>
>>
>>> It appears it has something to do with the box that Postfix is on. The
>>> load averages on that box were up to 8.00 yesterday, and now they are
>>> around 1.60, but that's still a little high. I'm not sure what's wrong
>>> with the box, but it appears it has something to do with that.
>>>
>>> Thanks again for the help! I know it's not Exim now :)
>>>
>>> Patrick
>>>
>>>
>>> Stanislaw Halik wrote:
>>>
>>>
>>>
>>>> On Thu, Nov 30, 2006, Patrick - South Valley Internet wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> I just now received the e-mail, and grep'd the logs again:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2006-11-30 16:37:09 1GpwHs-0004wU-QP => enyedy@???
>>>>> <patrick@???> F=<patrick.masciocchi@???> R=lookuphost
>>>>> T=remote_smtp S=1745 H=vfr.net.southvalley.mail1.psmtp.com [64.18.4.10]
>>>>> X=TLSv1:AES256-SHA:256 C="250 Thanks"
>>>>> 2006-11-30 16:37:09 1GpwHs-0004wU-QP Completed
>>>>>
>>>>>
>>>>>
>>>>>
>>>> I smell Postfix.
>>>>
>>>> Try sniffing on your destination box, too. tcpflow is a nice easy-to-use
>>>> plaintext sniffer.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>