Anti-Spam SMTP Proxy Server

set 'spamdb' to 'DB:'
set 'DBdriver' to 'BerkeleyDB'

set the required options in the Bayesian/HMM section

restart assp

look in to the startuplog for error and warnings - solve possible problems

run a rebuildspamdb

Thomas




Von:    Adrian Stoica <adrian.stoica@...>
An:     assp-test@..., 
Datum:  29.05.2012 13:26
Betreff:        [Assp-test] question about berkelydb



Hello

Please advise me about how to config assp to use DB for bayesian and hmm.

I have tryied set spamdb "DB:" and "BerkelayDB:"
the HMMusesBDB is on , DBdriver is "BerkeleyDB"

The version of berkeleydb is 4.8

What should i use ? I want something small , like sqlite or berkeleydb 
but unfortunatley i don't know howto.

"The following drivers are available on your system:
BerkeleyDB, DBM, ExampleP, File, Gofer, Proxy, SQLite, Sponge, mysql"

Thank you,
Adrian

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

I still have this error:

[Main_Thread] Admin Update: task RunRebuildNow was queued to run in 
worker 10001
[Worker_10001] RebuildSpamDB uses BerkeleyDB for temporary hashes
[Worker_10001] BerkeleyDB-ERROR: Undefined subroutine main::BDB_Filter 
at /srv/assp/lib/rebuildspamdb.pm line 544 thread 2.
          - BDB:BDB0062 Successful return: 0


/srv/assp/lib/rebuildspamdb.pm :
package rebuildspamdb;
our $VERSION = '5.04';

Any ideea?

ignore this error - will be (is still) fixed. The right name is '
main::BDB_filter' not 'main::BDB_Filter'.
The rebuild will run without any mistake.

Thomas




Von:    Adrian Stoica <adrian.stoica@...>
An:     assp-test@..., 
Datum:  29.05.2012 14:33
Betreff:        [Assp-test] question about berkelydb



I still have this error:

[Main_Thread] Admin Update: task RunRebuildNow was queued to run in 
worker 10001
[Worker_10001] RebuildSpamDB uses BerkeleyDB for temporary hashes
[Worker_10001] BerkeleyDB-ERROR: Undefined subroutine main::BDB_Filter 
at /srv/assp/lib/rebuildspamdb.pm line 544 thread 2.
          - BDB:BDB0062 Successful return: 0


/srv/assp/lib/rebuildspamdb.pm :
package rebuildspamdb;
our $VERSION = '5.04';

Any ideea?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

>Usally memory is all used out when it does

Tell me someting about the system hardware.

Is this the case even if you

use a database for all main hashes and lists
use BerkeleyDB for griplist , the internal hashes and the rebuild hashes ?

How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl 
installation a distro package or self compiled from souce?
How many connections are handled per day?

>Would activating "$main::enableCrashAnalyzer = 0;"  give logs with useful 
info?
This will only help if specific mails are crashing assp.

>How do I crash-debug so I get good logs?
If perl gives assp the chance to get some infos about a crash, you'll find 
the infos in 'exception.log'.

Thomas



Von:    "Pontus Karlsson" <pontus@...>
An:     "'ASSP development mailing list'" 
<assp-test@...>, 
Datum:  25.05.2012 11:07
Betreff:        [Assp-test] Assp crashes a cuple of times per day.



Hi there!

I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl v5.14.2 
which I would belive is the latest I can run.

