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

Mailing List Archive: Qmail: users

Delayed delivery

 

 

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


mdm at openaccessinc

Nov 1, 2009, 5:29 AM

Post #1 of 12 (3048 views)
Permalink
Delayed delivery

My qmail server processes all the inbound and outbound mail for my RT
Trouble Ticket Server. The issue is when RT processes requests it will
send approx 10 to 15 individual emails to one domain. About half of
those emails will be delivered imeadiatly the rest will be delivered
over th next 15 minutes.

What causes this behavior and what can be done correct it? I am
apparrently am at a complete loss.

Btw. I know the use of dist lists would solve this issue but at
present this not possible.


Michael Di Matino
Open Access, Inc.


lists-qmail at maexotic

Nov 1, 2009, 6:29 AM

Post #2 of 12 (2933 views)
Permalink
Re: Delayed delivery [In reply to]

On Sun, Nov 01, 2009 at 07:29:11AM -0600, Michael Di Martino wrote:
> What causes this behavior and what can be done correct it? I am
> apparrently am at a complete loss.

As I already wriote the last time you asked here:
What does the qmail-send logfile say?

I'd bet you can see the reason in there.
Check it. If you don't understand, it post some relevant lines here.

\Maex


mdm at openaccessinc

Nov 1, 2009, 6:50 AM

Post #3 of 12 (2918 views)
Permalink
RE: Delayed delivery [In reply to]

-----Original Message-----
From: Markus Stumpf [mailto:lists-qmail [at] maexotic]
Sent: Sunday, November 01, 2009 9:29 AM
To: Michael Di Martino
Cc: qmail List
Subject: Re: Delayed delivery

On Sun, Nov 01, 2009 at 07:29:11AM -0600, Michael Di Martino wrote:
> What causes this behavior and what can be done correct it? I am
> apparrently am at a complete loss.
__________________________________________________________________________

>>> As I already wriote the last time you asked here:
>> What does the qmail-send logfile say?

>> I'd bet you can see the reason in there.
>>Check it. If you don't understand, it post some relevant lines here.

>>> \Maex
__________________________________________________________________________________

Output of /var/log/qmail/current
As u will see 6 emails were delivered, howeer after running qmailctl queue you can see 6 still need to be delivered.


@kirk ~]$ sudo su -l
Password:
[root [at] kir ~]# tail -f /var/log/qmail/current
@400000004aed9e7f1230e9ec delivery 7926: success: 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_1257086581_31si6336125qyk.19/
@400000004aed9e7f1230f5a4 status: local 0/10 remote 5/80
@400000004aed9e7f18ef721c delivery 7924: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_4A493E604AD/
@400000004aed9e7f18ef79ec status: local 0/10 remote 4/80
@400000004aed9e8339522414 delivery 7916: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_CF5A1E604A3/
@400000004aed9e8339522be4 status: local 0/10 remote 3/80
@400000004aed9e8402c7345c delivery 7923: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_E4193E604AC/
@400000004aed9e8402c73c2c status: local 0/10 remote 2/80
@400000004aed9e8410d62094 delivery 7925: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_29710E604AA/
@400000004aed9e8410d62864 status: local 0/10 remote 1/80



@400000004aed9ec60a38b8dc delivery 7911: success: 64.194.216.140_accepted_message./Remote_host_said:_250_Ok:_queued_as_D08724470F/
@400000004aed9ec60a38c0ac status: local 0/10 remote 0/80

1 Nov 2009 14:43:00 GMT #6815748 986 <anonymous [at] t>
done remote swinick [at] topspinpartners
done remote rsantori [at] openaccessinc
remote roswald [at] openaccessinc
done remote rbecker [at] openaccessinc
remote nocsupport [at] openaccessinc
done remote nmayorga [at] openaccessinc
remote miles [at] openaccessinc
remote mdm [at] openaccessinc
remote mbeveridge [at] openaccessinc
done remote jrodriguez [at] openaccessinc
done remote jcapie [at] openaccessinc
remote ibatista [at] openaccessinc
done remote gto [at] openaccessinc
done remote ggradel [at] openaccessinc
done remote dsimone [at] openaccessinc
done remote cgucker [at] openaccessinc
28 Oct 2009 19:12:09 GMT #6815749 35228 <>
remote no-reply [at] thetakecare
[root [at] kir ~]#


