GroupMail

GroupMail > Tools

Manage Accounts > New

Account Properties

Name / User Infomation:
fill in the form with your company’s data

Delivery Options

Delivery Options: Standard

SMTP Server: rsxxx-realsender.com
[x] Requires Authentication

[setup]

Authentication Settings

[x] Use SMTP Authentication (outbound)

Type: AUTH LOGIN (Default)

Username: (the one we sent you)

Password: (the one we sent you)

[OK]

Advanced Email Settings

SMTP Port: 25

[x] Server requires an SSL connection

Use: STARTTLS (default)

[OK]

Inxmail Professional

Global Settings > Administration

> Mail Server > Sending Emails

Mail account settings

Name: rsxxx.realsender.com

SMTP mail server: rsxxx.realsender.com - Port: 25

Max. connections: 3

[x] Authentication
User name: (the one we sent you)
Password: (the one we sent you)

[x] Activate TLS, if possible

[Save]

[Activate connection to the mail server account]

Joomla AcyMailing

Joomla > Components

AcyMailing > Configuration

Sender Information

fill in the form with your company’s data

Mail Configuration

Mailer Method: SMTP Server

SMTP Configuration

Server: rsxxx.realsender.com
Port: 465
Secure Method: SSL

Keep Alive: [x] Yes
Authentication: [x] Yes

Username: (the one we sent you)
Password: (the one we sent you)

MaxBulk Mailer

[Settings]

Settings

Connections: 2

SMTP server access

SMTP host: rsxxx.realsender.com - TLS v1 EXP

Authentication: ESMTP - Plain

Account ID: (the one we sent you)

Password: (the one we sent you)

Delivery: [x] Singly (recommended)

Group mail: All at once

Sender information

From: (the sender email address)

Name: (the sender description)

[Save new account as…]

Name: rsxxx

[Create]

phplist

Configuration tested on:
phplist, version 3

Attention: make a backup copy before making
any changes on your phplist server configuration files
phplist config

Fill phplist/htdocs/config/config.php
with the correct data:

[…]
define(‘PHPMAILERHOST’, ‘rsxxx.realsender.com’);
[…]

define(‘PHPMAILER’,1);
define(‘PHPMAILER_SECURE’,‘TLS’);

$phpmailer_smtpuser = 'the one we sent you'; $phpmailer_smtppassword = ’the one we sent you’;
$phpmailer_smtpport = 587;

$pageroot = ‘/’;

SendBlaster

Messages > Send

Send settings:

Send mode: [x] Use SMTP server

SMTP Server: rsxxx.realsender.com
Port: 25 - [x] SSL

[x] Authentication required

Username: (the one we sent you)
Password: (the one we sent you)

[Take snapshot]

Sendy

Sendy


Select a brand > [Add a new brand]

New brand

Brand name

From name

From email

Reply to email

(fill the form with the list name and your company’s data)

SMTP settings

Host: rsxxx.realsender.com

Port: 587

SSL / TLS: TLS

Username: (the one we sent you)

Password: (the one we sent you)

[Save]

WordPress MailPoet 3

WordPress

MailPoet > Settings

Basics > Default sender
(fill the form with your company’s data)

From:
Company Name - newsletter (description)
newsletter@company-name.org (email address)

Reply-to
Company Name - marketing (description)
marketing@company-name.org (email address)

[Save settings]

Send With…

[x]  Other

Send emails via your host (not recommended!)
or via a third-party sender.

[Configure]

Send With…

Method: SMTP

Sending frequency: Recommended
(100 emails every 5 minutes. That’s 28.800 emails per day)

SMTP Hostname: rsxxx.realsender.com

SMTP Port: 587

Login: (the one we sent you)

Password: (the one we sent you)

Secure connection: TLS

Authentication: [x] Yes

[Save settings]

For Premium features and support, on the Mailpoet pricing page
choose the “I just want the Premium with no sending” option.

In this way you can continue to use RealSender,
combining it with a dedicated email address to receive the bounces.

The “Bounce Handler Mailpoet” plugin will also have to be installed.

Bounce Handling

Bounce Email:
Please set a single dedicated bounce address for bounce email

WordPress MailPoet 2

WordPress

MailPoet > Settings

Basics

Email notifications:
fill with the proper email address

