1 Topic by nadams

  • nadams
  • Member
  • Offline
  • Registered: 2014-04-19
  • Posts: 24

Topic: greylisting not working right

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

It seems like every domain is hitting greylisting - even the ones that are specified in the white list. In this specific example the SPF record for members.wayfair.com does correctly state 162.208.32.171 and 162.208.32.165 as valid mail servers. Please note I adjusted the greylisting message manually to help me identify when greylisting is happening.

Jun 23 17:33:31 mail1 postfix/smtpd:  NOQUEUE: reject: RCPT from sv11.members.wayfair.com[162.208.32.171]: 451 4.7.1 <REMOVED>: Recipient address rejected: Greylisting in effect - please come back later; from=<bounces@members.wayfair.com> to=<REMOVED> proto=ESMTP helo=<sv11.members.wayfair.com>
Jun 23 17:33:38 mail1 postfix/smtpd:  NOQUEUE: reject: RCPT from sv05.members.wayfair.com[162.208.32.165]: 451 4.7.1 <REMOVED>: Recipient address rejected: Greylisting in effect - please come back later; from=<bounces@members.wayfair.com> to=<REMOVED> proto=ESMTP helo=<sv05.members.wayfair.com>
Jun 23 17:33:39 mail1 postfix/smtpd:  NOQUEUE: reject: RCPT from sv05.members.wayfair.com[162.208.32.165]: 451 4.7.1 <REMOVED>: Recipient address rejected: Greylisting in effect - please come back later; from=<bounces@members.wayfair.com> to=<REMOVED> proto=ESMTP helo=<sv05.members.wayfair.com>

----

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

nadams's Website

2 Reply by ZhangHuangbin

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

Re: greylisting not working right

Seems you're running Cluebringer for greylisting service, not iRedAPD. Could you please show us output of commands below:

postconf smtpd_recipient_restrictions
postconf smtpd_end_of_data_restrictions

3 Reply by nadams

  • nadams
  • Member
  • Offline
  • Registered: 2014-04-19
  • Posts: 24

Re: greylisting not working right

ZhangHuangbin wrote:

Seems you're running Cluebringer for greylisting service, not iRedAPD. Could you please show us output of commands below:

postconf smtpd_recipient_restrictions
postconf smtpd_end_of_data_restrictions
:~# postconf smtpd_recipient_restrictions
smtpd_recipient_restrictions = reject_unknown_recipient_domain reject_non_fqdn_recipient reject_unlisted_recipient check_policy_service inet:127.0.0.1:7777 permit_mynetworks permit_sasl_authenticated reject_unauth_destination
:~# postconf smtpd_end_of_data_restrictions
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:7777

If I am using cluebringer - then why is the greylisting message the one I specified in /opt/iredapd/settings.py ?

GREYLISTING_MESSAGE = "Greylisting in effect - please come back later"

nadams's Website

4 Reply by nadams

  • nadams
  • Member
  • Offline
  • Registered: 2014-04-19
  • Posts: 24

Re: greylisting not working right

Any ideas?

nadams's Website

5 Reply by ZhangHuangbin

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

Re: greylisting not working right

nadams wrote:

If I am using cluebringer - then why is the greylisting message the one I specified in /opt/iredapd/settings.py ?

This makes sense, i didn't realize you're using custom message.
Please upgrade to the latest iRedAPD-2.1 (released today), and check this issue again.