Output from
/var/log/qmail/smtpd/current
2009-11-01 05:23:21.687547500 tcpserver: status: 0/20
2009-11-01 09:39:46.811572500 tcpserver: status: 1/20
2009-11-01 09:39:46.811633500 tcpserver: pid 3426 from 112.104.66.19
2009-11-01 09:39:46.826561500 tcpserver: ok 3426 t.openaccessinc.com:66.206.112.158:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::3512
2009-11-01 09:39:46.839528500 tcpserver: status: 2/20
2009-11-01 09:39:46.839601500 tcpserver: pid 3427 from 112.104.66.19
2009-11-01 09:39:46.841531500 tcpserver: status: 3/20
2009-11-01 09:39:46.841598500 tcpserver: pid 3428 from 112.104.66.19
2009-11-01 09:39:46.844541500 tcpserver: ok 3427 t.openaccessinc.com:66.206.112.152:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::2102
2009-11-01 09:39:46.845531500 tcpserver: ok 3428 t.openaccessinc.com:66.206.112.159:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::2531
2009-11-01 09:39:46.850528500 tcpserver: status: 4/20
2009-11-01 09:39:46.850605500 tcpserver: pid 3429 from 112.104.66.19
2009-11-01 09:39:46.854533500 tcpserver: ok 3429 t.openaccessinc.com:66.206.112.154:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::4145
2009-11-01 09:39:47.370238500 tcpserver: end 3426 status 256
2009-11-01 09:39:47.370239500 tcpserver: status: 3/20
2009-11-01 09:39:47.393199500 tcpserver: end 3427 status 256
2009-11-01 09:39:47.393200500 tcpserver: status: 2/20
2009-11-01 09:39:47.398186500 tcpserver: end 3428 status 256
2009-11-01 09:39:47.398188500 tcpserver: status: 1/20
2009-11-01 09:39:47.416190500 tcpserver: end 3429 status 256
2009-11-01 09:39:47.416191500 tcpserver: status: 0/20
[root [at] kir ~]#


mdm at openaccessinc

Nov 1, 2009, 7:16 AM

Post #4 of 12 (2959 views)
Permalink
RE: Delayed delivery [In reply to]

-----Original Message-----
From: Michael Di Martino [mailto:mdm [at] openaccessinc]
Sent: Sunday, November 01, 2009 9:51 AM
To: qmail List
Cc: Markus Stumpf
Subject: RE: Delayed delivery



-----Original Message-----
From: Markus Stumpf [mailto:lists-qmail [at] maexotic]
Sent: Sunday, November 01, 2009 9:29 AM
To: Michael Di Martino
Cc: qmail List
Subject: Re: Delayed delivery

On Sun, Nov 01, 2009 at 07:29:11AM -0600, Michael Di Martino wrote:
> What causes this behavior and what can be done correct it? I am
> apparrently am at a complete loss.
__________________________________________________________________________

>>> As I already wriote the last time you asked here:
>> What does the qmail-send logfile say?

>> I'd bet you can see the reason in there.
>>Check it. If you don't understand, it post some relevant lines here.

>>> \Maex
__________________________________________________________________________________

Output of /var/log/qmail/current
As u will see 6 emails were delivered, howeer after running qmailctl queue you can see 6 still need to be delivered.


@kirk ~]$ sudo su -l
Password:
[root [at] kir ~]# tail -f /var/log/qmail/current
@400000004aed9e7f1230e9ec delivery 7926: success: 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_1257086581_31si6336125qyk.19/
@400000004aed9e7f1230f5a4 status: local 0/10 remote 5/80
@400000004aed9e7f18ef721c delivery 7924: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_4A493E604AD/
@400000004aed9e7f18ef79ec status: local 0/10 remote 4/80
@400000004aed9e8339522414 delivery 7916: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_CF5A1E604A3/
@400000004aed9e8339522be4 status: local 0/10 remote 3/80
@400000004aed9e8402c7345c delivery 7923: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_E4193E604AC/
@400000004aed9e8402c73c2c status: local 0/10 remote 2/80
@400000004aed9e8410d62094 delivery 7925: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_29710E604AA/
@400000004aed9e8410d62864 status: local 0/10 remote 1/80



@400000004aed9ec60a38b8dc delivery 7911: success: 64.194.216.140_accepted_message./Remote_host_said:_250_Ok:_queued_as_D08724470F/
@400000004aed9ec60a38c0ac status: local 0/10 remote 0/80

1 Nov 2009 14:43:00 GMT #6815748 986 <anonymous [at] t>
done remote swinick [at] topspinpartners
done remote rsantori [at] openaccessinc
remote roswald [at] openaccessinc
done remote rbecker [at] openaccessinc
remote nocsupport [at] openaccessinc
done remote nmayorga [at] openaccessinc
remote miles [at] openaccessinc
remote mdm [at] openaccessinc
remote mbeveridge [at] openaccessinc
done remote jrodriguez [at] openaccessinc
done remote jcapie [at] openaccessinc
remote ibatista [at] openaccessinc
done remote gto [at] openaccessinc
done remote ggradel [at] openaccessinc
done remote dsimone [at] openaccessinc
done remote cgucker [at] openaccessinc
28 Oct 2009 19:12:09 GMT #6815749 35228 <>
remote no-reply [at] thetakecare
[root [at] kir ~]#


