website

Tag Archive for 'smtp server'

10 Reasons to Choose a Professional SMTP Service

Our users know very well that SendBlaster supports any SMTP servers in the world.
Standard (free) SMTP servers are good if you manage small email lists. For example Google Gmail allows sending up to 250 daily messages using its SMTP.

If you manage to send thousands of newsletters to your large email list through your standard SMTP server, they may never arrive in your recipients’ inboxes.  Why? Because Internet Service Providers (ISPs) often limit the number of messages a sender can send at once while also aggressively filtering incoming messages.  Dedicated SMTP servers solve these problems. Below are 10 compelling reasons to switch to a dedicated SMTP service provider:

  1. Improved Deliverability – ISPs do their part to eradicate spam by blacklisting IP addresses. Dedicated SMTP service providers work with major email providers to ensure that the dedicated SMTP server remains whitelisted.
  2. Easy Setup – Setting up a professional SMTP service is a simply matter of modifying your email client’s SMTP settings.
  3. Ease of Use – Sending thousands of messages in small batches to get around volume limits is tedious and time consuming. With a dedicated SMTP server, you can send thousands of bulk email messages with a single click from within your email client software.
    Continue reading ’10 Reasons to Choose a Professional SMTP Service’

How To Configure SendBlaster With The Right Advanced Settings

Today we focus our attention on the Advanced Settings section in SendBlaster, which allows users to fine-tune the sending timing, and other special settings. Obviously, to get the right advanced settings it is necessary to try out different combinations and verify how many messages actually get delivered. To simplify the settings, some Suggested settings are available. Please consider that they might not be optimized for your connection but they can be considered a good starting point to find out the best configuration.
Users connected to a “tolerant” enough SMTP server will probably not experience many problems, regardless of the settings specified that will only affect the sending speed.
On the other hand, if your connection is to a rather “strict” STMP server and if a large number of messages need delivered, it may be necessary to slow down message sending to avoid sending messages simultaneously.
Here are a few simple rules to consider:

  • A tolerant SMTP server allows fast sending without any, or with only limited, pauses. On restricted SMTP servers that use multiple anti-spam filters, more pauses and fewer simultaneous connections should be used.
  • SMTP servers do not usually allow the simultaneous sending of many messages. Therefore when sending in SMTP mode the number of connections must be low or, in certain situations, equal to 1 (no simultaneous connections). If the SMTP server is equipped with anti-spam restriction mechanisms, it may be necessary to slow down message sending by setting a pause of a few seconds between each send, and by setting a longer pause between message blocks. Blocks should not contain more than a few dozen messages.
  • In the case of a Direct Send, with a standard distribution list containing addresses belonging to different domains, the messages will be delivered to a variety of different servers. It is therefore possible to set a high number of connections* and limited or no pauses between messages and between blocks.
  • Continue reading ‘How To Configure SendBlaster With The Right Advanced Settings’

How to complete previous mailings…and work around SMTP server restrictions

Today we focus on a particular feature of SendBlaster that could be more useful than you think! We’re talking about partial deliveries and how to resume them.

Do you know that every time you start sending emails you can stop them manually (clicking the ‘Abort’ button during the sending operation) and then resume them in a single click?
Actually this is a simple and effective way to work around SMTP server restrictions applied for controlling automated spam messages. The average SMTP service, which usually comes bundled with your Internet connection might limit the maximum number of recipients per message or maximum number of messages per server connection, and may vary from time to time depending on server load and other factors.

For example if you use a SMTP server that does not allow sending more than 50 messages per hour and a distribution list with 100 email addresses, only the first half will go through during the first attempt. In this case the operation can be completed after a one-hour wait right from the History windows.

Let’s see how to use this cool feature:

Continue reading ‘How to complete previous mailings…and work around SMTP server restrictions’




Load Times Plugin made by Cheap Web Hosting