Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: exim: users

frozen messages

 

 

exim users RSS feed   Index | Next | Previous | View Threaded


jnatola at hotmail

Aug 27, 2009, 3:17 PM

Post #1 of 6 (1347 views)
Permalink
frozen messages

hi all,



I just noticed I have a few dozen frozen messages , some to actual valid users, others to bogus users- runnig exim -qff is not helping

how can i check why they are frozen?





tia

j





_________________________________________________________________
Hotmail® is up to 70% faster. Now good news travels really fast.
http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_faster:082009
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


eximX0902w at linuxwan

Aug 27, 2009, 7:45 PM

Post #2 of 6 (1292 views)
Permalink
Re: frozen messages [In reply to]

jean-paul natola wrote:
> I just noticed I have a few dozen frozen messages , some to actual
> valid users, others to bogus users- runnig exim -qff is not helping
> how can i check why they are frozen?

You'll have to interpret the message log for that particular message to
find out why they are getting stuck. Either use exigrep <messageid>
/path/to/mainlogfile, or exim -Mvl <message id>.

It also sounds like you might be accepting and then bouncing emails that
are sent to invalid local users. You should look into doing recipient
verification in your RCPT ACL. Accept and bounce is considered "A Bad
Thing"tm as it causes collateral spam.

ie. Something like this in your acl_check_rcpt (or whatever you have
called it)

# Deny unless the sender address can be verified.
require verify = sender

Here's some of the interesting command you might want to use when
playing with exim.

# exim -bp

This option requests a listing of the contents of the mail queue on
the standard output. If the -bp option is followed by a list of message
ids, just those messages are listed. By default, this option can be used
only by an admin user. However, the queue_list_requires_admin option can
be set false to allow any user to see the queue.

# exim -Mvl <message id>

This option causes the contents of the message log spool file to be
written to the standard output. This option can be used only by an admin
user.

# exim -Mt <message id> <message id> ...

This option requests Exim to “thaw” any of the listed messages that
are “frozen”, so that delivery attempts can resume. However, if any of
the messages are active, their status is not altered. This option can be
used only by an admin user.

The exim command line:
http://docs.exim.org/current/spec_html/ch05.html

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


jnatola at hotmail

Aug 28, 2009, 7:53 AM

Post #3 of 6 (1286 views)
Permalink
Re: frozen messages [In reply to]

Let me give you a bit of background first-



exim accepts mail (sa /clamav) then it delivers it to our internal Exchange server-



a few weeks ago I was tasked with creating a new domain and was running into trouble becuase exim would not relay mail for the new domain-



So i was told suggested to adjust my router config;



remove



route_out:
driver = dnslookup
transport = remote_smtp
domains = !example.com




and to change the



route_in



from



route_in:
driver = manualroute
transport = remote_smtp
domains = example.com:example2.com
route_list = * 192.168.1.2


to



route_in:
driver = manualroute
transport = remote_smtp
domains = +relay_to_domains
route_list = * 192.168.1.2










> Date: Fri, 28 Aug 2009 12:45:20 +1000
> From: eximX0902w [at] linuxwan
> To: exim-users [at] exim
> Subject: Re: [exim] frozen messages
>
> jean-paul natola wrote:
> > I just noticed I have a few dozen frozen messages , some to actual
> > valid users, others to bogus users- runnig exim -qff is not helping
> > how can i check why they are frozen?
>
> You'll have to interpret the message log for that particular message to
> find out why they are getting stuck. Either use exigrep <messageid>
> /path/to/mainlogfile, or exim -Mvl <message id>.
>
> It also sounds like you might be accepting and then bouncing emails that
> are sent to invalid local users. You should look into doing recipient
> verification in your RCPT ACL. Accept and bounce is considered "A Bad
> Thing"tm as it causes collateral spam.
>
> ie. Something like this in your acl_check_rcpt (or whatever you have
> called it)
>
> # Deny unless the sender address can be verified.
> require verify = sender
>
> Here's some of the interesting command you might want to use when
> playing with exim.
>
> # exim -bp
>
> This option requests a listing of the contents of the mail queue on
> the standard output. If the -bp option is followed by a list of message
> ids, just those messages are listed. By default, this option can be used
> only by an admin user. However, the queue_list_requires_admin option can
> be set false to allow any user to see the queue.
>
> # exim -Mvl <message id>
>
> This option causes the contents of the message log spool file to be
> written to the standard output. This option can be used only by an admin
> user.
>
> # exim -Mt <message id> <message id> ...
>
> This option requests Exim to “thaw” any of the listed messages that
> are “frozen”, so that delivery attempts can resume. However, if any of
> the messages are active, their status is not altered. This option can be
> used only by an admin user.
>
> The exim command line:
> http://docs.exim.org/current/spec_html/ch05.html
>
> --
> ## List details at http://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/

