 |
|
|
|||
|
The DNS changes necessary to allow Marvin to process your mail are usually not seen simultaneously for everyone on the Internet. DNS has a caching feature that allows DNS servers to remember the information they get about a domain for a period of time. The amount of time other servers are supposed to retain this information is known as the "time to live", or TTL. Every domain has a TTL value associated with it, that tells other DNS servers how long they can remember the information for. When DNS changes are made, some servers will see the changes immediately, and others may take as long as the value defined for the domain's TTL. If the TTL is set to two days, then it will take up to two days for most servers on the Internet to see the change. This means that during those two days, some of your mail will go through Marvin (since some servers will see the change immediately), and some mail will continue to go directly into your mailserver. ...back to top... The first two addresses listed (yourdomain.com.mx.marvin.sihope.com
and After Marvin processes the mail, it looks up the MX records for your domain to see where the mail should be delivered. When you sign up with Marvin, you provide the IP addresses of your mail servers, so Marvin knows where to deliver your mail. Since the Marvin servers can resolve the first two addresses, they will send the mail to your mailserver. If your mailserver is unreachable for some reason, Marvin will queue the mail and try to re-deliver the mail at another time....back to top... The first two addresses listed (yourdomain.com.mx.marvin.sihope.com
and The SMTP specification in RFC 2821 says, "To provide reliable mail transmission, the SMTP client MUST be able to try (and retry) each of the relevant addresses in this list in order, until a delivery attempt succeeds." Since much of the software spammers use is poorly written, and is designed for speed and not reliable mail delivery, this MX configuration prevents a lot of spam from even getting to the Marvin servers. Most modern SMTP implementations correctly adhere to RFC 2821 and have no problems delivering mail to Marvin-enabled domains....back to top... How to tell if Marvin processed a message: If you receive an e-mail and want to determine if it went through Marvin, you can look at the headers of the message to see if the Marvin servers are listed. The headers contain routing information that describes the path a message took to get from the sender to your mailbox. Most e-mail programs have a way to view the full headers of a message. Every mail server that handles an e-mail message adds a Received line to the message that contains information such as the message ID, the server name and address, the date and time of when it received the message, and the address of the server it got the message from. If Marvin handled the message, there will be Received lines that contain the server name "marvin.sihope.com"....back to top... How to block mail from all servers other than Sihope: Once all of your mail is going through Marvin, rather than your own mail server, you may decide to only accept SMTP connections from the Marvin servers. By rejecting connections from any other servers, your mail servers are protected from a spammer or hacker finding them and trying to abuse them. You can configure your firewall to only accept SMTP connections from the Marvin
servers. If you don't have a firewall, most mail servers can be configured
to only allow connections from specific addresses. Contact Sihope for
the current list of addresses used by the Marvin servers....back to top... |
||||||||||||||||||||||||||||||||||||||||||
>>
Log In
>> Support Links