HELO argument
HELO argument
Started to get a lot of rejected mails today, even Google was involved:
550 5.7.0 HELO argument [mail-ua0-f181.google.com] is missing a DNS entry. See http://spamauditor.org/best-practices/r ... dentifier/ for more information. Protection provided by MagicSpam 2.0.16-1 http://www.magicspam.com
550 5.7.0 HELO argument [mail-ua0-f181.google.com] is missing a DNS entry. See http://spamauditor.org/best-practices/r ... dentifier/ for more information. Protection provided by MagicSpam 2.0.16-1 http://www.magicspam.com
Re: HELO argument
Hello etcnet,
Thank you for your post.
Our team is aware of this issue and is currently investigating it. In the meantime, could you please send us over the DNS server(s) that your system uses?
Also can you please check and see if queries for HELO strings that are detected as spam properly resolves from your MagicSpam system?
Feel free to disable the following policy in your MagicSpam if it is preventing your customers from receiving emails from valid senders until this issue is fully resolved:
Confirm Server Identification Resolves (HELO)
Rule Name: resolve_helo_domain
Lastly could you please let us know following information about your system:
- Operating System and Version
- Operating System Architecture (32 bit or 64 bit)
- Plesk Version
- MTA (Qmail, Postfix, Exim)
Please let us know if you have any questions in the meantime.
Thank you for your post.
Our team is aware of this issue and is currently investigating it. In the meantime, could you please send us over the DNS server(s) that your system uses?
Also can you please check and see if queries for HELO strings that are detected as spam properly resolves from your MagicSpam system?
Feel free to disable the following policy in your MagicSpam if it is preventing your customers from receiving emails from valid senders until this issue is fully resolved:
Confirm Server Identification Resolves (HELO)
Rule Name: resolve_helo_domain
Lastly could you please let us know following information about your system:
- Operating System and Version
- Operating System Architecture (32 bit or 64 bit)
- Plesk Version
- MTA (Qmail, Postfix, Exim)
Please let us know if you have any questions in the meantime.
-- MagicSpam Support Team --
Re: HELO argument
Hi
Amount of HELO rejections increased dramatically.
Now disabled the resolve_helo_domain rule
our dns servers ns1.etcnet.fi, ns2.etcnet.fi, ns3.etcnet.fi, ns6.gandi.net
We're running
CentOs 7 64 bit
Plesk Onyx 17.8.11
mailserver Postfix (IMAP Dovecot)
Amount of HELO rejections increased dramatically.
Now disabled the resolve_helo_domain rule
our dns servers ns1.etcnet.fi, ns2.etcnet.fi, ns3.etcnet.fi, ns6.gandi.net
We're running
CentOs 7 64 bit
Plesk Onyx 17.8.11
mailserver Postfix (IMAP Dovecot)
Re: HELO argument
Hello etcnet,
Thank you for the update.
We have passed this information to our development team and will follow up with you once we have more information.
Thanks you again for reporting this issue with us.
Thank you for the update.
We have passed this information to our development team and will follow up with you once we have more information.
Thanks you again for reporting this issue with us.
-- MagicSpam Support Team --
-
- Posts: 3
- Joined: Thu May 17, 2018 2:39 am
Re: HELO argument
Hi,
I have the same problem on 4 VPS...
CentOs 7 64 bit
Plesk Onyx 17.5.3 Update #47 x 1
Plesk Onyx 17.8.11 Update #7 x 3
Mailserver Qmail (IMAP Dovecot)
Magic Spam 2.0.16-1 Free Edition
Thank you
I have the same problem on 4 VPS...
CentOs 7 64 bit
Plesk Onyx 17.5.3 Update #47 x 1
Plesk Onyx 17.8.11 Update #7 x 3
Mailserver Qmail (IMAP Dovecot)
Magic Spam 2.0.16-1 Free Edition
Thank you
Re: HELO argument
Hello zsozso1982 and etcnet,
Thank you for providing us additional information.
In order to continue troubleshooting this issue, could you please send us the output of the following command:
nslookup <helo domain> <your dns server>
Please do this for all your DNS servers and let us know.
Thank you for your patience and your assistance in troubleshooting this issue.
Thank you for providing us additional information.
In order to continue troubleshooting this issue, could you please send us the output of the following command:
nslookup <helo domain> <your dns server>
Please do this for all your DNS servers and let us know.
Thank you for your patience and your assistance in troubleshooting this issue.
-- MagicSpam Support Team --
-
- Posts: 3
- Joined: Thu May 17, 2018 2:39 am
Re: HELO argument
Hi.
Thi is the nameserver, in the resolv.conf:
nslookup ctb.wakelitenet.com 79.143.183.251
Server: 79.143.183.251
Address: 79.143.183.251#53
Non-authoritative answer:
Name: ctb.wakelitenet.com
Address: 193.34.145.41
nslookup ctb.wakelitenet.com 213.136.95.11
Server: 213.136.95.11
Address: 213.136.95.11#53
Non-authoritative answer:
Name: ctb.wakelitenet.com
Address: 193.34.145.41
This is the nameserver, that I use for the server's main domain:
nslookup ctb.wakelitenet.com pdns1.registrar-servers.com
Server: pdns1.registrar-servers.com
Address: 2620:74:19::33#53
Name: ctb.wakelitenet.com
Address: 193.34.145.41
Thi is the nameserver, in the resolv.conf:
nslookup ctb.wakelitenet.com 79.143.183.251
Server: 79.143.183.251
Address: 79.143.183.251#53
Non-authoritative answer:
Name: ctb.wakelitenet.com
Address: 193.34.145.41
nslookup ctb.wakelitenet.com 213.136.95.11
Server: 213.136.95.11
Address: 213.136.95.11#53
Non-authoritative answer:
Name: ctb.wakelitenet.com
Address: 193.34.145.41
This is the nameserver, that I use for the server's main domain:
nslookup ctb.wakelitenet.com pdns1.registrar-servers.com
Server: pdns1.registrar-servers.com
Address: 2620:74:19::33#53
Name: ctb.wakelitenet.com
Address: 193.34.145.41
Re: HELO argument
Hello zsozso1982,
Thank you for the post.
Based on the rejection message in your initial post, the HELO argument that has triggered the policy is mail-ua0-f181.google.com; could you please use this argument for your query and let us know the results:
e.g.
nslookup mail-ua0-f181.google.com <your dns server>
Thank you,
Thank you for the post.
Based on the rejection message in your initial post, the HELO argument that has triggered the policy is mail-ua0-f181.google.com; could you please use this argument for your query and let us know the results:
e.g.
nslookup mail-ua0-f181.google.com <your dns server>
Thank you,
-- MagicSpam Support Team --
-
- Posts: 3
- Joined: Thu May 17, 2018 2:39 am
Re: HELO argument
Hi. There is the problem... I'm moving to another DNS provider... I think this will be solve my problem. Thank you!
nslookup mail-ua0-f181.google.com pdns1.registrar-servers.com
;; Got SERVFAIL reply from 2620:74:19::33, trying next server
Server: pdns1.registrar-servers.com
Address: 2620:74:19::33#53
** server can't find mail-ua0-f181.google.com: NXDOMAIN
nslookup mail-ua0-f181.google.com pdns1.registrar-servers.com
;; Got SERVFAIL reply from 2620:74:19::33, trying next server
Server: pdns1.registrar-servers.com
Address: 2620:74:19::33#53
** server can't find mail-ua0-f181.google.com: NXDOMAIN
Re: HELO argument
Hello zsozso1982,
Thank you for the update.
If you have any further issues please do not hesitate to let us know.
Thank you for the update.
If you have any further issues please do not hesitate to let us know.
-- MagicSpam Support Team --
Who is online
Users browsing this forum: No registered users and 3 guests