Hi Thomas,
This version is not starting up at all:
Not enough arguments for Net::SMTP::DESTROY_SSLNSNot enough arguments for
Net::SMTP::assp_starttls at sub main::init line 311, near ()
at assp.pl line 6286.
Met vriendelijke groet / best regards,
Pascal Dreissen
applemooz
On 30 Nov 2014,
I spotted this one last night and it is to do with Net::SMTP::SSL version.
CPAN has version 1.01 of Net::SMTP::SSL and ASSP will not work with this.
Sourceforge has 1.02 so you need to download this to ASSPdir/lib/Net/SMTP
http://assp.cvs.sourceforge.net/viewvc/assp/assp2/lib/Net/SMTP/SSL.pm
It looks like this depends on the installed version of Net::SMTP - I'm
sorry.
download and try 2.4.4 build 14335
Thomas
Von:Pascal Dreissen pas...@applemooz.nl
An: ASSP development mailing list assp-test@lists.sourceforge.net
Datum: 01.12.2014 09:46
Betreff:Re: [Assp-test]
Thomas Eckardt wrote:
- fixes a thrown exception
Prototype mismatch: sub Net::SMTP::assp_starttls (-1) vs none at sub
Net::SMTP::assp_starttls line 28.
I was hoping this would address my SMTP STARTTLS problem, unfortunately
it did not.
Doug
--
Ben Franklin quote:
Those who would give
Hi.
I'm testing this feature in my test environment.
no sure what i should see but when i set SessionLog to verbose in addition
to normal log I see only a lot of:
Dec-01-14 12:35:50 m1-33747-02917 [Worker_1] [TLS-out] [PTRinvalid]
199.103.5.118 sen...@out.com to: m...@mydomain.com info: Maillog -
log-condition is zero
This means, that you don't collect all files - for this type of files
'nocollect' is set.
Thomas
Von:aquilinux aquili...@gmail.com
An: ASSP development mailing list assp-test@lists.sourceforge.net
Datum: 01.12.2014 12:58
Betreff:Re: [Assp-test] fixes
Hi Thomas,
This one one of the things I noticed the other day although I
misunderstood the logs then. I have every single collection option set
because I want everything collected so no mail goes missing bar redlist.
For that reason I do have DoNotCollectRedRe, DoNotCellectRedList and
2014-11-28 11:47:07 [Worker_1] matchSL - sen...@domain.tld
mailto:sen...@domain.tld - noCollecting
this is a debug output - means matchSL checks sen...@domain.tld for
noCollecting
if a match is found - it would be logged (see regexLogging)
log-condition is zero
shows that the logging
I woke up this morning to find ASSP down and no mail flowing. Build
14334 was failing due to the Net::SMTP::SSL issue already mentioned - I
reverted back to build 14331.
However, when trying to diagnose the issue, I opened my log files and
found them absolutely filled - gigabytes of log files,
set 'SessionLog' to standard
Thomas
Von:Scott MacLean a...@hollsco.com
An: ASSP Development Mailing List assp-test@lists.sourceforge.net
Datum: 01.12.2014 14:09
Betreff:[Assp-test] Two problems last night
I woke up this morning to find ASSP down and no mail flowing. Build
On Mon, Dec 1, 2014 at 1:05 PM, Thomas Eckardt thomas.ecka...@thockar.com
wrote:
This means, that you don't collect all files - for this type of files
'nocollect' is set.
On my production servers i have no collect only for:
*NonSpamLog *
*baysNonSpamLog*
*noProcessingLog*
all the others
O yeah ... - my mistake - sorry.
used a numerical (... == 0) instead of (... eq '0') for the parameter
check. To prevent the large amount of log lines set 'SessionLog' to
'standard'.
fix comes today.
Thomas
Von:Scott MacLean a...@hollsco.com
An: ASSP Development Mailing List
All my logging settings. All either okmail, spam, notspam, quarantine or
discard folder. So I do in fact have them all set to collect.
NonSpamLog:=2
baysNonSpamLog:=4
SpamLog:=1
noProcessingLog:=4
npAttachLog:=6
wlAttachLog:=6
extAttachLog:=6
SpamVirusLog:=5
spamBombLog:=1
scriptLog:=1
your MTA does not answer after it got the
.[CR][LF]
this should be
.[CR][LF]
1. 26-11-2014 16:33:23 [Worker_1] SMTPTraffic - read OK
2. 26-11-2014 16:33:23 [Worker_1] SMTPTraffic - process read
3. 26-11-2014 16:33:23 [Worker_1] doing line 250 2.0.0 Ok: queued
as
yes... yes ... yes Colin - my mistake ! fix follows today.
Thomas
Von:Colin colin.war...@gmail.com
An: assp-test@lists.sourceforge.net
Datum: 01.12.2014 15:08
Betreff:Re: [Assp-test] fixes in assp 2.4.4 build 14331
All my logging settings. All either okmail, spam, notspam,
On Dec 1, 2014, at 9:15 AM, Thomas Eckardt thomas.ecka...@thockar.com wrote:
your MTA does not answer after it got the
The MTA (Postfix) shows:
Dec 1 07:45:13 web postfix/smtpd[31547]: 72E162008D7CD:
client=assp.drdos.info[10.10.10.247], sasl_method=PLAIN,
lost connection after DATA (5571 bytes) from
assp.drdos.info[10.10.10.247]
assp debug was
26-11-2014 16:30:51 [Worker_1] SMTPTraffic - no more data -
In this case ASSP lost the connection to the client. If the client
connection is lost for any reason - assp closes the connection to the MTA.
Maybe I need to read up on tcpdump.
trace the connection between the client and assp.
The client being the end user or the Mail Server?
If the end user, this is happening on all of them, including my test laptop on
a MiFi wireless service. If that's the case, maybe it's my firewall. I'm
The client being the end user or the Mail Server?
the client
I'm currently using pfSense 2.1.5
IMHO one of the best you can have. So you may trace using the buildin
pfSense trace (packet capture) function.
Thomas
Von:Doug Lytle supp...@drdos.info
An: ASSP development mailing
Hi Thomas,
thanks for your reply. I’am now back from work and see that you have fixed
everything.
I jump for joy and want to give a treat. It’s running again with your fixes in
14336.
BIG THANKS
Please tell me for future diagnostics how to run interactive.
I thought with ./assp.pl -i
20 matches
Mail list logo