_________________________________________________________________
With Windows Live, you can organize, edit, and share your photos.
http://www.windowslive.com/Desktop/PhotoGallery
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


exim-users at lists

Aug 28, 2009, 8:05 AM

Post #4 of 6 (1291 views)
Permalink
Re: frozen messages [In reply to]

On 28/08/2009 15:53, jean-paul natola wrote:

> Let me give you a bit of background first-

<snip random bits of config>

>> You'll have to interpret the message log for that particular message to
>> find out why they are getting stuck. Either use exigrep<messageid>
>> /path/to/mainlogfile, or exim -Mvl<message id>.

Did you do this part? What is in the log file for one of these messages?
Also, please don't top post.

--
Mike Cardwell - IT Consultant and LAMP developer
Cardwell IT Ltd. (UK Reg'd Company #06920226) http://cardwellit.com/

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


jnatola at hotmail

Aug 28, 2009, 8:35 AM

Post #5 of 6 (1287 views)
Permalink
Re: frozen messages [In reply to]

> Date: Fri, 28 Aug 2009 16:05:26 +0100
> From: exim-users [at] lists
> To: Exim-users [at] exim
> Subject: Re: [exim] frozen messages
>
> On 28/08/2009 15:53, jean-paul natola wrote:
>
> > Let me give you a bit of background first-
>
> <snip random bits of config>
>
> >> You'll have to interpret the message log for that particular message to
> >> find out why they are getting stuck. Either use exigrep<messageid>
> >> /path/to/mainlogfile, or exim -Mvl<message id>.
>
> Did you do this part? What is in the log file for one of these messages?
> Also, please don't top post.
>




yes i have here is one example (obvious spam)

2009-08-27 07:18:51 Received from <> R=1Mgd0A-000G5A-CD U=mailnull P=local S=3635
2009-08-27 07:18:51 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:10:27 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:11:34 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:44:14 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-27 19:01:02 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-27 19:26:17 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-28 09:02:03 SMTP error from remote mail server after RCPT TO:<predominatef5 [at] sexdisk>: host mail.sexdisk.ru [195.182.143.150]: 550 "Where sender of this mail?!"
2009-08-28 09:02:03 predominatef5 [at] sexdisk R=familyroute_out T=remote_smtp: SMTP error from remote mail server after RCPT TO:<predominatef5 [at] sexdisk>: host mail.sexdisk.ru [195.182.143.150]: 550 "Where sender of this mail?!"
*** Frozen (delivery error message)
2009-08-28 09:06:10 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)
2009-08-28 11:30:53 routing failed for predominatef5 [at] sexdisk: Unknown user
*** Frozen (delivery error message)




HOWVER, this one was a valid email from one of our employees relatives



2009-08-26 19:07:33 Received from <> R=1MgRaS-000EMm-Ha U=mailnull P=local S=14397
2009-08-26 19:07:33 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:10:27 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:11:35 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-27 18:44:13 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-27 19:01:02 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-27 19:26:17 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)
2009-08-28 09:01:04 oberdad [at] aol <OberDAD [at] aol> R=familyroute_out T=remote_smtp: SMTP error from remote mail server after initial connection: host mailin-01.mx.aol.com [64.12.137.169]: 554- (RTR:DU) http://postmaster.info.aol.com/errors/554rtrdu.html\n554 Connecting IP: 72.43.172.72
*** Frozen (delivery error message)
2009-08-28 09:06:10 routing failed for oberdad [at] aol <OberDAD [at] aol>: Unknown user
*** Frozen (delivery error message)












_________________________________________________________________
Windows Live: Keep your friends up to date with what you do online.
http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


d.hill at yournetplus

Aug 28, 2009, 8:56 AM

Post #6 of 6 (1278 views)
Permalink
Re: frozen messages [In reply to]

On Fri, 28 Aug 2009, jean-paul natola wrote:

> 2009-08-28 09:01:04 oberdad [at] aol <OberDAD [at] aol> R=familyroute_out T=remote_smtp: SMTP error from remote mail server after initial connection: host mailin-01.mx.aol.com [64.12.137.169]: 554- (RTR:DU) http://postmaster.info.aol.com/errors/554rtrdu.html\n554 Connecting IP: 72.43.172.72
> *** Frozen (delivery error message)

AOL provided a link on this one. The reverse lookup for the IP mentioned
(72.43.172.72) is rrcs-72-43-172-72.nyc.biz.rr.com. It is a generic
reverse RoadRunner Internet uses for their business class customers. AOL
is blocking because the IP is on pbl.spamhaus.org:

%dig @localhost 72.172.43.72.pbl.spamhaus.org
...
;; ANSWER SECTION:
72.172.43.72.pbl.spamhaus.org. 900 IN A 127.0.0.10

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

exim users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.