Output from
/var/log/qmail/smtpd/current
2009-11-01 05:23:21.687547500 tcpserver: status: 0/20
2009-11-01 09:39:46.811572500 tcpserver: status: 1/20
2009-11-01 09:39:46.811633500 tcpserver: pid 3426 from 112.104.66.19
2009-11-01 09:39:46.826561500 tcpserver: ok 3426 t.openaccessinc.com:66.206.112.158:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::3512
2009-11-01 09:39:46.839528500 tcpserver: status: 2/20
2009-11-01 09:39:46.839601500 tcpserver: pid 3427 from 112.104.66.19
2009-11-01 09:39:46.841531500 tcpserver: status: 3/20
2009-11-01 09:39:46.841598500 tcpserver: pid 3428 from 112.104.66.19
2009-11-01 09:39:46.844541500 tcpserver: ok 3427 t.openaccessinc.com:66.206.112.152:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::2102
2009-11-01 09:39:46.845531500 tcpserver: ok 3428 t.openaccessinc.com:66.206.112.159:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::2531
2009-11-01 09:39:46.850528500 tcpserver: status: 4/20
2009-11-01 09:39:46.850605500 tcpserver: pid 3429 from 112.104.66.19
2009-11-01 09:39:46.854533500 tcpserver: ok 3429 t.openaccessinc.com:66.206.112.154:25 112-104-66-19.adsl.dynamic.seed.net.tw:112.104.66.19::4145
2009-11-01 09:39:47.370238500 tcpserver: end 3426 status 256
2009-11-01 09:39:47.370239500 tcpserver: status: 3/20
2009-11-01 09:39:47.393199500 tcpserver: end 3427 status 256
2009-11-01 09:39:47.393200500 tcpserver: status: 2/20
2009-11-01 09:39:47.398186500 tcpserver: end 3428 status 256
2009-11-01 09:39:47.398188500 tcpserver: status: 1/20
2009-11-01 09:39:47.416190500 tcpserver: end 3429 status 256
2009-11-01 09:39:47.416191500 tcpserver: status: 0/20
[root [at] kir ~]#

____________________________________________________________________________________

The remaining 6 emails were just delivered. Here is the full output of the send log.