Sender of notifications:
fill with the newsletter’s
FROM name and email address

[Save settings]

Send With…

[x] Third party

SMTP Hostname: rsxxx.realsender.com

Login: (the one we sent you)

Password: (the one we sent you)

SMTP Port: 587

Secure connection: TLS

Authentication: [x] Yes

Send… 60 emails every minute

[Save settings]

WordPress MailPress

WordPress > Plugins

MailPress > Settings

General

From - All Mails sent from:
fill in the form with the sender’s email address and name

if it’s your first MailPress setup
you must press [Save Changes]
to see the additional settings options (SMTP, Test, Logs)

SMTP

SMTP Server: rsxxx.realsender.com
Username: (the one we sent you)
Password: (the one we sent you)

Use SSL or TLS ? TLS

Port: Use for SSL/TLS/GMAIL

WordPress Mailster

WordPress

Settings > Newsletter

General

From Name:

From Email:

Reply-to Email:

(fill the form with your company’s data)

[Save Changes]

Delivery Method

[SMTP]

SMTP Host : Port rsxxx.realsender.com : 587

Timeout: 10 seconds

Secure connection: [x] TLS

SMTPAuth: Plain

Username: (the one we sent you)

Password: (the one we sent you)

[Save Changes]

Bounces

Bounce Address:
Undeliverable emails will return to this address

newsletter mailboxes

To receive the bounced messages generated by sending newsletters and mass mailings,
you need to setup additional mailboxes (e.g. bounce@…)

and optionally one mailbox for receiving reply emails (e.g. news@…)
if you want to filter them and send automatic replies to the most common requests.

For this reason we introduced two mailboxes matched to your RealSender account:
bounce@email.youremaildomain.com -> bounce@rsXXX-realsender.com
news@email.youremaildomain.com -> news@rsXXX-realsender.com

Explanation:

Using a Mail-From address (also known as bounce/return-path/envelope address)  
with a domain other than the From address
would break the DMARC authentication

To use the "newsletter mailboxes" 
you need to set up a sub-domain of the From address

e.g.  the From address is:           offers@youremaildomain.com
      the sub-domain could be:       email.youremaildomain.com   CNAME   rsXXX-realsender.com
      the Mail-From address becomes: bounce@email.youremaildomain.com

The suggested configuration follows the rules
to send DMARC compliant emails on behalf of customers.

DMARC allows you to send authenticated emails using a sub-domain (such as email.youremaildomain.com), and still be able to use the top-level domain in the From: header (e.g. From: offers@youremaildomain.com).

No additional settings are required in the DNS of your domain name.

As per RFC1912 section 2.4:
 A CNAME record is not allowed to coexist with any other data.  
 In other words, if email.youremaildomain.com is an alias for rsXXX-realsender.com, 
 you can't also have an MX record for email.youremaildomain.com, or an A record, 
 or even a TXT record 

The mailboxes have been configured so that they can receive
large amounts of emails in a short time, as in the case of bounces.
!!! Please note: email messages are automatically deleted after 7 days !!!

To download the emails, you should configure your email client,
or the application that analyzes the bounced messages,
with the following POP3 server address: pop.rsXXX-realsender.com.
Usernames and passwords are available through the website’s restricted area.

list-unsubscribe with block

The automatic blocklist

The “bouncehandler” app automatically checks for unsubscribe requests
and blocks new emails from recipients who have requested not to receive future emails.

The “unsubscriptions” blocklist is activated:
it contains all the email addresses that have requested unsubscribe
via the “List-Unsubscribe” function, as described above.

the weekly log of all “unsubscriptions” is available at the web address:
https://…unsubs.email.weekly

Sending messages to a recipient on the blocklist will result in an error like this:

Manage your blocks independently

We provide you with the following files,
as web addresses, protected by password or IP address:

https://…unsubs.json
the details of unsubscribe requests received in the last seven days, in JSON format, such as:

  {
    "mailbox": "rsXXX",
    "id": "20241121T181856-0088",
    "from": "Jonh Doe <john.doe@bogusemail.net>",
    "to": [
      "<abuse@rsXXX-realsender.com>"
    ],
    "subject": "RealSender :: rsXXX Nov-1 4ALGbKtb016000 :: please UNSUBSCRIBE me ::",
    "date": "2024-11-21T18:18:56.908809804+01:00",
    "posix-millis": 1732209536908,
    "size": 4057,
    "seen": false
  },