Due to reaccuring(2-3 times a day) crashes I have made upgrades on 
everything (used to run on older Debian and older perl) but ASSP keep on 
crashing.
I made a script which I run with cron every two minutes just to make sure 
assp is allways running(if it's not I start it again).
I get no logs when it crashes it just stops running. Usally memory is all 
used out when it does (but not the swap)
It's not really an acceptable solution to keep on restarting.

So, question:
How do I crash-debug so I get good logs?
I have tried verbose (not debug) mode  logging settings in assp. Lots of 
logs with no useful extra info.
How much load would debug on all give -and- would it give the crash-info I 
need?

Would activating "$main::enableCrashAnalyzer = 0;"  give logs with useful 
info?
Or, is there a way right way to do this "hunt"  to get things running 
smooth and not crash.

It crashes if I run it with a database or not, I have tried both to be 
sure the database had nothing to do with it.

Regards,
Pontus



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

I have a similar setup running - Ubuntu 12.04, Perl v5.14.2

I have always had a couple of instances of ASSP bailing out a day and I 
posted a thread about it back in February. The issue has been brought 
back into focus with the recent upgrades addressing simultaneous 
connections and I have been meaning to post back my results.

The upgraded version of ASSP that was meant to resolve the issue did not 
crash on me for approximately 24 hours but since then the crashes came back.

I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a 
single crash since.

So, for the original poster - do your logs show two workers handling 
similar messages just prior to the crash? If so try the above workaround 
to see if your issue is the same as mine.

For Thomas, the bad news at least on my part is that the fix that you 
put in the main code doesn't appear to have corrected the problem for 
me. If you have any other possible fixes I don't mind trying them out 
for you - we receive numerous frequent server monitoring alerts from our 
clients that come through the same or similar gateways so you can be 
guaranteed the problem will rear its head quickly.

All the best,
Colin Waring.

On 27/05/2012 07:06, Thomas Eckardt wrote:
>> Usally memory is all used out when it does
> Tell me someting about the system hardware.
>
> Is this the case even if you
>
> use a database for all main hashes and lists
> use BerkeleyDB for griplist , the internal hashes and the rebuild hashes ?
>
> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl
> installation a distro package or self compiled from souce?
> How many connections are handled per day?
>
>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with useful
> info?
> This will only help if specific mails are crashing assp.
>
>> How do I crash-debug so I get good logs?
> If perl gives assp the chance to get some infos about a crash, you'll find
> the infos in 'exception.log'.
>
> Thomas
>
>
>
> Von:    "Pontus Karlsson"<pontus@...>
> An:     "'ASSP development mailing list'"
> <assp-test@...>,
> Datum:  25.05.2012 11:07
> Betreff:        [Assp-test] Assp crashes a cuple of times per day.
>
>
>
> Hi there!
>
> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl v5.14.2
> which I would belive is the latest I can run.
>
> Due to reaccuring(2-3 times a day) crashes I have made upgrades on
> everything (used to run on older Debian and older perl) but ASSP keep on
> crashing.
> I made a script which I run with cron every two minutes just to make sure
> assp is allways running(if it's not I start it again).
> I get no logs when it crashes it just stops running. Usally memory is all
> used out when it does (but not the swap)
> It's not really an acceptable solution to keep on restarting.
>
> So, question:
> How do I crash-debug so I get good logs?
> I have tried verbose (not debug) mode  logging settings in assp. Lots of
> logs with no useful extra info.
> How much load would debug on all give -and- would it give the crash-info I
> need?
>
> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with useful
> info?
> Or, is there a way right way to do this "hunt"  to get things running
> smooth and not crash.
>
> It crashes if I run it with a database or not, I have tried both to be
> sure the database had nothing to do with it.
>
> Regards,
> Pontus
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> 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!
> *******************************************************
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test

I try to fix that in every new release. Even if I do not hint in the 
change log.

Colin, please do not use the workaround - it will work. Better use the 
latest version and report.

Thomas





Von:    Colin <assp@...>
An:     assp-test@..., 
Datum:  28.05.2012 17:15
Betreff:        Re: [Assp-test] Antwort:  Assp crashes a cuple of times 
per day.



I have a similar setup running - Ubuntu 12.04, Perl v5.14.2

I have always had a couple of instances of ASSP bailing out a day and I 
posted a thread about it back in February. The issue has been brought 
back into focus with the recent upgrades addressing simultaneous 
connections and I have been meaning to post back my results.

The upgraded version of ASSP that was meant to resolve the issue did not 
crash on me for approximately 24 hours but since then the crashes came 
back.

I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a 
single crash since.

So, for the original poster - do your logs show two workers handling 
similar messages just prior to the crash? If so try the above workaround 
to see if your issue is the same as mine.

For Thomas, the bad news at least on my part is that the fix that you 
put in the main code doesn't appear to have corrected the problem for 
me. If you have any other possible fixes I don't mind trying them out 
for you - we receive numerous frequent server monitoring alerts from our 
clients that come through the same or similar gateways so you can be 
guaranteed the problem will rear its head quickly.

All the best,
Colin Waring.

On 27/05/2012 07:06, Thomas Eckardt wrote:
>> Usally memory is all used out when it does
> Tell me someting about the system hardware.
>
> Is this the case even if you
>
> use a database for all main hashes and lists
> use BerkeleyDB for griplist , the internal hashes and the rebuild hashes 
?
>
> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl
> installation a distro package or self compiled from souce?
> How many connections are handled per day?
>
>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with 
useful
> info?
> This will only help if specific mails are crashing assp.
>
>> How do I crash-debug so I get good logs?
> If perl gives assp the chance to get some infos about a crash, you'll 
find
> the infos in 'exception.log'.
>
> Thomas
>
>
>
> Von:    "Pontus Karlsson"<pontus@...>
> An:     "'ASSP development mailing list'"
> <assp-test@...>,
> Datum:  25.05.2012 11:07
> Betreff:        [Assp-test] Assp crashes a cuple of times per day.
>
>
>
> Hi there!
>
> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl v5.14.2
> which I would belive is the latest I can run.
>
> Due to reaccuring(2-3 times a day) crashes I have made upgrades on
> everything (used to run on older Debian and older perl) but ASSP keep on
> crashing.
> I made a script which I run with cron every two minutes just to make 
sure
> assp is allways running(if it's not I start it again).
> I get no logs when it crashes it just stops running. Usally memory is 
all
> used out when it does (but not the swap)
> It's not really an acceptable solution to keep on restarting.
>
> So, question:
> How do I crash-debug so I get good logs?
> I have tried verbose (not debug) mode  logging settings in assp. Lots of
> logs with no useful extra info.
> How much load would debug on all give -and- would it give the crash-info 
I
> need?
>
> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with 
useful
> info?
> Or, is there a way right way to do this "hunt"  to get things running
> smooth and not crash.
>
> It crashes if I run it with a database or not, I have tried both to be
> sure the database had nothing to do with it.
>
> Regards,
> Pontus
>
>
>
> 
------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> 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!
> *******************************************************
>
>
>
>
> 
------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

Hi There!

Well, I have this in my Sub Set in the lib/CorrectASSPcfg.pm :
$main::delaySameIPorHelo = 5 # number > 0 - prevents accessing same storage
for identical connections at the same time
&main::mlog(0,"info: delaySameIPorHelo set to 5");

Still, it goes down every now and then.
I will check logs for dual connections, but I have not seen that happen yet.

Are you running the latest version of assp then?

Regards,
Pontus



-----Original Message-----
From: Colin [mailto:assp@...] 
Sent: den 28 maj 2012 17:15
To: assp-test@...
Subject: Re: [Assp-test] Antwort: Assp crashes a cuple of times per day.

I have a similar setup running - Ubuntu 12.04, Perl v5.14.2

I have always had a couple of instances of ASSP bailing out a day and I
posted a thread about it back in February. The issue has been brought back
into focus with the recent upgrades addressing simultaneous connections and
I have been meaning to post back my results.

The upgraded version of ASSP that was meant to resolve the issue did not
crash on me for approximately 24 hours but since then the crashes came back.

I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a
single crash since.

So, for the original poster - do your logs show two workers handling similar
messages just prior to the crash? If so try the above workaround to see if
your issue is the same as mine.

For Thomas, the bad news at least on my part is that the fix that you put in
the main code doesn't appear to have corrected the problem for me. If you
have any other possible fixes I don't mind trying them out for you - we
receive numerous frequent server monitoring alerts from our clients that
come through the same or similar gateways so you can be guaranteed the
problem will rear its head quickly.

All the best,
Colin Waring.

On 27/05/2012 07:06, Thomas Eckardt wrote:
>> Usally memory is all used out when it does
> Tell me someting about the system hardware.
>
> Is this the case even if you
>
> use a database for all main hashes and lists use BerkeleyDB for 
> griplist , the internal hashes and the rebuild hashes ?
>
> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl 
> installation a distro package or self compiled from souce?
> How many connections are handled per day?
>
>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with 
>> useful
> info?
> This will only help if specific mails are crashing assp.
>
>> How do I crash-debug so I get good logs?
> If perl gives assp the chance to get some infos about a crash, you'll 
> find the infos in 'exception.log'.
>
> Thomas
>
>
>
> Von:    "Pontus Karlsson"<pontus@...>
> An:     "'ASSP development mailing list'"
> <assp-test@...>,
> Datum:  25.05.2012 11:07
> Betreff:        [Assp-test] Assp crashes a cuple of times per day.
>
>
>
> Hi there!
>
> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl 
> v5.14.2 which I would belive is the latest I can run.
>
> Due to reaccuring(2-3 times a day) crashes I have made upgrades on 
> everything (used to run on older Debian and older perl) but ASSP keep 
> on crashing.
> I made a script which I run with cron every two minutes just to make 
> sure assp is allways running(if it's not I start it again).
> I get no logs when it crashes it just stops running. Usally memory is 
> all used out when it does (but not the swap) It's not really an 
> acceptable solution to keep on restarting.
>
> So, question:
> How do I crash-debug so I get good logs?
> I have tried verbose (not debug) mode  logging settings in assp. Lots 
> of logs with no useful extra info.
> How much load would debug on all give -and- would it give the 
> crash-info I need?
>
> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with 
> useful info?
> Or, is there a way right way to do this "hunt"  to get things running 
> smooth and not crash.
>
> It crashes if I run it with a database or not, I have tried both to be 
> sure the database had nothing to do with it.
>
> Regards,
> Pontus
>
>
>
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> 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!
> *******************************************************
>
>
>
>
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test


----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test

As it turns out the workaround doesn't work.

ASSP on my main relay restarted itself about an hour ago with the same 
symptoms - two connections from the same IP within 1 second of each other.

When I looked in the logs to check I noticed:

2012-05-28 20:50:12 [startup] Error: calling CorrectASSPcfg.pm returned 
error - Global symbol "$delaySameIPorHelo" requires explicit package 
name at /usr/local/assp/lib/CorrectASSPcfg.pm line 39.
         Compilation failed in require at (eval 41) line 1.
         BEGIN failed--compilation aborted at (eval 41) line 1.

I presume I have either got the spelling wrong or need to declare the 
variable before it takes effect.

So bad news for me getting it wrong, bad news for resolving the issue as 
I am running 2.2.2(12149).

Is there anything else I can do to help track down the problem?

All the best,
Colin.

On 28/05/2012 19:22, Thomas Eckardt wrote:
> I try to fix that in every new release. Even if I do not hint in the
> change log.
>
> Colin, please do not use the workaround - it will work. Better use the
> latest version and report.
>
> Thomas
>
>
>
>
>
> Von:    Colin<assp@...>
> An:     assp-test@...,
> Datum:  28.05.2012 17:15
> Betreff:        Re: [Assp-test] Antwort:  Assp crashes a cuple of times
> per day.
>
>
>
> I have a similar setup running - Ubuntu 12.04, Perl v5.14.2
>
> I have always had a couple of instances of ASSP bailing out a day and I
> posted a thread about it back in February. The issue has been brought
> back into focus with the recent upgrades addressing simultaneous
> connections and I have been meaning to post back my results.
>
> The upgraded version of ASSP that was meant to resolve the issue did not
> crash on me for approximately 24 hours but since then the crashes came
> back.
>
> I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a
> single crash since.
>
> So, for the original poster - do your logs show two workers handling
> similar messages just prior to the crash? If so try the above workaround
> to see if your issue is the same as mine.
>
> For Thomas, the bad news at least on my part is that the fix that you
> put in the main code doesn't appear to have corrected the problem for
> me. If you have any other possible fixes I don't mind trying them out
> for you - we receive numerous frequent server monitoring alerts from our
> clients that come through the same or similar gateways so you can be
> guaranteed the problem will rear its head quickly.
>
> All the best,
> Colin Waring.
>
> On 27/05/2012 07:06, Thomas Eckardt wrote:
>>> Usally memory is all used out when it does
>> Tell me someting about the system hardware.
>>
>> Is this the case even if you
>>
>> use a database for all main hashes and lists
>> use BerkeleyDB for griplist , the internal hashes and the rebuild hashes
> ?
>> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl
>> installation a distro package or self compiled from souce?
>> How many connections are handled per day?
>>
>>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with
> useful
>> info?
>> This will only help if specific mails are crashing assp.
>>
>>> How do I crash-debug so I get good logs?
>> If perl gives assp the chance to get some infos about a crash, you'll
> find
>> the infos in 'exception.log'.
>>
>> Thomas
>>
>>
>>
>> Von:    "Pontus Karlsson"<pontus@...>
>> An:     "'ASSP development mailing list'"
>> <assp-test@...>,
>> Datum:  25.05.2012 11:07
>> Betreff:        [Assp-test] Assp crashes a cuple of times per day.
>>
>>
>>
>> Hi there!
>>
>> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl v5.14.2
>> which I would belive is the latest I can run.
>>
>> Due to reaccuring(2-3 times a day) crashes I have made upgrades on
>> everything (used to run on older Debian and older perl) but ASSP keep on
>> crashing.
>> I made a script which I run with cron every two minutes just to make
> sure
>> assp is allways running(if it's not I start it again).
>> I get no logs when it crashes it just stops running. Usally memory is
> all
>> used out when it does (but not the swap)
>> It's not really an acceptable solution to keep on restarting.
>>
>> So, question:
>> How do I crash-debug so I get good logs?
>> I have tried verbose (not debug) mode  logging settings in assp. Lots of
>> logs with no useful extra info.
>> How much load would debug on all give -and- would it give the crash-info
> I
>> need?
>>
>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with
> useful
>> info?
>> Or, is there a way right way to do this "hunt"  to get things running
>> smooth and not crash.
>>
>> It crashes if I run it with a database or not, I have tried both to be
>> sure the database had nothing to do with it.
>>
>> Regards,
>> Pontus
>>
>>
>>
>>
> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> 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!
>> *******************************************************
>>
>>
>>
>>
>>
> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>
>>
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> 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!
> *******************************************************
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test

in 'CorrectASSPcfg.pm' you have to defne:

$main::delaySameIPorHelo = 5;

Thomas


Von:    Colin <assp@...>
An:     assp-test@..., 
Datum:  28.05.2012 23:06
Betreff:        Re: [Assp-test] Antwort: Re: Antwort: Assp crashes a cuple 
of times per day.



As it turns out the workaround doesn't work.

ASSP on my main relay restarted itself about an hour ago with the same 
symptoms - two connections from the same IP within 1 second of each other.

When I looked in the logs to check I noticed:

2012-05-28 20:50:12 [startup] Error: calling CorrectASSPcfg.pm returned 
error - Global symbol "$delaySameIPorHelo" requires explicit package 
name at /usr/local/assp/lib/CorrectASSPcfg.pm line 39.
         Compilation failed in require at (eval 41) line 1.
         BEGIN failed--compilation aborted at (eval 41) line 1.

I presume I have either got the spelling wrong or need to declare the 
variable before it takes effect.

So bad news for me getting it wrong, bad news for resolving the issue as 
I am running 2.2.2(12149).

Is there anything else I can do to help track down the problem?

All the best,
Colin.

On 28/05/2012 19:22, Thomas Eckardt wrote:
> I try to fix that in every new release. Even if I do not hint in the
> change log.
>
> Colin, please do not use the workaround - it will work. Better use the
> latest version and report.
>
> Thomas
>
>
>
>
>
> Von:    Colin<assp@...>
> An:     assp-test@...,
> Datum:  28.05.2012 17:15
> Betreff:        Re: [Assp-test] Antwort:  Assp crashes a cuple of times
> per day.
>
>
>
> I have a similar setup running - Ubuntu 12.04, Perl v5.14.2
>
> I have always had a couple of instances of ASSP bailing out a day and I
> posted a thread about it back in February. The issue has been brought
> back into focus with the recent upgrades addressing simultaneous
> connections and I have been meaning to post back my results.
>
> The upgraded version of ASSP that was meant to resolve the issue did not
> crash on me for approximately 24 hours but since then the crashes came
> back.
>
> I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a
> single crash since.
>
> So, for the original poster - do your logs show two workers handling
> similar messages just prior to the crash? If so try the above workaround
> to see if your issue is the same as mine.
>
> For Thomas, the bad news at least on my part is that the fix that you
> put in the main code doesn't appear to have corrected the problem for
> me. If you have any other possible fixes I don't mind trying them out
> for you - we receive numerous frequent server monitoring alerts from our
> clients that come through the same or similar gateways so you can be
> guaranteed the problem will rear its head quickly.
>
> All the best,
> Colin Waring.
>
> On 27/05/2012 07:06, Thomas Eckardt wrote:
>>> Usally memory is all used out when it does
>> Tell me someting about the system hardware.
>>
>> Is this the case even if you
>>
>> use a database for all main hashes and lists
>> use BerkeleyDB for griplist , the internal hashes and the rebuild 
hashes
> ?
>> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl
>> installation a distro package or self compiled from souce?
>> How many connections are handled per day?
>>
>>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with
> useful
>> info?
>> This will only help if specific mails are crashing assp.
>>
>>> How do I crash-debug so I get good logs?
>> If perl gives assp the chance to get some infos about a crash, you'll
> find
>> the infos in 'exception.log'.
>>
>> Thomas
>>
>>
>>
>> Von:    "Pontus Karlsson"<pontus@...>
>> An:     "'ASSP development mailing list'"
>> <assp-test@...>,
>> Datum:  25.05.2012 11:07
>> Betreff:        [Assp-test] Assp crashes a cuple of times per day.
>>
>>
>>
>> Hi there!
>>
>> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl 
v5.14.2
>> which I would belive is the latest I can run.
>>
>> Due to reaccuring(2-3 times a day) crashes I have made upgrades on
>> everything (used to run on older Debian and older perl) but ASSP keep 
on
>> crashing.
>> I made a script which I run with cron every two minutes just to make
> sure
>> assp is allways running(if it's not I start it again).
>> I get no logs when it crashes it just stops running. Usally memory is
> all
>> used out when it does (but not the swap)
>> It's not really an acceptable solution to keep on restarting.
>>
>> So, question:
>> How do I crash-debug so I get good logs?
>> I have tried verbose (not debug) mode  logging settings in assp. Lots 
of
>> logs with no useful extra info.
>> How much load would debug on all give -and- would it give the 
crash-info
> I
>> need?
>>
>> Would activating "$main::enableCrashAnalyzer = 0;"  give logs with
> useful
>> info?
>> Or, is there a way right way to do this "hunt"  to get things running
>> smooth and not crash.
>>
>> It crashes if I run it with a database or not, I have tried both to be
>> sure the database had nothing to do with it.
>>
>> Regards,
>> Pontus
>>
>>
>>
>>
> 
------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> 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!
>> *******************************************************
>>
>>
>>
>>
>>
> 
------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>
>>
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>
> 
------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> 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!
> *******************************************************
>
>
>
>
> 
------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

>once you've resolved the new bugs

There is no BUG - SSL works perfect in all versions, if there is no dependency mismatch. Try to debug SSL. This should show your local problem.
Keep in mind, that you have to reinstall/recompile Net::SSLeay if you update OpenSSL!

Thomas

-----"Steve Moss" <spm@...> schrieb: ----- 
An: "ASSP development mailing list" <assp-test@...>
Von: "Steve Moss" <spm@...>
Datum: 25.05.2012 09:10
Betreff: Re: [Assp-test] Antwort: Re: Antwort: SSL Problems With ASSP 2.1.2.12137

>> build 12123 with IO::Socket::SSL 1.74 ? This should not be possible!
<<

I never said it was. Build 12123 works with IO::Socket::SSL 1.44. Build
12137 doesn't work here with IO::Socket::SSL 1.44 or 1.74.

>> At least check your version of Net::SSLeay <<

Checked - it is version 1.48.

>> addition to the changelog of build 12145... <<

OK, I will check this out in a subsequent build, once you've resolved
the new bugs introduced in 12145.

>> Updating OpenSSL could help to prevent or to solve this problem. <<

I already have OpenSSL version 1.0.1c.


-----Original Message-----
From: Thomas Eckardt [mailto:Thomas.Eckardt@...] 
Sent: Thursday, May 24, 2012 11:58 AM
To: ASSP development mailing list
Subject: [Assp-test] Antwort: Re: Antwort: SSL Problems With ASSP
2.1.2.12137

>SSL worked just fine in ASSP build 12123.

build 12123 with IO::Socket::SSL 1.74 ? This should not be possible!

At least check your version of Net::SSLeay.

addition to the changelog of build 12145:

- it was possible that some SSL handshake has failed because of an 
unavailable 'ciffer' in one peer
  ASSP now supports all in the OpenSSL available ciffers. Updating
OpenSSL 
could help to prevent or to solve this
  problem. 

Thomas



Von:    "Steve Moss" <spm@...>
An:     "ASSP development mailing list"
<assp-test@...>, 

Datum:  24.05.2012 12:38
Betreff:        Re: [Assp-test] Antwort:  SSL Problems With ASSP 
2.1.2.12137



>> the latest version of this module is 1.74! <<

So what? What you appear to be saying, then, is that ASSP no longer
supports older versions of IO::Socket::SSL. Only recently, you were
saying that ASSP didn't support newer versions of it.

Oh, and the same problem exists with version 1.74 anyway.

SSL worked just fine in ASSP build 12123.

-----Original Message-----
From: Thomas Eckardt [mailto:Thomas.Eckardt@...] 
Sent: Saturday, May 19, 2012 7:25 AM
To: ASSP development mailing list
Subject: [Assp-test] Antwort: SSL Problems With ASSP 2.1.2.12137

>have IO::Socket::SSL v1.44

the latest version of this module is 1.74!

Thomas



Von:    "Steve Moss" <steve@...>
An:     <assp-test@...>, 
Datum:  18.05.2012 22:24
Betreff:        [Assp-test] SSL Problems With ASSP 2.1.2.12137



I updated from ASSP 2.1.2 build 12123 to build 12137 two days ago, and
have IO::Socket::SSL v1.44. The great majority of our legitimate emails
stopped arriving in our mailboxes, so I took at our ASSP logs and found
a large number of "Connection idle for 600 secs - timeout" errors. Over
two days, I can see over 1000 such errors. Prior to the update, the logs
show on average around 5 to 7 such errors a day.

I have now switched doTLS to 'drop TLS' and now mail is flowing again,
including mail delayed over the last two days.

There is therefore definitely a problem with ASSP build 12137, and its
interaction with IO::Socket::SSL.



------------------------------------------------------------------------
------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond.
Discussions 
will include endpoint security, mobile security and the latest in
malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************




------------------------------------------------------------------------
------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond.
Discussions 
will include endpoint security, mobile security and the latest in
malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

Hi Steve,

> That entry with any value crashes perl on my box with a memory error...

> Win2k8r2
> Perl 5.014002
> Assp 2.2.2(12145)
> Latest  CorrectASSPcfg.pm

With that entry in CorrectASSPcfg.pm

$main::delaySameIPorHelo = 3;

assp is worked without any error...

FreeBSD8.2
Perl 5.012004
Assp 2.2.2(12145)

Mike


> -----Original Message-----
> From: Thomas Eckardt [mailto:Thomas.Eckardt@...] 
> Sent: Thursday, May 24, 2012 7:33 AM
> To: ASSP development mailing list
> Subject: [Assp-test] fixes in assp 2.2.2 build 12145:

> Hi all,

> fixed in assp 2.2.2 build 12145:

> - workers were restarted or assp was dieing if the same mail from
> the same IP was delivered in two or more
>   different threads at exactly the same time
>   because it is really difficult to reproduce this mistake - this
> is the first try to solve this problem
>   For those of you, who gets attacked by spammers with such mails -
> there is a hardcoded workaround available.
>  
>   $delaySameIPorHelo = 0; # number > 0 - prevents accessing same
> storage for identical connections at the same time

>   To prevent assp from dieing on this problem, set this variable at the commandline or in the module
>   CorrectASSPcfg.pm to a value of between 2 and 5. Indentical IP's
> and/or HELO's will be delayed in processing for
>   this number of seconds.
>   Notice that this workaround could (will) be removed at any time,
> if this issue is no longer reported.
>  
> - the internal handling of the DNS query handling is improved

> - the import of the Spamdb and/or HMMdb from the rebuildspamdb thread
> (10001) has shown a wrong remaining time
>   in the log
>  

> Thomas

Mike,

please don't use this option - the workaround! Yes, it will prevent your 
assp (one of two in the world !) from running in to trouble - but I've 
tried to fix that otherwise and I need to know if this fix is working!

Thomas



Von:    Michael M Galapchuk <Michael.Galapchuk@...>
An:     Steve Moffat <Steve@...>, 
Kopie:  ASSP development mailing list <assp-test@...>
Datum:  24.05.2012 16:24
Betreff:        Re: [Assp-test] fixes in assp 2.2.2 build 12145:



Hi Steve,

> That entry with any value crashes perl on my box with a memory error...

> Win2k8r2
> Perl 5.014002
> Assp 2.2.2(12145)
> Latest  CorrectASSPcfg.pm

With that entry in CorrectASSPcfg.pm

$main::delaySameIPorHelo = 3;

assp is worked without any error...

FreeBSD8.2
Perl 5.012004
Assp 2.2.2(12145)

Mike


> -----Original Message-----
> From: Thomas Eckardt [mailto:Thomas.Eckardt@...] 
> Sent: Thursday, May 24, 2012 7:33 AM
> To: ASSP development mailing list
> Subject: [Assp-test] fixes in assp 2.2.2 build 12145:

> Hi all,

> fixed in assp 2.2.2 build 12145:

> - workers were restarted or assp was dieing if the same mail from
> the same IP was delivered in two or more
>   different threads at exactly the same time
>   because it is really difficult to reproduce this mistake - this
> is the first try to solve this problem
>   For those of you, who gets attacked by spammers with such mails -
> there is a hardcoded workaround available.
> 
>   $delaySameIPorHelo = 0; # number > 0 - prevents accessing same
> storage for identical connections at the same time

>   To prevent assp from dieing on this problem, set this variable at the 
commandline or in the module
>   CorrectASSPcfg.pm to a value of between 2 and 5. Indentical IP's
> and/or HELO's will be delayed in processing for
>   this number of seconds.
>   Notice that this workaround could (will) be removed at any time,
> if this issue is no longer reported.
> 
> - the internal handling of the DNS query handling is improved

> - the import of the Spamdb and/or HMMdb from the rebuildspamdb thread
> (10001) has shown a wrong remaining time
>   in the log
> 

> Thomas



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

Paul,

debug such a report - set 'debugNoWriteBody' to off!

Thomas




Von:    Paul Farrow <assp@...>
An:     <assp-test@...>, 
Datum:  24.05.2012 17:28
Betreff:        [Assp-test] bare lf's in reporting spam confirmation email



Hi

Just tried to report some spam (which I rarely ever have to do) to ASSP 
and I got this in the log and no confirmation of spam reported like I 
used to get.

May-24-12 11:16:05 [Worker_1] Info: report message written to -> 
/usr/local/ASSP_V2/errors/spam/Abiquo_introduction_June_7th - 
16479.rpt.eml
May-24-12 11:16:05 [Worker_1] Spam-Report: finished report-message from 
....@...
May-24-12 11:16:05 m-72565-02600 [Worker_1] [TLS-out] 127.0.0.1 [SMTP 
Reply] 250 flushed
May-24-12 11:16:05 [Worker_1] RMabort: quit Expected 250, got: 451 See 
http://pobox.com/~djb/docs/smtplf.html.
          - report to ....@...
May-24-12 11:16:05 m-72565-02600 [Worker_1] [TLS-out] 127.0.0.1 [SMTP 
Reply] 221 mail.thefabfarrows.com


I am running 2.2.1(12137) with Perl 5.014002.

Basically as you can see it has bare LF's in the message popped back. 
Do I need to just fix my reporting confirmation message or something.  I 
haven't changed any thing except for taking 2.2.1 recently.

Thanks

Paul

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************

>SSL worked just fine in ASSP build 12123.

build 12123 with IO::Socket::SSL 1.74 ? This should not be possible!

At least check your version of Net::SSLeay.

addition to the changelog of build 12145:

- it was possible that some SSL handshake has failed because of an 
unavailable 'ciffer' in one peer
  ASSP now supports all in the OpenSSL available ciffers. Updating OpenSSL 
could help to prevent or to solve this
  problem. 

Thomas



Von:    "Steve Moss" <spm@...>
An:     "ASSP development mailing list" <assp-test@...>, 

Datum:  24.05.2012 12:38
Betreff:        Re: [Assp-test] Antwort:  SSL Problems With ASSP 
2.1.2.12137



>> the latest version of this module is 1.74! <<

So what? What you appear to be saying, then, is that ASSP no longer
supports older versions of IO::Socket::SSL. Only recently, you were
saying that ASSP didn't support newer versions of it.

Oh, and the same problem exists with version 1.74 anyway.

SSL worked just fine in ASSP build 12123.

-----Original Message-----
From: Thomas Eckardt [mailto:Thomas.Eckardt@...] 
Sent: Saturday, May 19, 2012 7:25 AM
To: ASSP development mailing list
Subject: [Assp-test] Antwort: SSL Problems With ASSP 2.1.2.12137

>have IO::Socket::SSL v1.44

the latest version of this module is 1.74!

Thomas



Von:    "Steve Moss" <steve@...>
An:     <assp-test@...>, 
Datum:  18.05.2012 22:24
Betreff:        [Assp-test] SSL Problems With ASSP 2.1.2.12137



I updated from ASSP 2.1.2 build 12123 to build 12137 two days ago, and
have IO::Socket::SSL v1.44. The great majority of our legitimate emails
stopped arriving in our mailboxes, so I took at our ASSP logs and found
a large number of "Connection idle for 600 secs - timeout" errors. Over
two days, I can see over 1000 such errors. Prior to the update, the logs
show on average around 5 to 7 such errors a day.

I have now switched doTLS to 'drop TLS' and now mail is flowing again,
including mail delayed over the last two days.

There is therefore definitely a problem with ASSP build 12137, and its
interaction with IO::Socket::SSL.



------------------------------------------------------------------------
------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond.
Discussions 
will include endpoint security, mobile security and the latest in
malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
Assp-test@...
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!
*******************************************************