2009-11-01 09:43:00.458118500 new msg 6815745
2009-11-01 09:43:00.458121500 info msg 6815745: bytes 1321 from <anonymous [at] t> qp 3625 uid 48
2009-11-01 09:43:00.476785500 starting delivery 7910: msg 6815745 to remote mdm [at] openaccessinc
2009-11-01 09:43:00.476786500 status: local 0/10 remote 1/80
2009-11-01 09:43:00.485079500 new msg 6815748
2009-11-01 09:43:00.485081500 info msg 6815748: bytes 986 from <anonymous [at] t> qp 3627 uid 48
2009-11-01 09:43:00.502512500 starting delivery 7911: msg 6815748 to remote swinick [at] topspinpartners
2009-11-01 09:43:00.502513500 status: local 0/10 remote 2/80
2009-11-01 09:43:00.502514500 starting delivery 7912: msg 6815748 to remote rsantori [at] openaccessinc
2009-11-01 09:43:00.502516500 status: local 0/10 remote 3/80
2009-11-01 09:43:00.502516500 starting delivery 7913: msg 6815748 to remote roswald [at] openaccessinc
2009-11-01 09:43:00.502518500 status: local 0/10 remote 4/80
2009-11-01 09:43:00.502519500 starting delivery 7914: msg 6815748 to remote rbecker [at] openaccessinc
2009-11-01 09:43:00.502529500 status: local 0/10 remote 5/80
2009-11-01 09:43:00.502530500 starting delivery 7915: msg 6815748 to remote nocsupport [at] openaccessinc
2009-11-01 09:43:00.502532500 status: local 0/10 remote 6/80
2009-11-01 09:43:00.502532500 starting delivery 7916: msg 6815748 to remote nmayorga [at] openaccessinc
2009-11-01 09:43:00.502534500 status: local 0/10 remote 7/80
2009-11-01 09:43:00.502534500 starting delivery 7917: msg 6815748 to remote miles [at] openaccessinc
2009-11-01 09:43:00.502539500 status: local 0/10 remote 8/80
2009-11-01 09:43:00.502540500 starting delivery 7918: msg 6815748 to remote mdm [at] openaccessinc
2009-11-01 09:43:00.502541500 status: local 0/10 remote 9/80
2009-11-01 09:43:00.502542500 starting delivery 7919: msg 6815748 to remote mbeveridge [at] openaccessinc
2009-11-01 09:43:00.502543500 status: local 0/10 remote 10/80
2009-11-01 09:43:00.502544500 starting delivery 7920: msg 6815748 to remote jrodriguez [at] openaccessinc
2009-11-01 09:43:00.502549500 status: local 0/10 remote 11/80
2009-11-01 09:43:00.502558500 starting delivery 7921: msg 6815748 to remote jcapie [at] openaccessinc
2009-11-01 09:43:00.502559500 status: local 0/10 remote 12/80
2009-11-01 09:43:00.502560500 starting delivery 7922: msg 6815748 to remote ibatista [at] openaccessinc
2009-11-01 09:43:00.502561500 status: local 0/10 remote 13/80
2009-11-01 09:43:00.502562500 starting delivery 7923: msg 6815748 to remote gto [at] openaccessinc
2009-11-01 09:43:00.502563500 status: local 0/10 remote 14/80
2009-11-01 09:43:00.502567500 starting delivery 7924: msg 6815748 to remote ggradel [at] openaccessinc
2009-11-01 09:43:00.502568500 status: local 0/10 remote 15/80
2009-11-01 09:43:00.502569500 starting delivery 7925: msg 6815748 to remote dsimone [at] openaccessinc
2009-11-01 09:43:00.502570500 status: local 0/10 remote 16/80
2009-11-01 09:43:00.502571500 starting delivery 7926: msg 6815748 to remote cgucker [at] openaccessinc
2009-11-01 09:43:00.502572500 status: local 0/10 remote 17/80
2009-11-01 09:43:00.665771500 delivery 7915: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:00.665774500 status: local 0/10 remote 16/80
2009-11-01 09:43:00.753754500 delivery 7922: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:00.753756500 status: local 0/10 remote 15/80
2009-11-01 09:43:00.820678500 delivery 7917: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:00.820681500 status: local 0/10 remote 14/80
2009-11-01 09:43:00.904640500 delivery 7913: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:00.904643500 status: local 0/10 remote 13/80
2009-11-01 09:43:00.965611500 delivery 7920: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_CFF4AE6045A/
2009-11-01 09:43:00.965613500 status: local 0/10 remote 12/80
2009-11-01 09:43:00.984582500 delivery 7919: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:00.984585500 status: local 0/10 remote 11/80
2009-11-01 09:43:01.047525500 delivery 7918: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:43:01.047527500 status: local 0/10 remote 10/80
2009-11-01 09:43:01.049603500 delivery 7910: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_CFED1E60429/
2009-11-01 09:43:01.049605500 status: local 0/10 remote 9/80
2009-11-01 09:43:01.049606500 end msg 6815745
2009-11-01 09:43:01.100506500 delivery 7921: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_F081BE604AA/
2009-11-01 09:43:01.100508500 status: local 0/10 remote 8/80
2009-11-01 09:43:01.196498500 delivery 7914: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_146BCE604AC/
2009-11-01 09:43:01.196501500 status: local 0/10 remote 7/80
2009-11-01 09:43:01.297458500 delivery 7912: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_2C406E6045A/
2009-11-01 09:43:01.297461500 status: local 0/10 remote 6/80
2009-11-01 09:43:01.305195500 delivery 7926: success: 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_1257086581_31si6336125qyk.19/
2009-11-01 09:43:01.305198500 status: local 0/10 remote 5/80
2009-11-01 09:43:01.418345500 delivery 7924: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_4A493E604AD/
2009-11-01 09:43:01.418347500 status: local 0/10 remote 4/80
2009-11-01 09:43:05.961684500 delivery 7916: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_CF5A1E604A3/
2009-11-01 09:43:05.961686500 status: local 0/10 remote 3/80
2009-11-01 09:43:06.046609500 delivery 7923: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_E4193E604AC/
2009-11-01 09:43:06.046611500 status: local 0/10 remote 2/80
2009-11-01 09:43:06.282468500 delivery 7925: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_29710E604AA/
2009-11-01 09:43:06.282470500 status: local 0/10 remote 1/80
2009-11-01 09:44:12.171489500 delivery 7911: success: 64.194.216.140_accepted_message./Remote_host_said:_250_Ok:_queued_as_D08724470F/
2009-11-01 09:44:12.171491500 status: local 0/10 remote 0/80
2009-11-01 09:49:41.170865500 starting delivery 7927: msg 6815748 to remote roswald [at] openaccessinc
2009-11-01 09:49:41.170867500 status: local 0/10 remote 1/80
2009-11-01 09:49:41.170924500 starting delivery 7928: msg 6815748 to remote nocsupport [at] openaccessinc
2009-11-01 09:49:41.170925500 status: local 0/10 remote 2/80
2009-11-01 09:49:41.171019500 starting delivery 7929: msg 6815748 to remote miles [at] openaccessinc
2009-11-01 09:49:41.171020500 status: local 0/10 remote 3/80
2009-11-01 09:49:41.171137500 starting delivery 7930: msg 6815748 to remote mdm [at] openaccessinc
2009-11-01 09:49:41.171138500 status: local 0/10 remote 4/80
2009-11-01 09:49:41.171139500 starting delivery 7931: msg 6815748 to remote mbeveridge [at] openaccessinc
2009-11-01 09:49:41.171140500 status: local 0/10 remote 5/80
2009-11-01 09:49:41.171141500 starting delivery 7932: msg 6815748 to remote ibatista [at] openaccessinc
2009-11-01 09:49:41.171142500 status: local 0/10 remote 6/80
2009-11-01 09:49:41.306492500 delivery 7930: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
2009-11-01 09:49:41.306495500 status: local 0/10 remote 5/80
2009-11-01 09:49:41.617297500 delivery 7929: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_7B55BE60491/
2009-11-01 09:49:41.617299500 status: local 0/10 remote 4/80
2009-11-01 09:49:41.790201500 delivery 7931: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_9F09EE6049E/
2009-11-01 09:49:41.790203500 status: local 0/10 remote 3/80
2009-11-01 09:49:41.796219500 delivery 7927: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_A698AE604AD/
2009-11-01 09:49:41.796220500 status: local 0/10 remote 2/80
2009-11-01 09:49:41.796293500 delivery 7932: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_A683FE604A1/
2009-11-01 09:49:41.796294500 status: local 0/10 remote 1/80
2009-11-01 09:49:41.797234500 delivery 7928: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_A66C7E6049A/
2009-11-01 09:49:41.797236500 status: local 0/10 remote 0/80
2009-11-01 09:53:44.795861500 starting delivery 7933: msg 6815752 to remote no-reply [at] theredstake
2009-11-01 09:53:44.795862500 status: local 0/10 remote 1/80
2009-11-01 09:54:46.273922500 delivery 7933: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
2009-11-01 09:54:46.273923500 status: local 0/10 remote 0/80
2009-11-01 10:09:41.273895500 starting delivery 7934: msg 6815748 to remote mdm [at] openaccessinc
2009-11-01 10:09:41.273897500 status: local 0/10 remote 1/80
2009-11-01 10:09:41.644891500 delivery 7934: success: 98.129.185.3_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_8215BA6D92C/
2009-11-01 10:09:41.644893500 status: local 0/10 remote 0/80
2009-11-01 10:09:41.644894500 end msg 6815748
2009-11-01 10:12:24.643868500 starting delivery 7935: msg 6815747 to remote bk [at] isis
2009-11-01 10:12:24.643870500 status: local 0/10 remote 1/80
2009-11-01 10:12:24.685644500 delivery 7935: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
2009-11-01 10:12:24.685646500 status: local 0/10 remote 0/80
[root [at] kir ~]#


