%%merge recip.nameemail%%
The full name and email address of the recipient. For example, you might want each posting to your list to have a header which identifies the original author, as in:
From: %%merge recip.nameemail%%
If a full name is not available, ListManager will only put the email address.
For example:
Bob Smith <bob@example.com>
Or if no name is available:
bob@example.com
%%merge recip.emailaddr%%
This substitutes in the recipient's email address.
For example, you might make your list header be:
To: %%merge recip.EmailAddr%%
You may be interested to know….
And ListManager would substitute it to say:
To: bob.smith@example.com
You may be interested to know….
%%merge recip.fullname%%
This substitutes in the recipients' full name, as recorded in the members_.fullname_ field. If
the member does not have a full name, their email address is used instead.
For example, you might start your mailing out with this:
Dear %%merge recip.FullName%%, we are glad that you have…
And ListManager would substitute it to say:
Dear Bob Smith, we are glad that you have…
%%merge recip.firstname%%
This substitutes in the recipients' first name (the first component of their full name). If the
member does not have a full name, their email address is used instead. If a member only has a single
component to their name, that component is used.
For example, you might start your mailing out with this:
Dear %%merge recip.FirstName%%, we are glad that you have…
And ListManager would substitute it to say:
Dear Bob, we are glad that you have…
%%merge recip.memberid%%
This substitutes in the recipients' unique Member ID. This is useful for exactly identifying
the user.
%%merge recip.list%%
The name of the mailing list this recipient is receiving this message from.
%%merge recip.receiveack%%
Whether or not this recipient receives acknowledgements of their postings.
%%merge recip.subtype%%
The type of subscription this recipient has (mail, digest, etc).
%%merge recip.expiredate%%
The date (if any) that this recipient's subscription expires.
%%merge recip.whatlists%%
This substitutes in a listing of all the lists the recipient is a member of. This is very useful when you want to let users know exactly which lists they have signed up for. It is important to note that this tag only shows those lists where the member's status is "normal". In other words, if a list the member has subscribed to is set to require confirmation, and the member has not confirmed, the list will not show up in this listing.
For example, you may want to use this merge tag in the confirmation document:
Welcome! You have signed up for the following lists:
%%merge recip.whatlists%%
By replying to this message, you confirm...
An excellent opportunity for the above example is when a member signs up for many lists at once and they are sent a single confirmation document. That way, rather than receiving a confirmation for each list, they receive a single confirmation with a listing of the lists.
%%merge recip.whatlistsunconfirmed%%
This substitutes a listing of all the lists the recipient has subscribed to, but has not yet sent confirmation for. This is particularly useful when adding a member to many lists and you want to send them a single confirmation that shows the lists they have not yet confirmed on.
For example, you may want to use this merge tag in the confirmation document:
Welcome! Your confirmation is needed for the following lists:
%%merge recip.whatlistsunconfirmed%%
By replying to this message, you will confirm yourself for all of these lists...
A good opportunity to use this tag is when you have subscribed someone to many lists at once using the 'Add' command in a command message. In that command message, you also specified that the member should receive a single confirmation message by using the oneconfirm modifier.
%%merge purgeid%%
This substitutes in the Recipient's email address, in square brackets. If this text is forwarded
to the unsubscribe-listname@… or purge@… address, ListManager will automatically locate it and unsubscribe
this address. This allows you to provide a failsafe unsubscribe mechanism. For example, a typical list
footer might be:
This is a posting from: %%merge List.Name%%
To unsubscribe, send a message to %%merge Email.UnSub%%
%%merge PurgeID%%
%%merge outmail.messageid%%
This substitutes in the message's unique outmail message ID. This is useful for exactly identifying
the message.
For example, if you sent the following message to a mailing list:
Hello! Your email address is %%merge recip.EmailAddr%%, your member ID is %%merge recip.MemberID%% and the ID of this message is %%merge Outmail.MessageID%%.
To the person who received the message, it might look like this:
Hello! Your email address is bob@example.com, your member ID is 905 and the ID of this message is 3154.
%%merge recip.datejoined%%
The date that this recipient joined this mailing list.
%%merge recip.numbounces%%
The number of permanent failures this recipient has produced in recent days.
%%merge recip.datebounce%%
The date of the most recent permanent failure received from this recipient.
%%merge recip.islistadm%%
Whether or not this recipient is a list administrator.
%%merge recip.confirmdat%%
The date (if any) that this recipient confirmed their membership. Only applies to lists where
"confirm membership: yes" is set.
%%merge recip.notifyerr%%
Whether or not this recipient receives error mail notifications (i.e., failure reports).
%%merge recip.dateheld%%
If this recipient is held, what date they were held on.
%%merge recip.norepro%%
Whether or not this recipient receives copies of their own postings.
%%merge recip.cleanauto%%
Whether or not this recipient will be automatically held if they bounce too much mail (too many
permanent failures).
%%merge recip.comment%%
The comments that this recipient has.
%%merge recip.additional%%
The additional information this recipient has. This field is not used by ListManager, and is
meant for user-defined data of any type.
%%merge recip.userid%%
The userid information this recipient has. This field is not used by ListManager, and is meant
for user-defined data of any type.