MailHop Outbound Readme
Important information to know about MaiHop Forward
- Relays
- Message Size
- Multiple Recipients
- Intended Use, Limits, Mailing Lists and Spam
- Client-side Virus Scanning
- 421 Temporary Local Error and Sender Verification
Relays
The MailHop Outbound service is sold in blocks of 150 "relays," or available outgoing emails per day. For example, if you purchase three MailHop Outbound blocks, you can send up to 450 messages daily. The MailHop Outbound counter is reset every morning at 12:00am UTC (see http://www.worldtimeserver.com/current_time_in_UTC.aspx).
If you reach the cap, you will not be able to send additional emails through MailHop Outbound until the counter is reset or you purchase additional blocks. Our server will return temporary failure messages notifying you of the problem. Because you cannot send more messages than you are alloted, we do not charge overage fees.
Message Size
MailHop Outbound can send messages up to 50MB in size. Messages larger than 10MB count for multiple relays, as described in the chart below:
| Message Size | Multiplier |
|---|---|
| 10MB - <20MB | 2 |
| 20MB - <30MB | 3 |
| 30MB - <40MB | 4 |
| 40MB - <50MB | 5 |
| Exactly 50MB | 6 |
Multiple Recipients
To prevent potential abuse of our services, MailHop Outbound is limited to 100 recipients per message. If you have a large mailing list, you should break the list down into blocks of 100 recipients apiece, or configure your sending client to send individual messages to each recipient.
Intended Use, Limits, Mailing Lists and Spam
MailHop Outbound is most helpful to individual users, small groups and small to medium-size companies for personal communications. It is not intended for large corporations, automated messages (such as forum notifications or confirmation emails), or mailing lists such as advertising and newsletters. We have a very strict standing on spam, and take all complaints very seriously and will deactivate your account if you receive several complaints.
If you purchase several MailHop Outbound blocks, we will hold your invoice and contact to verify your usage. We are also currently limiting the number of MailHop Outbound blocks you may have in your account.
If you have a mailing list, such as a newsletter, and intend to distribute this list through MailHop Outbound, you must be very careful to comply with both anti-spam etiquette and law, such as opt-in policies, opt-out instructions, and other procedures as required by the US CAN-SPAM act and our Acceptable Use Policy.
If you have any questions about what may or may not be allowed, please contact our support team for more information.
Client-side Virus Scanning
If you use virus scanning software and notice that your relay count is nearly double your actual usage, you may wish to disable the email scanning function; some utilities such as Norton AV cause every sent message to be counted twice. Norton's outgoing email scanning may also prevent SSL from working correctly. Since our MailHop Outbound service scans outgoing messages with ClamAV, additional client-side scanning is usually redundant, so you should disable the email scanning feature of your anti-virus if you encounter this issue.
421 Temporary Local Error and Sender Verification
Customers may occasionally receive a 451 Temporary Local Error when attempting to send email through MailHop Outbound. This error usually indicates that sender verification failed. Sender verification is when our server checks to make sure the sending address uses a valid domain, which prevents spammers from sending mail from nonexistent domains. The most common causes of sender verification failure for valid domains are typos in the sending address (e.g. "user@domian.com" instead of "user@domain.com") or DNS resolution failure.
If you receive this error, but your domain appears to resolve correctly and your sending address is correctly spelled, please contact our support team for further help. You can check your sending domain's resolution using our DNS Query Tool.