[7.450][BUG][FIXED] SMTP spool?

Just looked into mail manager and saw lots of mails in the spool, all marked with "error". After further investigation I found the mails in question were indeed delivered correctly. Even a mail I sent to a Astaro engineer yesterday is in the queue (it definitely was delivered correctly as I received a reply *g*).

In the smtp logs the mail is also correctly handled:

2009:06:10-11:20:29 astaro1 exim[6737]: 2009-06-10 11:20:29 SMTP connection from [192.168.0.90]:16102 (TCP/IP connection count = 1)

2009:06:10-11:20:29 astaro1 exim[9736]: 2009-06-10 11:20:29 [192.168.0.90] F= R= Accepted: from relay

2009:06:10-11:20:29 astaro1 exim[9736]: 2009-06-10 11:20:29 1MEJyv-0002X2-1t  ***@astaro.com R=smarthost_route T=remote_smtp H=mail.***.de [***]:25 X=TLSv1[:D]HE-RSA-AES256-SHA:256

2009:06:10-11:20:53 astaro1 exim[9741]: 2009-06-10 11:20:53 10QTJE-0002X2-1t Completed

I removed private data from this excerpt. This was a mail sent from here to Astaro. The queue also contains mails I received via SMTP correctly, as I can find them in my Exchange mailbox [;)]

Here a log from an incoming mail:

2009:06:10-12:52:17 astaro1 exim[6737]: 2009-06-10 12:52:17 SMTP connection from [***]:30997 (TCP/IP connection count = 1)

2009:06:10-12:52:17 astaro1 exim[12087]: 2009-06-10 12:52:17 [212.184.24.81] F= R= Verifying recipient address with callout

2009:06:10-12:52:18 astaro1 exim[12087]: 2009-06-10 12:52:18 1MELPm-00038x-0m ctasd reports 'Unknown' RefID:str=0001.0A0B0206.4A2F9062.01A6,ss=1,fgs=0

2009:06:10-12:52:18 astaro1 exim[12087]: 2009-06-10 12:52:18 1MELPm-00038x-0m Greylisting: *** is a known retry host

2009:06:10-12:52:18 astaro1 exim[12087]: 2009-06-10 12:52:18 1MELPm-00038x-0m  ***@***.de R=static_route_hostlist T=static_smtp H=192.168.0.90 [192.168.0.90]:25 X=TLSv1:AES128-SHA:128

2009:06:10-12:52:20 astaro1 exim[12096]: 2009-06-10 12:52:20 10dz5J-00038x-0m Completed

The queue finally contains ASG notifications, too.

I found my logs also include the crash messages as already noted in https://community.sophos.com/products/unified-threat-management/astaroorg/f/98/t/67518

Parents

0 chow11 over 16 years ago

I have this same error. After a fresh reboot, the smtp spool is clear, but after a while I come back and look and it looks like the last 2 weeks of delivered email shows up as "error".
- mail_mgr.jpg
- View
- Hide
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RDL over 16 years ago in reply to chow11

The 7.450 mail spool is definately doing multiple weird things.
I do have this issue.

I also have the issue with stuff getting stuck in error with the time bomb symbol that never clears, if I view that email, it has multiple reattempts to deliver undeliverable mail, it never quits. Some of the errors go away, some don't due to a bounced message, undeliverable to sender. ie SPAM
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 chow11 over 16 years ago in reply to RDL

In case there we might find a common element here..

My backend SMTP server is Exchange 2007 64-bit (running on 64-bit 2003 server).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Monarch over 16 years ago in reply to chow11

I'm also using Exchange 2007, but its running on Server 2008 x64.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BAlfson over 16 years ago in reply to Monarch

Have you turned off tarpitting? Apparently, it's on by default in Exchange 2007.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Monarch over 16 years ago in reply to BAlfson

I will check this tonight.

But I didn't change my Exchange configuration and until ASG 7.402 inclusively it worked.

Regards,
Bastian
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to Monarch

If you use the "callout" method for address verification on the Astaro with an Exchange 2007 server, make sure you disable the tarpit feature which is enabled by default on that version... this can also be enabled on Exchange 2003, but it's disabled by default.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Astaro Beta Bot over 16 years ago in reply to BrucekConvergent

Astaro Beta Report
--------------------------------
Version: 7.450
Type: BUG
State: FIXED
Reporter: Monarch
Contributor: 
MantisID: 10727 
--------------------------------

0 Monarch over 16 years ago in reply to Astaro Beta Bot

OK, now I checked again the smtp spool. And I saw there are no new messages after the 7.460 Update. Has this update possibly fixed the problem [:S]

Thus I won't examine my Exchange configuration any further for now.

Regards,
Bastian
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 chow11 over 16 years ago in reply to BAlfson

Have you turned off tarpitting?  Apparently, it's on by default in Exchange 2007.

Cheers - Bob

I did have to go through removing tarpitting from Exchange 2007 to get exchange to even accept mail from ASG.  Thanks to whomever posted those instructions.

If I use the mail manager to "retry" the messages, then I see duplicates in my inbox of mail that was already delivered, so it seems like maybe there is some event that can happen at the end of the mail delivery, maybe specific to exchange 2007, that looks like and error but really isn't.

Interestingly, I just looked at the spool and I haven't seen an "error" since 6/18.

Perhaps this is "fixed" in 7.460 and I am just seeing leftovers from 7.450.  I will clear the spool and see if that takes care of it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 chow11 over 16 years ago in reply to BAlfson

Have you turned off tarpitting?  Apparently, it's on by default in Exchange 2007.

Cheers - Bob

I did have to go through removing tarpitting from Exchange 2007 to get exchange to even accept mail from ASG.  Thanks to whomever posted those instructions.

If I use the mail manager to "retry" the messages, then I see duplicates in my inbox of mail that was already delivered, so it seems like maybe there is some event that can happen at the end of the mail delivery, maybe specific to exchange 2007, that looks like and error but really isn't.

Interestingly, I just looked at the spool and I haven't seen an "error" since 6/18.

Perhaps this is "fixed" in 7.460 and I am just seeing leftovers from 7.450.  I will clear the spool and see if that takes care of it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data