larger smaller normal text version of this page
Phplist Documentation Message functions


Message Forwarding



You can invite your newsletter readers to send a copy of the newsletter to someone he knows that might be interested in the same information. The way it works is like this:

Placeholders
In an email you can use two Placeholders, either [FORWARD] or [FORWARDFORM]

The latter is only useful for HTML email. [FORWARD] will add a link to the email that goes back to the website to fill out a little form, enter an email and it will send the related newsletter to the email, as if it is from the user who is forwarding.

[FORWARDFORM] adds the email entry box to the HTML email, and points back to the site as well to do the actual forwarding.
In the configuration, there is a new option which is the "footer" of a forwarded email, that will be used in case of forwarding, instead of the normal footer. This footer can contain [SUBSCRIBE] to point the person who receives the forwarding to the place where they can sign up to the mailing lists.

Formatting of the form in the email can be done using the CSS classes:

.forwardform -> formtag
.forwardinput -> input box
.forwardsubmit -> submit button

Issues
- Placeholders will be replaced by nothing, if the user does not exist in the database. This is why it is advisable to promote this clearly over using the forward button of the mail program. No attributes of the forwarding user can accidentally be disclosed.
- Users who it is forwarded to are not added to the database (and won't either)
- If sending fails, the error is "forwarding failed", but no extra information to avoid data mining.
- Currently it's only logged that something has been forwarded, but it is not remembered by user or anything.
- If click tracking is enabled, it will not be enabled for forwarded messages, as it is user dependent and would therefore fail, because the user doesn't exist.

In 2.10.6RC1 the following optional behavior has been added:

Keep sender attributes
When forwarding ('to a friend') the message will be using the attributes of the destination email by default. This often means the message gets stripped of al its attributes. When setting a config value to 1, the message will use the attributes of the forwarding user. It can be used to connect the destinatory to the forwarder and/or reward the forwarder. Warning: attributes of the forwarding user can be disclosed to his friend this way.

Send to multiple emails
You can allow to enter more than one friend. A setting defines how many email addresses you can enter in the forward page. Default is 1 to not change behaviour from previous version. This maximum is counted per day.

Personal message
You can allow user to prepend a personal note when forwarding 'to a friend'. The note is prepended to both text and html messages and will be stripped of all html

With everything switched on it looks like this:
image image

In 2.10.6RC2 the following optional behavior has been added:

Proper headers maintaining the "chain of custody"
That is, the first (chronologically, so the last one in the header) "Received : " field will show that the communication was initiated by someone else, in this case the person that decided to forward it. An example of this idea can be found at http://www.spamcop.net/fom-serve/cache/369.html .

Blacklisting possibility for unknown addresses
{domain}/lists/?p=blacklist will ask for email and then blacklist this email even if not in db
{domain}/lists/?p=blacklist&email=test@test.tst will ask the same way with the email prefilled
In case of forwarding both [BLACKLIST] and [UNSUBSCRIBE] will be translated to
<a href="{domain}lists/?p=blacklist&email=test@test.tst">{'this link' in chosen language}<a/>,
[BLACKLISTURL] and [UNSUBSCRIBEURL] will be translated to {domain}lists/?p=blacklist&email=test@test.tst

Friend counter aka Lead Reference Scheme aka Viral marketing
When the string constant FORWARD_FRIEND_COUNT_ATTRIBUTE is not empty (see your config.php file) and an attribute with that name exists, the
total count of all succesfull handovers to the MTA (mails sent, not receive with certainty) will be saved in that
attribute.


This block in config.php:

#0011857: forward to friend, retain attributes
# When forwarding ('to a friend') the message will be using the attributes of the destination email by default.
# This often means the message gets stripped of al its attributes.
# When setting this constant to 1, the message will use the attributes of the forwarding user. It can be used
# to connect the destinatory to the forwarder and/or reward the forwarder.
define("KEEPFORWARDERATTRIBUTES",0);

#0011860: forward to friend, multiple emails
# This setting defines howmany email addresses you can enter in the forward page.
# Default is 1 to not change behaviour from previous version.
define("FORWARD_EMAIL_COUNT",1);

#0011996: forward to friend - personal message
# Allow user to add a personal note when forwarding 'to a friend'
# 0 will turn this option off. default is 0 to not change behaviour from previous version.
# 500 is recommended as a sound value to write a little introductory note to a friend
#The note is prepeded to both text and html messages and will be stripped of all html
define("FORWARD_PERSONAL_NOTE_SIZE",0);

#0013076: different content when forwarding 'to a friend'
# Allow admin to enter a different message that will be sent when forwarding 'to a friend'
# This will show an extra tab in the message dialog.
define("FORWARD_ALTERNATIVE_CONTENT",0);

#0013845 Lead Ref Scheme
# When this setting has a value <> '' all succesfull handovers to the MTA will be counted
# and saved in the attribute with the name of this setting.
#define('FORWARD_FRIEND_COUNT_ATTRIBUTE', 'FriendCount');




CategoryDocumentation
Page was generated in 0.1282 seconds