1

Topic: Greylisting implementation in iRedMail

Is greylisting implemented in iRedMail able to discern if the same server try's to send mail at another point in time?

Better put if a server sends mail for the first time to a iRedMail server it is greylisted by default. If the message is successfully delivered will mail from the same server still be greylisted next time that it trys to send mail (for example the next day or the next week)?

----

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

2

Re: Greylisting implementation in iRedMail

My tests show that iRedMail appears to whitelist a server after it passes the greylist test. Would like to have a better understanding of the implementation of greylisting in iRedMail and be sure of the conclusion since the test was a small sample.

Additionally Gmail or Hotmail for example may send from many different servers (server1.hotmail.com, server2.hotmail.com). Is the greylisting domain based/ip based/ ect?

3

Re: Greylisting implementation in iRedMail

*) Greylisting is offered by software Cluebringer in iRedMail.
*) Based on IP.

References:

http://greylisting.org
http://wiki.policyd.org/greylisting

4

Re: Greylisting implementation in iRedMail

The only issue I have found with greylisting is that, very occasionally, mail can get stuck in loop if the sender domain uses multiple sending servers on different IP's. If the sender has a round-robin approach to the sending server then the greylisting refuses delivery of the 1st; 2nd; 3rd IP's and by the time the 1st server tries again the greylisting refuses again due to the length of time since the first try.
This issue has only been very occasional - it also affect the Barracuda hosted spam service we use for work email too.

ZhangHuangbin - if you have a backup MX specified that doesn't use greylisting but your primary server does use greylisting - is there a simple way to stop connecting servers from immediately delivering to the backup mx when the primary mx refuses during the greylisting period?

Thanks for a great mail server btw smile any thoughts on a docker app?

5

Re: Greylisting implementation in iRedMail

For that last part, a CRON Job on the Backup MX to check whether the primary is alive and if it is then close port 25 via IPTables or similar. The only downfall is that you may miss some e-mails if the sender cannot access the Primary for some legitimate reason, but the Backup MX Rejects it. This would happen without a backup MX anyway.

6

Re: Greylisting implementation in iRedMail

blackisle wrote:

ZhangHuangbin - if you have a backup MX specified that doesn't use greylisting but your primary server does use greylisting - is there a simple way to stop connecting servers from immediately delivering to the backup mx when the primary mx refuses during the greylisting period?

It sounds like a sender-side issue, not yours. no idea.

blackisle wrote:

any thoughts on a docker app?

We're lack of man-power. If you're interesting in build a Docker app, i'm willing to offer help.

7

Re: Greylisting implementation in iRedMail

It could be a sender-side issue but its also how Spammers get around a Greylist, they send to Backup MXes which have less security and often allow Spam to get in without facing a Greylist