Category: Uncategorized

It’s important to know your message’s spam rate before sending.

Email servers imply sophisticated technologies and spam filters to eliminate spam attacks. Very often absolutely legal emails are marked as spam. Your message may be regarded as spam, if it doesn’t correspond to email servers’ rules.

This tool analyzes the email’s source code and shows what types of corrections should you bring about to lessen the spam rate, and correspondingly to increase deliverability.

How to check emails:

1. Go to Edit or Create Campaign in web based mailing software.
2. Click “Check Spam Rate” button.

An electronic mail message consists of two components, the message header, and the message body, which is the email’s content. The message header contains control information, including, minimally, an originator’s email address and one or more recipient addresses. Usually additional information is added, such as a subject header field. Following are some common SMTP headers.

	From:	The eMail address, and optionally the name of the author(s). In many eMail clients not changeable except through changing account settings.
	To:	The eMail address(es), and optionally name(s) of the message’s recipient(s). Indicates primary recipients (multiple allowed), for secondary recipients see Cc: and Bcc: below.
	Subject:	A brief summary of the topic of the message. Certain abbreviations are commonly used in the subject, including “RE:” and “FW:”.
	Date:	The local time and date when the message was written. Like the From: field, many email clients fill this in automatically when sending. The recipient’s client may then display the time in the format and time zone local to him/her.
	Message-ID:	Also an automatically generated field; used to prevent multiple delivery and for reference in In-Reply-To: (see below).
	Bcc:	Blind Carbon Copy; addresses added to the SMTP delivery list but not (usually) listed in the message data, remaining invisible to other recipients.
	Cc:	Carbon copy; Many eMail clients will mark eMail in your inbox differently depending on whether you are in the To: or Cc: list.
	Content-Type:	Information about how the message is to be displayed, usually a MIME type.
	In-Reply-To:	Message-ID of the message that this is a reply to. Used to link related messages together.
	Precedence:	Commonly with values “bulk”, “junk”, or “list”; used to indicate that automated “vacation” or “out of office” responses should not be returned for this mail, e.g. to prevent vacation notices from being sent to all other subscribers of a mailinglist.
	Received:	Tracking information generated by mail servers that have previously handled a message, in reverse order (last handler first).
	References:	Message-ID of the message that this is a reply to, and the message-id of the message the previous was reply a reply to, etc.
	Reply-To:	Address that should be used to reply to the message.
	Sender:	Address of the actual sender acting on behalf of the author listed in the From: field (secretary, list manager, etc.).
	Return-Path:	When the delivery SMTP server makes the “final delivery” of a message, it inserts a return-path line at the beginning of the mail data. Thisuse of return-path is required; mail systems MUST support it. The return-path line preserves the information in the from the MAIL command.
	Error-To:	Indicates where error messages should be sent. In the absence of this line, they go to the Sender:, and absent that, the From: address.
	X-*	No standard header field will ever begin with the characters “X-“, so application developers are free to use them for their own purposes.

Bounce processing protects the integrity of email lists by ensuring they are clean and current. The result is higher deliverability since ISP’s regard repeated attempts to deliver to nonexistent addresses as spamming or harvesting.

For our customers convenience; our systems automatically categorized bounces into a number of different types so different actions can be taken for different bounce types.

• Blocked
  A Blocked message/recipient occurs when our system prevents a message from being sent. To identify the reason for the blocked message, either review the “Message Tracking” details or download the “Recipient Bounce Details” data file and review the “details” column. The most common cause for a blocked message/recipient is due to a Hard Bounce address or a blocked keyword. (Either of the two reports will provide all information necessary to identify the root cause)
• Hard Bounce
  A hard bounce occurs when the recipient’s mail server replies with a permanent error (typically 5xx codes), which in most cases means that the attempt to deliver to that recipient will never succeed. An example of a hard bounce error is ‘recipient@domain.com’ does not exist, which commonly occurs when a list of members has not been contacted recently.If you receive a hard bounce, you should immediately remove the recipients from any future mailings.
• Soft Bounce
  A soft bounce occurs when the recipient’s mail server replies with a transient error (typically 4xx codes), or never replies at all. An example of a soft bounce error could be caused by a server that overloaded or a user whose mailbox is full.As a general rule, if you receive 5 soft bounces for a recipient you should remove them from any future mailings.
• Grey Bounce
  Greylisting (or graylisting) is a method of defending e-mail users against spam. A mail transfer agent (MTA) using greylisting will “temporarily reject” any email from a sender it does not recognize. If the mail is legitimate the originating server will, after a delay, try again and, if sufficient time has elapsed, the email will be accepted.Unified eMail servers will automatically retry delivery after a delay.
• UBL Bounce (User Block List)
  Numerous ISPs and corporate mail systems allow individual Users to block inbound mail from select recipients or URLs within the content of the message. Bounces classified as UBLs fall into this category.
