Re: [Assp-test] Email::MIME problem

[Colin W. <co...@la...>]

Strangely, downgrading to 1.911 and upgrading to the latest ASSP did not
work for me. I have already had some overnight reports of corrupted mail.

I am just upgrading to 14144 now so hopefully that will resolve the problem.
With 14144 should we use the latest Email::MIME?

All the best,
Colin Waring.

-----Original Message-----
From: Thomas Eckardt [mailto:Tho...@th...] 
Sent: 23 May 2014 16:39
To: ASSP development mailing list
Subject: Re: [Assp-test] Email::MIME problem

clean the PTRCache after upgrade

Thomas




Von:    "Colin Waring" <co...@la...>
An:     "'ASSP development mailing list'" 
<ass...@li...>
Datum:  23.05.2014 17:27
Betreff:        Re: [Assp-test] Email::MIME problem



I've gone through my servers and replaces Email::MIME 1.926 with 1.911.

I'll get the latest version of ASSP running shortly. PTR cache is turned off
already, presumably I noticed problems with the cache at some point.

I have ASSP_AFC enabled but charset conversation not enabled.

All the best,
Colin Waring.

-----Original Message-----
From: Thomas Eckardt [mailto:Tho...@th...]
Sent: 23 May 2014 10:23
To: ASSP development mailing list
Subject: Re: [Assp-test] Email::MIME problem

Colin,

>so you may wish to check the code introduced after 14097

I'm doing this for several days now.

With Email::MIME 1.926 I (and others) get wired behavior - even if I use the
same mail multiple times.

There are two places where assp uses Email::MIME to modify an  email, the
charset conversion and the ASSP_AFC plugin (in case of spam/bad attachment
only).
Both could be disabled having the same result.

I have an idea what could happen - but I hope I'm wrong. I'll have to look
in to Perl and Carp source code - eval and exception handling.

workaround -> use Email::MIME 1.911

Colin , btw. 14097 has a big issue with the PTR resolving/caching - switch
this check off!

Thomas

 





Von:    "Colin Waring" <co...@la...>
An:     "'ASSP development mailing list'" 
<ass...@li...>
Datum:  23.05.2014 09:56
Betreff:        Re: [Assp-test] Email::MIME problem



Hi Thomas,

This sounds like exactly the issue I reported on the 6th.

I found that the issue was not present in version 14097 and earlier so you
may wish to check the code introduced after 14097.

I've been busy with other things so haven't been able to do any more
troubleshooting on it and am still running 14097 myself without the issue.

All the best,
Colin Waring.

-----Original Message-----
From: Thomas Eckardt [mailto:Tho...@th...]
Sent: 23 May 2014 06:52
To: development mailing list ASSP
Subject: [Assp-test] Email::MIME problem

Hi all,

I got a report from Philipp about the problem were mails are delivered
incomplete/destroyed.

Philipp wrote:

...
I recently had the problem that some mails were forwarded incorrectly by
ASSP
2.4.2 build 14141 (and 14130, too).

That is, the mail was received and saved to file correctly, but when it was
forwarded to the destination MTA, it started in the midst of the content,
removed ALL header lines and added the ASSP-Headers at the end of the mail.
It was the same for noProcessing-mails, too, thus I excluded problems by
spam processing.

After long and painful debugging, I concluded that the problem must be the 



Header-Parsing of some multipart mails, but not all of them and I still
don't know which of those exactly, sorry!

Since I have another server with more or less the same configuration (at
least no differences that would influence noProcessing-mails) and there is
no sign of this problem, I concentrated on differences between those two
servers.

The only real differences were on some perl module version numbers. While
the faulty server had Email::MIME in version 1.926, the other one in version
1.911. Thus I downgraded this module on the faulty server and it seems as it
solved the problem.
....

I've released Email::MIME 1.911 as ZIP in the /lib folder on SF and SF-CVS.
To install it, copy the extracted ZIP in to the assp/lib folder and restart
assp. 
I currently don't know why and where the problem in assp is. It will take a
while to analyze the problem.

Thomas



DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the 



individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no known
virus in this email!
*******************************************************




----------------------------------------------------------------------------
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform 
available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Assp-test mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 


individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************




----------------------------------------------------------------------------
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform 
available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Assp-test mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************