kyle-qmail at memoryhole

Nov 1, 2009, 7:38 AM

Post #5 of 12 (2935 views)
Permalink
Re: Delayed delivery [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sunday, November 1 at 09:16 AM, quoth Michael Di Martino:
>2009-11-01 09:43:00.665771500 delivery 7915: deferral:
>Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/

There's your answer right there. Your recipient refused to accept that
many connections from you (which is an unfortunately common, and
misguided, anti-spam technique). Thus, some of the messages could not
be delivered right away. Qmail waited, tried again later, and they got
through on the second try.

To fix this, you either need to involve serialmail (a somewhat
involved process where you deliver all messages for this domain to a
local Maildir and then use serialmail to push all those messages out
through a single connection), OR convince the recipient domain of the
idiocy of its connection limitation policy.

~Kyle
- --
Strong coffee, much strong coffee, is what awakens me. Coffee gives me
warmth, waking, an unusual force and a pain that is not without very
great pleasure.
-- Napoleon Bonaparte
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJK7at0AAoJECuveozR/AWeThkQAKXCjLtzBxbvo6vQm0Mb2kkk
1zrjq+m5i3ADQrgjzpJuQjENggKLlJ44J6Vn0wIY2jdDrlZ9gZi7QabjpeUyfata
9eLYBBmg4C2/fFmP3nFLKp9B40SERmagE2PJON5za1YQgBcXYDJc6uc2iYevK9wM
L+dKeopNZQ+Dw783s4VI/XMyb7sij1xi0f7vR2dG4MjSVqWNIsE83LYzt9l4q5PF
svYJ/IgLutaOqc4D7XW5h1UGIU07l8KcNe1z/cSl+eebDZFH/3UnMiNM/gajUXH6
lcj+GhZBkdqOvJffkhKUXk4XzYQRz0vik0fIAfkmAzaB0RWQbB8PDB2fqoxBChSI
zKkllLX9RfvHCJ+egWJ39yTZmmePdPlF+RCxwjOaiJhubylc3BZNFsBApxqjYw9i
A0RMrt8OSqEA0U745koMFcFxUjKyvBZD3e5Bb4L7VBM7r1N7irSuUlzQL8kIw/qj
KdJQrQybF2F0rq1g7eKn7I6Ooa5kOvvsX+MnF9ecZQ4Wl5glul2blijxej2etydJ
nvMyOw+aNkzsNGHLdaFrJZCTseyOfb/jpmaPkhrKNYcz9d+QTHCz+sJ48beQ7xsQ
iVcQeTDEAPZkwEPPlWkEzbXiEllU3FsQmFsxSoNmSNQmF7gsiEqGLr1psb04pc+A
loBD3c4RaI2WbNYs7JWD
=MqeC
-----END PGP SIGNATURE-----


lists-qmail at maexotic

Nov 1, 2009, 8:11 AM

Post #6 of 12 (2936 views)
Permalink
Re: Delayed delivery [In reply to]

On Sun, Nov 01, 2009 at 09:16:13AM -0600, Michael Di Martino wrote:
> 2009-11-01 09:43:00.502571500 starting delivery 7926: msg 6815748 to remote cgucker [at] openaccessinc
> 2009-11-01 09:43:00.502572500 status: local 0/10 remote 17/80
> 2009-11-01 09:43:00.665771500 delivery 7915: deferral: Connected_to_98.129.185.3_but_greeting_failed./Remote_host_said:_421_4.7.0_gate2.gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/

Ah, here it is!
You are allowing you qmail server to open 80 parallel outgoing
connections. The server at 98.129.185.3 however has a limit on
the number of parallel incoming connections from the same IP address.
(spam protection probably).

You have 2 (easy) possibilities:
1) If you qmail server is not running with heavy load, reduce the number
of parallel outgoing connections to 10. This should be fine for the
receiving server. (see control/concurrencyremote file)
2) If you have control of the receiving server you could check whether
you can increase the number of parallel incoming connection for one
IP address *only* (for 66.206.114.119) to maybe 20 or 30.