https://…unsubs.email
the list of email addresses that have requested unsubscription in the last seven days

This is the same files used by the automatic blocklist:

https://…unsubssfull.email
the list of all email addresses that requested unsubscription, in alphabetical order

automatic bounce management

Repeated sending to incorrect/inactive recipients is considered “spammer behavior.”

RealSender’s “copymail” app handles this automatically and transparently.
The receiver will only see the original sender, who will continue to receive replies from the recipients.

Email messages contain a header that remains invisible to the recipient. It’s called “Return-Path” and allows error messages to be sent to another email address.
Copymail automatically populates it with valuable information that, in addition to allowing them to be received, will also allow it to determine which list the message was sent from and which email address generated the error.

Below is an example of the header inserted in a message,
sent from the “test” list to the recipient "wrong.address@customer.com":
Return-Path: <test-bounces+wrong.address=customer.com@mXXX-realsender.com>

The application identifies two types of errors:
hard bounce (status-code 5.XXX.XXX): the email address generated a permanent error
such as “550 5.1.1 … User unknown” or “5.1.2 … Host unknown”
A permanent error indicates that you should never send to that recipient again.

soft bounce (status-code 4.XXX.XXX): the email address generated a temporary error
such as “452 4.2.2 … Mailbox full”
A transient error indicates that you can retry delivery in the future.

Here’s a brief description of how automatic bounce management works:

1. After three hard bounces (permanent error, e.g., “user unknown”) or six soft bounces (temporary error, e.g., “mailbox full”), the recipient is blocked and a checkmark is added under the “nomail” column in the subscriber list.

2. Once the recipient is blocked, three “Your subscription to the list … has been disabled” messages are sent before the recipient is removed from the list.

3. When the recipient is removed from the list, the administrator receives an email notification.

Note: Only one error per day affects the subscriber’s score, so even if ten bounces are received in the same day, the score will only increase by one.

All these operations may seem simple and manageable even manually by an operator.
This is only possible with very small numbers, up to a few hundred recipients.

On average, about 20% of sent messages are bounced back.
For every 1,000 emails, about 200 are bounced,
which become unmanageable without the help of an automated system.

unsubscribe management

1. The use of automated calling and communication systems without 
human intervention (automatic calling machines), facsimile machines (fax) 
or electronic mail for the purposes of direct marketing may be allowed 
only in respect of subscribers or users who have given their prior consent.

2. Notwithstanding paragraph 1, where a natural or legal person obtains 
from its customers their electronic contact details for electronic mail, 
in the context of the sale of a product or a service, in accordance with 
Directive 95/46/EC, the same natural or legal person may use these electronic 
contact details for direct marketing of its own similar products or services 
provided that customers clearly and distinctly are given the opportunity 
to object, free of charge and in an easy manner, to such use of electronic 
contact details at the time of their collection and on the occasion of each 
message in case the customer has not initially refused such use.

-- Unsolicited communications, extract from Article 13 of Directive 2002/58/EC

This rule, now outdated, is still used as a basis of principle. In short:

1. The recipients must have requested to receive messages
2. The only exception is if they are already a customer, and even then
   they must always be given the option to unsubscribe

Beyond the legal implications, failure to comply with these simple rules essentially leads to being labeled a “spammer.” The damage caused can even lead to the inability to reach even those recipients who wish to receive your communications.

RealSender’s “copymail” app provides a link to an “options” page for unsubscribing from each list,
which the customer can include in email messages. Here’s an example:

After completing the form, the entered address will receive an email
inviting them to click the link to confirm the cancellation:

We have received a request ... for the removal of your email
address, ... from the ... mailing list.  To confirm that you want
to be removed from this mailing list, visit this web page:
(http address for unsubscription confirmation)

This same message is sent to those requesting unsubscription
via the “List-Unsubscribe: …” header, which is automatically inserted into every email sent.

This header allows webmail applications like Gmail to activate the “Unsubscribe” link
directly in the interface, without requiring the user to search for it in the message.

To be notified of all unsubscribes made independently by recipients, it is recommended
to activate the notification feature to the administrator’s email address
from the “General Options” of the list: