In an effort to combat the effects of spam email on our customers, BlueTie has implemented several new email rules and restrictions. Stringent rules are being applied industry-wide and in following this trend, we hope to decrease the amount of spam coming into the system by applying the following rules and by identifying the predictable behavior and system specifications that spammers use.
The SPAM score is used to provide a statistical average to monitor and properly place emails coming in frequently from specific addresses. This service has been put in place to help prevent false-positives.
When a BlueTie interface user flags a message as Junk, by either using the Flag as feature or dragging the message to the Junk folder, the IP address of the sending server is recorded in BlueTie’s Complaint Table and may be blacklisted by BlueTie servers
In order to be blacklisted by BlueTie’s servers, the following criteria must be met:
Please note that the email sender will receive a bounceback message from the BlueTie servers.
Prior to delivering email to our customers, BlueTie performs a reverse lookup on the ‘From’ address of the sending mail server. This reverse IP lookup cannot be blank, it must resolve to a hostname. For example, BlueTie’s sending server response to a reverse IP lookup would be mail.bluetie.com.
- Reverse DNS lookup failures are temporary and will result in a temporary error bounceback while the server retries to send the messages sending servers will typically generate the first temporary error bounceback to the sender after 4 hours. Please note that this timeframe is configurable per server.
- The sending server will generate a permanent bounce after the retry timeframe has expired (this timeframe is also configurable, but is generally 5-7days), the sending server will generate a bounceback message stating that a permanent error has occurred and that the message was not delivered.
Resolution: If a sender should receive a bounceback stating that a temporary or permanent failure has occurred “450 4.7.1 Client host rejected: cannot find your reverse hostname” the administrator for that server should be contacted and a valid hostname should be given to the sending server.
When sending email to BlueTie, the sending mail server must respond to a preliminary ‘handshake’ from the BlueTie servers with a Fully Qualified Domain Name (FQDN.) The FQDN identifies the server & domain name. For example, BlueTie’s sending mail server’s FQDN reads outbound1.bluetie.com.This restriction helps to reduce incoming spam, as most spamming machines do not identify themselves with a FQDN.
Resolution: If a sender should receive a bounceback message with this error referenced, the administrator for that server should be contacted and the FQDN should be updated to current RFC standards.
Any user sending out of the BlueTie SMTP service, must use a valid email address/alias. The following error will be received if the proper authentication is not used:
Error: 553 <tester@yahoo.com>: Sender address rejected: not owned by user tester@bluetie.com
A valid address is defined as an address or alias that is found in the BlueTie system. Any address that is used to send mail from a mail client (such as Outlook) must also be found on the username that is using SMTP authentication. This can be verified in the user aliases section which is accessible via the Enterprise Manager.
To regulate traffic, throttling rules are applied to both inbound and outbound messages.
Inbound Threshold
Outbound Threshold