If both of the above solutions are unacceptable more work is needed.

1) on qmail.org there is a patch:
Joshua Megerman wrote a patch to implement hashed per-IP connection
limiting in qmail-send and qmail-remote.
http://www.coyotetechnical.com/software/patches/qmail-send-concurrencyperip.patch
It introduces a new control file "concurrencyperip".
I have never used that patch but it looks like it should solve
your problem by setting concurrencyperip to "10"

2) You could add a virtual domain for openaccessinc.net to the TTS server,
deliver those mails to a local Maildir and then use maildirsmtp from
a cron job to check and batch send the messages every minute or so.
For maildirsmtp you need the
http://cr.yp.to/serialmail.html
package.

\Maex


mdm at openaccessinc

Nov 1, 2009, 9:06 AM

Post #7 of 12 (2923 views)
Permalink
RE: Delayed delivery [In reply to]

Michael DiMartino | Director of IT | Open Access, Inc.
115 Bi County Blvd | Farmingdale, NY 11735     
631.227.1034| 631.694.6730 FAX |631.988.6060 MOBILE
www.openaccessinc.com


-----Original Message-----
From: Markus Stumpf [mailto:lists-qmail [at] maexotic]
Sent: Sunday, November 01, 2009 10:49 AM
To: Michael Di Martino
Cc: qmail List
Subject: Re: Delayed delivery

On Sun, Nov 01, 2009 at 08:50:42AM -0600, Michael Di Martino wrote:
> Output of /var/log/qmail/current
> As u will see 6 emails were delivered, howeer after running qmailctl queue you can see 6 still need to be delivered.

