Header Rewrites

The Header Rewrites tab is used to rewrite headers for the Email Submitted Content. The fields available are explained in the table below:

Field Name Description

From

If defined, replaces the From: in mailings distributed to the list when the mailing has been submitted via email. If blank, the From: is the email address and name of the author of the message. In some cases, you may want to obscure the email address of the author of the message and replace it with something else.

In some cases, you may want to obscure the email address of the administrator who created the mailing and replace that address with another. For example, if several people in the sales department of your organization can contribute announcements, you may want the From: to say sales@your-company rather than the email address of the actual author. Doing so protects the original author's identity and prevents list members from contacting the author directly.

You may also use the email address of the list, if you like.

Note

This field must be a valid email address. If you do not specify a valid email address for this field, you might have problems when you try to mail. Some sites might refuse your mail, while others might show strange information in the From: field on the messages they receive

Find below examples of valid values for this field include:

bob@example.com 
Bob Smith <bob@example.com> 
bob@example.com (Bob Smith)
"Bob Smith" <bob@example.com>
"listname" <listname@yourlistmanagerserver.com>

The default when creating content or mailings is the email address of the administrator currently logged in. To change this default, modify Default To in Utilities > List Settings > Web Created Content.

Reply To:

If defined, replaces the Reply To: which the Aurea List Manager normally places in outgoing mailing list mail and replaces it with the contents of this field. If blank, the email address of the list is used. Enter author to use the email address of the message's author, or nochange to use the value of the header as received

The default setting depends on the type of list you created when using Utilities > Administration > Lists > New List to create a new list. For discussion lists, Reply To: is blank. The email address of the list is used, so that recipients of mail from a mailing list can reply back to the mailing list.

For Email Marketing and Announcement lists, the Reply To: is set to nochange which uses the value as received. When using the administrator web interface to create a message, there is no Reply To: with this setting. If you like to have a different Reply To: than the From:, specify it here

If you are using email to send messages to an Email Marketing or Announcement list, it may be useful to change this address to an in-house email address, an autoresponder, or to the unsubscribe mail merge tag %%email.unsub%% so recipients can unsubscribe easily if they try to respond to the message

Examples of valid values for this field include:

bob@example.com 
Bob Smith <bob@example.com> 
bob@example.com (Bob Smith)
"Bob Smith" <bob@example.com>
author
nochange

If you enter an invalid email address in the Reply-To: field, some mail systems may either refuse your email address or rewrite the header in unexpected ways.

To:

If specified, this address is going to be the To: message header on mail that is distributed to the mailing list. If blank, the email address of the list is entered. Enter nochange to use the value of the To: header as received

The default setting depends on the type of list you created when using Utilities > Administration > Lists > New List to create a new list.

For Email Marketing and Announcement lists, the To: is a mail merge tag which merges in the name and email address of the recipient

For discussion lists, To: is blank, and Aurea List Manager sets the To: header to be:

List Description <list-email-address> as in Jazz Discussion List <jazz@clio.lyris.net>

If you enter a value for this field which is not an email address, the mail received from Aurea List Manager may be rejected or the To: may be rewritten to something odd, depending on what the receiving email system is programmed to do with invalid email addresses

Examples of valid values for this field include:

jazz@clio.lyris.net 
Jazz Discussion List <jazz@clio.lyris.net> 
jazz@clio.lyris.net (Jazz Discussion List)
"Jazz Discussion List" <jazz@clio.lyris.net>
%%nameemail%%
%%emailaddr%%

If you want to have the To: header be the email address of each recipient, you can use the mail merge feature to accomplish this. In the To: field, enter %%emailaddr%% for the email address only, or %%nameemail%% for both name and email address

If you wanted to have a combination description/email address, you could make the To: field be:

Jazz Discussion List <%%emailaddr%%>

Remove Headers

This option allows you to explicitly remove any mail headers from mail being distributed to the mailing list. You can also remove headers that are inserted by Aurea List Manager

If headers or footers are defined at multiple levels, that is . server, site, or list, each header/footer is going to be added; one does not overwrite the other. Therefore, to remove headers or footers, you must remove them at each level in order to remove them completely

If you want to remove multiple headers, you can as many as you like, by separating each header to remove with a carriage return. For example:

Precedence
Organization 
Comments 
X-Lyris-MessageID

It searches in a case-insensitive manner for the headers you specify. If any of the headers you specify to remove are found, they are automatically removed.