1 Topic by ale-freetime

  • ale-freetime
  • Member
  • Offline
  • Registered: 2012-10-09
  • Posts: 8

Topic: IredApd - GreyList

==== Required information ====
- iRedMail version 0.9.6
- Linux/BSD distribution name and version:  Debian
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  MySql
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Is it possible to setup greylist to accept connections after retry timeout not on recipient based, but server/domain based?
Now greylist operates like in this example : (sender ip address is always the same)
- <sender> <recipient1> -> Greylist

- greylist timeout expires

- <sender> <recipient2> ->  Greylist
- <sender> <recipient3> ->  Greylist
- <sender> <recipient1> -> Pass

Thanks

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,788

Re: IredApd - GreyList

This model doesn't make much sense to me.

If MTA running on sender server will retry message delivery normally, then it will pass greylisting. So it doesn't make much sense to do this.