Yes. And the inetresting ones are the ones that did NOT get delivered.
Could you do a
fgrep deferral /var/log/qmail/current | fgrep roswald [at] openaccessinc
and send the output?
Or if this is empty do a
fgrep deferral /var/log/qmail/* | fgrep roswald [at] openaccessinc

Another question: how does your setup look like?
1) You have one machine that hosts the Trouble Ticket System. This machine
runs qmail and sends the mail. The qmail-send logfile was from that
machine.
2) This machine sends the messages to another machine. This is running
another mailserver (not qmail).
3) you provided a smtpd logile of a qmail server. Which server is this?
The one o the TTS machine? Another one?

\Maex

__________________________________________________________________________________

Strangely this comes up empty.
[root [at] kir qmail]#
[root [at] kir qmail]# fgrep deferral /var/log/qmail/current | fgrep roswald [at] openaccessinc
[root [at] kir qmail]#

1) You have one machine that hosts the Trouble Ticket System. This machine
runs qmail and sends the mail. The qmail-send logfile was from that
machine.
RT and qmail are on the same box.

2) This machine sends the messages to another machine. This is running
another mailserver (not qmail).
The outbound mail for @openaccessinc.com sent to another linbox.
The concurrencyincomming is now set to 40 and this box concurrencyremote is not set to 10
This setting has now increased the # of deferrals.

3) you provided a smtpd logile of a qmail server. Which server is this?
The one o the TTS machine? Another one?
This is the RT qmail box.


mdm at openaccessinc

Nov 1, 2009, 9:40 AM

Post #8 of 12 (2970 views)
Permalink
Re: Delayed delivery [In reply to]

On Nov 1, 2009, at 11:05 AM, "Kyle Wheeler" <kyle-
qmail [at] memoryhole> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sunday, November 1 at 09:16 AM, quoth Michael Di Martino:
>> 2009-11-01 09:43:00.665771500 delivery 7915: deferral:
>> Connected_to_98.129.185.3_but_greeting_failed./
>> Remote_host_said:
>> _421_4.7.0_gate2.
>> gate.dfw.mlsrvr.com_Error:_too_many_connections_from_66.206.114.119/
>
> There's your answer right there. Your recipient refused to accept that
> many connections from you (which is an unfortunately common, and
> misguided, anti-spam technique). Thus, some of the messages could not
> be delivered right away. Qmail waited, tried again later, and they got
> through on the second try.
>
> To fix this, you either need to involve serialmail (a somewhat
> involved process where you deliver all messages for this domain to a
> local Maildir and then use serialmail to push all those messages out
> through a single connection), OR convince the recipient domain of the
> idiocy of its connection limitation policy.
>
> ~Kyle
> - --
> Strong coffee, much strong coffee, is what awakens me. Coffee gives me
> warmth, waking, an unusual force and a pain that is not without very
> great pleasure.
> -- Napoleon Bonaparte
> -----BEGIN PGP SIGNATURE-----
> Comment: Thank you for using encryption!
>
> iQIcBAEBCAAGBQJK7at0AAoJECuveozR/AWeThkQAKXCjLtzBxbvo6vQm0Mb2kkk
> 1zrjq+m5i3ADQrgjzpJuQjENggKLlJ44J6Vn0wIY2jdDrlZ9gZi7QabjpeUyfata
> 9eLYBBmg4C2/fFmP3nFLKp9B40SERmagE2PJON5za1YQgBcXYDJc6uc2iYevK9wM
> L+dKeopNZQ+Dw783s4VI/XMyb7sij1xi0f7vR2dG4MjSVqWNIsE83LYzt9l4q5PF
> svYJ/IgLutaOqc4D7XW5h1UGIU07l8KcNe1z/cSl+eebDZFH/3UnMiNM/gajUXH6
> lcj+GhZBkdqOvJffkhKUXk4XzYQRz0vik0fIAfkmAzaB0RWQbB8PDB2fqoxBChSI
> zKkllLX9RfvHCJ+egWJ39yTZmmePdPlF+RCxwjOaiJhubylc3BZNFsBApxqjYw9i
> A0RMrt8OSqEA0U745koMFcFxUjKyvBZD3e5Bb4L7VBM7r1N7irSuUlzQL8kIw/qj
> KdJQrQybF2F0rq1g7eKn7I6Ooa5kOvvsX+MnF9ecZQ4Wl5glul2blijxej2etydJ
> nvMyOw+aNkzsNGHLdaFrJZCTseyOfb/jpmaPkhrKNYcz9d+QTHCz+sJ48beQ7xsQ
> iVcQeTDEAPZkwEPPlWkEzbXiEllU3FsQmFsxSoNmSNQmF7gsiEqGLr1psb04pc+A
> loBD3c4RaI2WbNYs7JWD
> =MqeC
> -----END PGP SIGNATURE


That was it thank you.


f_a_f12001 at yahoo

Nov 2, 2009, 12:54 AM

Post #9 of 12 (2925 views)
Permalink
RE: Delayed delivery [In reply to]

I have aside question,
If my logs said some thing like this,
@400000004aed9e7f1230e9ec delivery 7926: success:
209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_1257086581_31si6336125qyk.19/
-This really means the recipient server really accepted the message?, Or there is any chance it didn't receive it, As I had a case before about specific email as my logs said the remote server accepted the message like this log entry, But the recipient insisted he didn't get the message, We tried with another message and got the same result.


lists-qmail at maexotic

Nov 2, 2009, 4:34 AM

Post #10 of 12 (2923 views)
Permalink
Re: Delayed delivery [In reply to]

On Mon, Nov 02, 2009 at 12:54:30AM -0800, MOHAMED AHMED wrote:
> If my logs said some thing like this,
> @400000004aed9e7f1230e9ec delivery 7926: success:
> 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_1257086581_31si6336125qyk.19/
> -This really means the recipient server really accepted the message?

Yes ... from the answer it looks like the receiving server provides a
timestamp (1257086581) and also an internal message-id (31si6336125qyk.19)
for reference.

> But the recipient insisted he didn't get the message,
> We tried with another message and got the same result.

Maybe the recipient wants to have a look at his Google Spam Folder?
Or he automatically sorted it into some other folder (eg with a regex
pattern?).

\Maex


feh at fehcom

Nov 2, 2009, 5:24 AM

Post #11 of 12 (2917 views)
Permalink
Re: Delayed delivery [In reply to]

Hi,


--On Montag, November 02, 2009 13:34:56 +0100 Markus Stumpf
<lists-qmail [at] maexotic> wrote:

> On Mon, Nov 02, 2009 at 12:54:30AM -0800, MOHAMED AHMED wrote:
>> If my logs said some thing like this,
>> @400000004aed9e7f1230e9ec delivery 7926: success:
>> 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_125708658
>> 1_31si6336125qyk.19/ -This really means the recipient server really
>> accepted the message?
>
> Yes ... from the answer it looks like the receiving server provides a
> timestamp (1257086581) and also an internal message-id (31si6336125qyk.19)
> for reference.
>
>> But the recipient insisted he didn't get the message,
>> We tried with another message and got the same result.
>
> Maybe the recipient wants to have a look at his Google Spam Folder?
> Or he automatically sorted it into some other folder (eg with a regex
> pattern?).

Recently I run into the same trap:

Some automtic (PHP/Java) mail programs don't generate a valid email header.
In particular, they 'forget' to include the 'Date:' header.

Depending on the mail client of the targeted user, the mail is listed at
the very first line in the inbox (if sorted by date); thus it seems, there
was no mail received.
In particular, if the inbox is very large (my has currently about 180
unsorted entries), you simply miss this mail.

regards.
--eh.


>
> \Maex
>



Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/


f_a_f12001 at yahoo

Nov 3, 2009, 1:18 AM

Post #12 of 12 (2893 views)
Permalink
Re: Delayed delivery [In reply to]

>Some automtic (PHP/Java) mail programs don't generate a valid email header.
>In particular, they 'forget' to include the 'Date:' header.
-Yes I think I saw some thing like that a short time ago, Somebody is receiving some emails only on his Outlook, But when he checks the web interface he doesn't find those emails, This is happening to him from time to time.
 I thought that time this is because his web interface is really old and I advised them to update it, May the new versions be better and it can show all emails.
--- On Mon, 11/2/09, Erwin Hoffmann <feh [at] fehcom> wrote:

From: Erwin Hoffmann <feh [at] fehcom>
Subject: Re: Delayed delivery
To: "MOHAMED AHMED" <f_a_f12001 [at] yahoo>
Cc: "qmail List" <qmail [at] list>
Date: Monday, November 2, 2009, 3:24 PM

Hi,


--On Montag, November 02, 2009 13:34:56 +0100 Markus Stumpf
<lists-qmail [at] maexotic> wrote:

> On Mon, Nov 02, 2009 at 12:54:30AM -0800, MOHAMED AHMED wrote:
>> If my logs said some thing like this,
>> @400000004aed9e7f1230e9ec delivery 7926: success:
>> 209.85.221.23_accepted_message./Remote_host_said:_250_2.0.0_OK_125708658
>> 1_31si6336125qyk.19/ -This really means the recipient server really
>> accepted the message?
>
> Yes ... from the answer it looks like the receiving server provides a
> timestamp (1257086581) and also an internal message-id (31si6336125qyk.19)
> for reference.
>
>> But the recipient insisted he didn't get the message,
>> We tried with another message and got the same result.
>
> Maybe the recipient wants to have a look at his Google Spam Folder?
> Or he automatically sorted it into some other folder (eg with a regex
> pattern?).

Recently I run into the same trap:

Some automtic (PHP/Java) mail programs don't generate a valid email header.
In particular, they 'forget' to include the 'Date:' header.

Depending on the mail client of the targeted user, the mail is listed at
the very first line in the inbox (if sorted by date); thus it seems, there
was no mail received.
In particular, if the inbox is very large (my has currently about 180
unsorted entries), you simply miss this mail.

regards.
--eh.


>
>     \Maex
>



Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/

Qmail 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.