Many ISPs are now blocking port 25 outbound from end users to prevent spam from their network. A new standard is to use port 587 and setup Plesk to listen on port 587.
To setup Outlook to do this
Outlook should now use port 587 for sending mail.
If your AtMail search is not working, you can apply the following fix to lines 364 and 369:
sed -i 's/20$BeforeYear/$BeforeYear/g' /var/www/atmail/search.php sed -i 's/20$AfterYear/$AfterYear/g' /var/www/atmail/search.php
This fixes a bug in the search.php file for AtMail 1.04 and 1.05.
Re: How we deal with SPAM for email forwarding
We have changed the way we deal with spam for all emails managed by our parked domain services. External services such as Google/Gmail, Hotmail, AOL are constantly tightening their incoming email requirements and so in an effort to minimise false positives further, we have applied the following features:
1) We have modified the score for Spam Assassin to eliminate false positives.
2) We have activated Spam Assassin for all emails. This includes incoming mail for mailboxes, out going mail for mail boxes and emails forwarded to external destinations.
3) Email determined to be SPAM by Spam Assassin is no longer quarantined but will continue to be forwarded (or delivered if you have a Mailbox) with the addition of the text “[SPAM]” added to the subject header.
4) The Spam Assassin headers will remain intact for all forwarded email. This will show the receiving mail server that we have already evaluated the email and marked the score. The receiving mail server may perform additional checks.
5) Google’s Gmail policy states that even if email arrives that they determine is spam, it will still be delivered as long as the text “SPAM” is included in the email subject header. See Best practices when forwarding to Gmail for more information.
6) These changes are only relevant to parked domain services (microlite1) and are not relevant to our Plesk hosting services.
If you see an email with [SPAM] in the subject header this just means that this MAY be spam, it is down to you to decide as it is impossible to know for sure on an automated basis. Other than the subject header change the email will be treated normally as with any other email. The modification of the subject header will ensure that all emails are delivered to your external services.
As always, if you have any questions do not hesitate to contact the support teams.
The sender mail server has no reverse DNS entry. You can verify the reverse DNS setting here: Check rDNS
The reverse DNS of your IP Address is typical of a dynamic/residential IP Address. Please have it updated to something unique like mail.example.com, or use the mail servers your ISP provides for residential customer traffic.
rDNS must be in the form of a fully-qualified domain name. rDNS containing in-addr.arpa are not acceptable, as these are merely placeholders for a valid PTR record. rDNS consisting of IP addresses are also not acceptable, as they do not correctly establish the relationship between domain and IP address.
rDNS that may be similar to dynamic IP space (containing pool, dhcp, dyn, etc.) may be treated as suspect, and should therefore should be changed to reflect a fully-qualified domain name with standard reverse DNS.
Re: Forwarded emails not arriving, no bounce message
Many free email services such as Gmail, AOL, Hotmail (and ISPs) are constantly tightening up their spam systems and are being increasingly particular about which emails they allow in to their system.
If you find that forwarding email to one of these addresses is simply ‘disappearing’, ie. no bounce message then you can be safe in assuming that your email alias (address) is temporarily blocked from the target mail system.
Why does this happen?
Let’s assume you are doing all the right things. ie Your SPF record is correctly set, your MX records are correct.
When forwarding emails from your parked domain name, you are also forwarding SPAM to your destination email address. If you send enough SPAM messages then you will block your own alias. Often the block is only in place for a limited time, for example 24 hours. Then it will start working again and once you have forwarded enough SPAM the block is re-applied. Does this sound like the problem you are experiencing?
What can you do?