Page 1 of 1

Another error in softbounce.log

Posted: Fri Aug 30, 2013 2:33 pm
by Fatalin
Hi,

We have an error in our softbounce.log file, that we don't understand:
[30.08.2013 03:00:02] 11641 INFO/main: Starting up
[30.08.2013 03:00:02] 11641 INFO/kill: Remove old addresses from softbounce_email_tbl
[30.08.2013 03:00:02] 11641 INFO/kill: Removed 0 address(es)
[30.08.2013 03:00:02] 11641 INFO/collect: Updated timestamps
[30.08.2013 03:00:03] 11641 INFO/collect: Read 1 records (1 uniques) and inserted 0
[30.08.2013 03:00:03] 11641 INFO/collect: Timestamp updated
[30.08.2013 03:00:03] 11641 INFO/merge: Working on 1
[30.08.2013 03:00:03] 11641 FATAL/except: CAUGHT EXCEPTION:
Traceback (most recent call last):
File "/home/openemm/bin/scripts/softbounce.py", line 167, in <module>
data = scurs.querys (squery, parm, cleanup = True)
File "/home/openemm/bin/scripts/agn.py", line 2054, in querys
for rec in self.query (req, parm, cleanup, rtype):
File "/home/openemm/bin/scripts/agn.py", line 2017, in query
self.curs.execute (req, parm)
File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 159, in execute
query = query % db.literal(args)
TypeError: not enough arguments for format string
From the other log files it appears, that the graylisting is not detected / processed correctly, because no graylisting shows in the logs (but it should). Additionally we get a large number of softbounces. This number seams to correspondent with the missing number graylistings.

Can anyone help?

Thanks
Markus

Re: Another error in softbounce.log

Posted: Mon Sep 02, 2013 8:45 am
by ud
There is only a limited support for graylisting detection; in this case the bounce is ignored and not explicit recorded. All others are recorded as softbounce (if matching the remaining rules for softbounces), so all bounces from graylisting, which are not identified by the available logic is counted as softbounce.

-- ud

Re: Another error in softbounce.log

Posted: Tue Sep 03, 2013 10:54 am
by Fatalin
Hi ud,

I am not quite sure I understand what you want to say.
Graylisting works fine on our OpenEMM 6.2 installation. Just not on the OE2013. And we can't find the reason yet.

Markus