1 Topic by nadams

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

Topic: Bug in greylisting

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version (check /etc/iredmail-release): 2.6.1
- 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
- Related log if you're reporting an issue: https://gist.github.com/nadams810/a6523 … 1b0671c113
====

I had a complaint that an email bounced. From the logs it looks like whoever setup the email system at sbcglobal.net set it to send email out from a number of email servers. I haven't looked at the source for greylisting but I imagine it might consider the email server itself which will not work for sbcglobal emails.

Would the best action to be just whitelist (for greylisting) sbcglobal.net ? If so that might be good as a default entry.

----

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: 31,088

Re: Bug in greylisting

If you're running iRedAPD for greylisting service, just whitelist this domain with iRedAdmin-Pro:

System -> Anti Spam -> Greylisting -> Do not apply greylisting on emails sent from domains listed below

3 Reply by nadams

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

Re: Bug in greylisting

ZhangHuangbin wrote:

If you're running iRedAPD for greylisting service, just whitelist this domain with iRedAdmin-Pro:

System -> Anti Spam -> Greylisting -> Do not apply greylisting on emails sent from domains listed below

I did that already - however what I'm suggesting is that should be added by default in a new install (or by an update) to ensure new/current users don't have issues in receiving emails from sbcglobal.net.

nadams's Website

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Bug in greylisting

I cannot even access www.sbcglobal.net (returns error message on index page). Would you mind introducing this to help me understand whether it's worth to whitelist it in default iRedMail setting?

5 Reply by nadams

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

Re: Bug in greylisting

ZhangHuangbin wrote:

I cannot even access www.sbcglobal.net (returns error message on index page). Would you mind introducing this to help me understand whether it's worth to whitelist it in default iRedMail setting?

sbcglobal was gobbled up by AT&T (a large communications/ISP provider in the US) many years ago and for some reason they offer it as an email domain for it's residential customers. But it shouldn't matter what they have on their homepage - they have valid MX records:

:~# dig sbcglobal.net MX

; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> sbcglobal.net MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32957
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;sbcglobal.net.                 IN      MX

;; ANSWER SECTION:
sbcglobal.net.          300     IN      MX      10 ff-ip4-mx-vip1.prodigy.net.
sbcglobal.net.          300     IN      MX      10 al-ip4-mx-vip1.prodigy.net.
sbcglobal.net.          300     IN      MX      10 ff-ip4-mx-vip2.prodigy.net.
sbcglobal.net.          300     IN      MX      10 al-ip4-mx-vip2.prodigy.net.

;; AUTHORITY SECTION:
sbcglobal.net.          14400   IN      NS      ns1.attdns.com.
sbcglobal.net.          14400   IN      NS      ns3.attdns.com.
sbcglobal.net.          14400   IN      NS      ns2.attdns.com.
sbcglobal.net.          14400   IN      NS      ns4.attdns.com.

nadams's Website

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Bug in greylisting

That makes sense. I added this domain in iRedAPD by default.
https://bitbucket.org/zhb/iredapd/commi … 7b2e0f0388

Thanks for the feedback. smile