• RBL Bounce
  The message was blocked due to a sending IP address being blocked by the recipients server. This may be caused by an eMail administrator explicitly blocking the sender’s server or because the sending server’s IP is listed on a public RBL provider.
  Unified eMail monitors over 170+ public RBLs. If any of our shared or dedicated IP addresses ever shows up; our support staff works with the RBL provider to get it removed as soon as possible. Unified eMail also monitors to see if any recipient server is blocking delivery. In the event an individual recipient server blocks mail delivery; our support staff will attempt to contact the eMail administrator of the recipients domain to remove the blocking.
• Technical Bounce
  A technical issue prevented delivery of the message.
• Unclassified
  Our systems were unable to classify the bounce. (Typically the response from the recipients server was not recognized)

The following table provides the TCP Port information that you will need when setting up your eMail Clien software to communicate with our servers.
We strongly recommend that you configuration your client software to use the encrypted communcations when sending and receving eMail from our systems.

Be sure your personal and/or corporate firewalls are configured to allow communications on the desired ports listed below.

POP3 (eMail Retrieval)
POP supports simple download-and-delete requirements for access to remote mailboxes.  Although most POP clients have an option to leave mail on server after download, eMail clients using POP generally connect, retrieve all messages, store them on the user’s client device (PC, Phone, Tablet, etc) as new messages, delete them from the server, and then disconnect. (Although you can use POP with our service, we recommend using IMAP or the MAPI Connector for Outlook).

Description TCP Port # SSL/TLS

Standard POP3 (Non-Encrypted)	110	NO
Encrypted POP3 – Recommended	995	YES: SSL

IMAP (eMail Retrieval)

IMAP syncs your mail client program with the server.  eMails stay on the server, and you can make and view mail folders on the server in addition to the inbox. Most mail client program have a feature to initially sync just the eMail headers, so you can quickly see what emails you have, then download the message body when you want to read the email. Since emails stay on the server, you can see all your emails from many mail client programs or devices and our WebWeb client.  (If you are not use Microsoft Outlook which supports the MAPI protocol, IMAP is our recommended protocol)

Description TCP Port # SSL/TLS

Standard IMAP (Non-Encrypted)	143	NO
Encrypted IMAP – Recommended	993	YES: SSL

SMTP (Sending Messages)
IMAP syncs your mail client program with the server.  eMails stay on the server, and you can make and view mail folders on the server in addition to the inbox. Most mail client program have a feature to initially sync just the eMail headers, so you can quickly see what emails you have, then download the message body when you want to read the email. Since emails stay on the server, you can see all your emails from many mail client programs or devices and our WebWeb client.  (If you are not use Microsoft Outlook which supports the MAPI protocol, IMAP is our recommended protocol)

Description TCP Port # SSL/TLS

Standard SMTP (Encryption Optional via TLS)	25	YES: TLS
Standard SMTP (Encryption Optional via TLS) – Recommendation 1	2525	YES: TLS
Standard SMTP Submission Port (Encryption Optional via TLS)	587	YES: TLS
Encrypted SMTP – Recommendation 2	465	YES: SSL

Synchronization (CalDAV/CardDAV & SyncML)
CalDAV and CardDAV allows mail clients to access server hosted calendars and contacts.
SyncML is widely used as the synchronization protocl for mobile devices.

Description TCP Port # SSL/TLS

Standard Synchronization	8080	NO
Encrypted Synchronization – Recommended	8443	YES: SSL

ActiveSync and AutoDiscover (Mobile Device Sync)
ActiveSync allows a mobile device to be synchroized with the mail server.
AutoDiscover is a service that allows users to easily configure their email client knowing only their email address and password.

Description TCP Port # SSL/TLS

Standard Communications	80	NO
Encrypted Communications- Recommened	443	YES: SSL

WebMail and WebAdmin (Web Sites)
WebMail is websites that allow for accessing eMail on PC and Mobile devices.
WebAdmin is a website for uses with Admin permissiosn to manage their postoffices.

Description TCP Port # SSL/TLS

Standard Website	80	NO
Encrypted Website – Recommened	443	YES: SSL

To add an SPF record to your DNS, follow these instructions –

1. Login to cPanel Account

2. Click the “Email Authentication” button

3. Click the “Enable” button found under the SPF heading

You now have a basic SPF record setup for the domain name. Advanced users may wish to tweak it by modifying the settings below the “Enable” button.

