1

Topic: BUG in graylisting

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5.1
- Linux/BSD distribution name and version: Debain Jessie
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:
====

My iredapd.log is flooded with lines like this:
2016-05-24 20:10:05 INFO * <<< ERROR >>> Cannot insert new record for domain <foo.bar>: (1213, 'deadlock found when trying to get lock; try restarting transaction')

Why do I see this?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: BUG in graylisting

It seems to be related to spf_to_greylist_whitelists.py as the log lines appear just after:
2016-05-25 01:20:01 INFO * Query SQL server to get mail domain names.
2016-05-25 01:20:01 INFO * Parsing domains, 38 in total.
2016-05-25 01:20:01 INFO     + [amazon.com]
2016-05-25 01:20:01 INFO     + [aol.com]
2016-05-25 01:20:02 INFO     + [aol.com]
......

3

Re: BUG in graylisting

mir wrote:

2016-05-25 01:20:01 INFO     + [aol.com]
2016-05-25 01:20:02 INFO     + [aol.com]

Please check root's cron job, do you have duplicate jobs to run spf_to_greylist_whitelists.py?

4

Re: BUG in graylisting

ZhangHuangbin wrote:

Please check root's cron job, do you have duplicate jobs to run spf_to_greylist_whitelists.py?

Nice catch.
I have made a copy/paste error so consider this a bug 40 ;-)

Suggestion. Since the script obviously does not like to run in parallel there might should be a check for an already running instance?

5

Re: BUG in graylisting

mir wrote:

Suggestion. Since the script obviously does not like to run in parallel there might should be a check for an already running instance?

No.