WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mydomain.com claims to be host server.myhost.com [but that host is at xxx.xxx.66.2 (may be cached), not xxx.xxx.66.3]
Code: ; Modified by Web Host Manager ; Zone File for mydomain.com $TTL 14400 @ 86400 IN SOA ns1.myhost.com. root.server.myhost.com. ( 2006081304 7200 7200 1209600 86400 )
mydomain.com. 86400 IN NS ns1.myhost.com. mydomain.com. 86400 IN NS ns2.myhost.com.
mydomain.com. 14400 IN A xxx.xxx.66.3
localhost.mydomain.com. 14400 IN A 127.0.0.1
mydomain.com. 14400 IN MX 0 mydomain.com.
mail 14400 IN CNAME mydomain.com. www 14400 IN CNAME mydomain.com. ftp 14400 IN A xxx.xxx.66.3
mydomain.com. 14400 IN TXT "v=spf1 include:optonline.net ~all"
I always have customers complaining not receiving emails from my online store.
While checking with dnsreport, I found the following:
Quote:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.shashinki.com claims to be non-existent host mail.shashinki.com: 220-mail.shashinki.com ESMTP Exim 4.66 #1 Thu, 12 Jul 2007 10:51:20 +0800 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
I have my own dedicated server.
How can I correct the above so that ISP will not treat mails sending from my servers as spam and deleted them without sending to my customers?
Problem: I am using to my Centos/Exim/Cpanel server to relay emails. The person who receives my email sees a helo that captures my ISP IP address and lastly the mail server for my domain along with its IP.
My ISP (Verizon) IP is constantly being flagged as a spam source by a variety of RBL's.
My domains have never sent spam and I only send a low volume of emails.
How can I remove my ISP helo IP address from being added to my outgoing email so that the only IP is the IP of domain sending the email?
Example Header:
Quote:
Received: from c-99-172-221-252.hlvd.va.verizon.net ([99.172.221.252]:3389 helo=[127.0.0.1]) <-- remove this part by server.myserver.com with esmtpa (Exim 4.69) (envelope-from <email@mydomain.com>) id 1MLoYc-0004Ol-20 for friend@hotmail.com; Tue, 30 Jun 2009 21:24:18 -0400
I am on a VPS and set everything up myself. When I try and email a friend, I get it bounced back with the following message (with his email filtered):
<<< 550-5.7.1 {mx078} Sorry, your helo has been denied. <<< 550 5.7.1 [url] 550 5.1.1 <**********@gmx.co.uk>... User unknown
I'm pretty sure the user isn't unknown, I have checked and it is his email address. Can anyone tell me what is wrong, and if the problem is on my end or his, and if my end how I might go about fixing it?
!verify = helo !verify = reverse_host_lookup in exim acl and drop message if helo is not passed. But one issue is this validates for users even having account in the server and trying to send mail using server account to someone else
I want to put validation for only incoming mails "to" this server
What i dont want is to validate the mails that authenticated smtp users send
I have a dedicated linux/cpanel server running various websites with the shared ip and one website with a dedicated ip.
But when sending mail through sendmail from the dedicated ip website the ip in the helo greeting is not matching the ip of the sender, it is using the main shared ip rather than the dedicated ip which is producing a 550 error from some receiving mail servers. I have racked my brains trying to figure this out and was wondering if anyone else has/had a similar experience and found a solution.
By the way the helo greeting sent in mail from the shared ip websites is fine...
I seem to be having a problem with domain forwarding in cPanel.
I have 3 cPanel accounts:
1) foobar.com.np with a POP3 account and forwarders for info@foobar.com.np. Works fine.
2) foobar.com with domain forwarding to foobar.com.np. Works fine too when I send an email to info@foobar.com.
3) foo.com.np with domain forwarding to foobar.com.np. Doesn't work! When I send a message to info@foo.com.np I get the following message in my Exim log:
Code: 2007-11-29 04:11:32 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1IxgMm-0007DW-0m 2007-11-29 04:11:32 1IxgMm-0007DW-0m ** info@foo.com.np R=lookuphost T=remote_smtp: SMTP error from remote mail server after MAIL FROM:<noreply@********.com> SIZE=2059: host foo.com.np [74.86.*.*]: 554 5.7.1 Helo invalid(forged) 2007-11-29 04:11:32 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <> -E1IxgMm-0007DW-0m 2007-11-29 04:11:32 1IxgMm-0007Da-Bd <= <> R=1IxgMm-0007DW-0m U=mailnull P=local S=2006 T="Mail delivery failed: returning message to sender" 2007-11-29 04:11:32 1IxgMm-0007DW-0m Completed ... As you can see, this domain forwarder is not functioning like the other one (foobar.com) since the domain forwarder for foobar.com DOES actually work:
Code: 2007-11-29 03:58:21 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1IxgA0-0002Gs-Vb 2007-11-29 03:58:21 1IxgA0-0002Gs-Vb => info <info@foobar.com> R=virtual_user T=virtual_userdelivery 2007-11-29 03:58:22 1IxgA0-0002Gs-Vb => *******@gmail.com <info@foobar.com> R=lookuphost T=remote_smtp H=gmail-smtp-in.l.google.com [209.85.133.27] 2007-11-29 03:58:22 1IxgA0-0002Gs-Vb -> *******@gmail.com <info@foobar.com> R=lookuphost T=remote_smtp H=gmail-smtp-in.l.google.com [209.85.133.27] 2007-11-29 03:58:22 1IxgA0-0002Gs-Vb Completed It looks like Exim doesn't know that emails sent to info@foo.com.np should be a local delivery. I checked the file "/etc/vdomainaliases/foo.com.np" and it says:
Im trying to troubleshoot the exim install that was included with cpanel. I read that the helo response being localhost instead of a fully qualified domain can lead to mail be directed to the bulk mail folder.
Looking at the mail headers, this is indeed set this way:
Received: from www.mydomain.com ([my_ip_addr] helo=localhost)
How is this response determined and how can I have it be a fully qualified domain name instead?
#Server PHP - hosts php and handles apache/mysql requests. #Server 2 - handles mail and dns requests.
Yesterday we moved mail from # server 2 to a new mail server, a cPanel one, all mailboxes are created, users can send and recieve email using webmail, mail clients, etc.
But.. while trying to send mails using PHP authenticated from the #Server PHP/Apache/MySQL , we got this error from the mail servers:
Code: We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. SMTP -> FROM SERVER: SMTP -> FROM SERVER: SMTP -> ERROR: HELO not accepted from server: SMTP -> get_lines(): $data was "" SMTP -> get_lines(): $str is "220-srv247.serverhost.com This was working when mails were recieved/sent in Sendmail (an Ensim box), now with Exim 4.x on a cPanel box we got this issue.
Already added IP address from #server php into all Exim whitelists, also added the IP to /etc/alwaysrely, but didn't help.
Im using RHE 5.2 on the mail server and latest Release build.
I formatted my server and installed CENTOS 7 and PLESK 12. I have problems with cbl.abuseat.org. My ip enters in blacklist. I sent email to the support of abuseat.org and abuseat reply:
Please fix your HELO strings.
I check the my configuration and I think is correct:
- Reverse lookup is ok - Hostname is ok (server.domain.tld)
But I have the file in /etc/sysconfig/network empty. There is only written: # Created by anaconda
Also, is correct the my etc/hosts file?
127.0.0.1 server.domain.tld server localhost4 localhost4.localdomain4 :: 1 server.domain.tld server localhost6 localhost6.localdomain6
I've been plagued by CBL listing for quite some time now, on a linux server with Plesk 12.After months of a fierce fight against every possible malware on the about 120 various websites on this server, extensively monitoring clients emails, enabling restrictive policies and finally even hiring a private security firm to investigate the problems further, we were sure that not a single spam message was sent by our server in any way.
So we finally contacted CBL, exposed the issue and got this answer:The CBL attempts to detect compromised machines in a number of ways based upon the email that the CBL's mail servers receive.During this it tries distinguish whether the connections represent real mail servers by ensuring that each connection is claiming a plausible machine name for itself (via SMTP HELO), and not listing any IP that corresponds to a real mail server (or several mail servers if the IP address is a NAT firewall with multiple mail servers behind it). 54.194.XX.XXX was found to be using several different EHLO/HELO names during multiple connections on or about:
The names seen included: xxx1.xx, xxx2.xx, xxx3.xx, xxx4.xx, xx.xxx5.xx, veniceberg.com..Note that the above list may include one or more names that are not fully qualified DNS names (FQDNs). Host names (ie: Windows node names) without a dot are not FQDNs.
The final possibility is that 54.194.XX.XXX is not a NAT firewall, and is instead a single box with many domains provisioned on it, some that send email directly, setting the HELO as the sending domain. If this is the case, to prevent a relisting we strongly recommend setting the mail software on the box so that a single identifying name is used in outbound SMTP connections mail software on the box so that a single identifying name is used in outbound SMTP connections. As an alternate workaround, you can configure the mail software to relay its outbound email through an intermediate mail server. Even a co-resident mail server package (such as IIS on Windows) will do fine.
This pointed me to this Plesk Mail setting (not sure if this selection is the default). Now we are waiting a few days to see if changing to "Send from domain IP addresses" solves the issue. I think this is a kind of issue which deserves attention by Parallels to avoid other users go trough our fatiguing ordeals. If this setting is responsible for getting servers blacklisted, it should be highly discouraged.
Seems this started when upgrading to a version of 12. It was working a few days ago and only seems to affect mailing lists. I found a google Cached thread here where Igor was assisting some folks as late as Aug 4 and referenced this was "reported to development (PPP-10678 for your reference)" it seems the forums on Parallels changed or something because several Google links are not working and resulting in having to used cached results for the two links below.
I am able to disable SPF and the e-mails go through just fine however this was working with SPF enabled before a recent upgrade.
Page 1 [URL] ....
Page 2 [URL] ....
This is the error message displayed in /var/log/maillog Sep 24 01:38:35 controlpanel postfix/smtpd[3725]: connect from localhost[127.0.0.1] Sep 24 01:38:35 controlpanel postfix/smtpd[3725]: D565017C013E: client=localhost[127.0.0.1] Sep 24 01:38:35 controlpanel greylisting filter[3899]: Starting greylisting filter...
I am looking at a VPS of one friend, using OpenVZ. It has 256MB RAM, but it always goes down, and the host asks my friend to upgrade to larger RAM. I have read that if UBC setting is too low, the VPS could not use all allocated RAM, not sure if it's correctly or not, but is there anyway to check?
I have it installed on server, but sometimes it's dead, but no warning from system. It will prevent emails working then. So I wonder if there is any way to check clamav? when it's not working, system will release an email to the admin?
I'm on shared hosting (apache) and would like to closer inspect my log files. 2 questions I have at the moment.
1. Where can I typically find my log files for downloading?
2. Is there any good (free) software I can use locally (Windows desktop) that can manage these logs i.e. stats, searches etc? At the moment I mainly want to run a search on the log files.
Is there a way to track outgoing mail that's sent from a Linux server? I'm running on Fedora 8 now, and would like to confirm and check mail that's being sent out by a PHP application.
Which both seem to be for blacklisted email servers. But what about checking if the ip has been blacklisted for other reasons ( business practices, reports of complaint, adult sites, etc)
What is a decent check?
This is for checking on newly assigned dedicated ip's ( or other) before applying them to domains on a new account.