1. Login to cPanel.
2. Click ‘Autoresponder’ under ‘Mail’ section.
3. Click Add Autoresponder to create a new auto responder.
4. Choose a character set. UTF-8 is the most common character.
5. Set the interval, in hours, you wish for the autoresponder to wait between responses to the same email address.
6. Set the email address where the response will come from.
7. Type the name and the subject you want to appear in the response, in the From and Subject text fields respectively.
8. If the response going to include HTML tags, then click to check the HTML checkbox.
9. In the Body text field, type the message of the response.
10. Select a start time. You can choose to either start responding Immediately or set a specific date and time to start from.
11. Select a stop time. You can choose to ‘Never’ stop or stop at a specific date and time.
12. Click Create to save the new auto responder.

Webmail can be used to access your email account from any computer connected to the internet.

Cpanel

To access webmail, go to http://yourdomainname.com/webmail

* Replace yourdomainname.com with your own domain.

Plesk

To access webmail, go to http://webmail.yourdomainname.com

* Replace yourdomainname.com with your own domain.

To connect to an outgoing SMTP server from a PHP script using SMTP authentication and send an email:

• Make sure the PEAR Mail package is installed.
  • Typically, in particular with PHP 4 or later, this will have already been done for you. Just give it a try.
• Adapt the example below for your needs. Make sure you change the following variables at least:
  • from: the email address from which you want the message to be sent.
  • to: the recipient’s email address and name.
  • host: your outgoing SMTP server name.
  • username: the SMTP user name (typically the same as the user name used to retrieve mail).
  • password: the password for SMTP authentication.

Sending Mail from PHP Using SMTP Authentication – Example

<?php
 require_once "Mail.php";
 
 $from = "Sandra Sender <sender@example.com>";
 $to = "Ramona Recipient <recipient@example.com>";
 $subject = "Hi!";
 $body = "Hi,\n\nHow are you?";
 
 $host = "mail.example.com";
 $username = "smtp_username";
 $password = "smtp_password";
 
 $headers = array ('From' => $from,
   'To' => $to,
   'Subject' => $subject);
 $smtp = Mail::factory('smtp',
   array ('host' => $host,
     'auth' => true,
     'username' => $username,
     'password' => $password));
 
 $mail = $smtp->send($to, $headers, $body);
 
 if (PEAR::isError($mail)) {
   echo("<p>" . $mail->getMessage() . "</p>");
  } else {
   echo("<p>Message successfully sent!</p>");
  }
 ?>

Sending Mail from PHP Using SMTP Authentication and SSL Encryption – Example

<?php
 require_once "Mail.php";
 
 $from = "Sandra Sender <sender@example.com>";
 $to = "Ramona Recipient <recipient@example.com>";
 $subject = "Hi!";
 $body = "Hi,\n\nHow are you?";
 
 $host = "ssl://mail.example.com";
 $port = "465";
 $username = "smtp_username";
 $password = "smtp_password";
 
 $headers = array ('From' => $from,
   'To' => $to,
   'Subject' => $subject);
 $smtp = Mail::factory('smtp',
   array ('host' => $host,
     'port' => $port,
     'auth' => true,
     'username' => $username,
     'password' => $password));
 
 $mail = $smtp->send($to, $headers, $body);
 
 if (PEAR::isError($mail)) {
   echo("<p>" . $mail->getMessage() . "</p>");
  } else {
   echo("<p>Message successfully sent!</p>");
  }
 ?>

Overview

Sending bulk or high volume email presents unique challenges for businesses, ISPs and email hosting companies. To accommodate bulk email sending, MMS provides several SMTP options including shared, semi-dedicated and dedicated hosting services.

High volume SMTP Features:

• DKIM Signing
• Sender Policy Framework (SPF)
• Simple Integration with your application

Your Application, Our SMTP

Unlike typical email marketing services, our high volume SMTP hosting service lets you send from your own application server, email client or a combination of different sources. For distributions of several thousand to greater than 1,000,000 messages per month, our high volume services are highly scalable and competitively priced.

Becoming a Client

In accordance with our Zero Spam Tolerance Policy, MMS’s bulk email hosting is a tightly regulated service. Clients are expected to responsibly manage ISP abuse reports and follow CAN-SPAM guidelines. In addition, MMS researches potential clients and performs extensive due diligence to prevent abuse.

SMTP Pricing

Shared IP

	Sends per month	Monthly Price	Order Now
Plan 1	100,000	$65
Plan 2	250,000	$75
Plan 3	500,000	$120
Plan 4	100,0000	$200

1. One Dedicated IP (free ip replacement if become blacklist).
2. RDNS.
3. Domain Keys.
4. SPF Records.

* Actual monthly price for dedicated IP varies depending on burst sending requirements, hardware configuration, and SMTP volume.

Are you looking for free email lists to send email marketing promotions? please click on live chat we help you with that.

We can send unlimited emails to our subscribers for you. We have authorization from our subscribers that we can send them weekly promotions about any product or service.

All you need is to buy our any solo email marketing plan and we will send emails to our subscribers once a week.