Utilities: List Document: New List Document: Advanced
Applies To
The list, site or server this document can be used for. The document can apply to a single list, all lists on the site, or all lists on the server.
Document Type
The type of document this is. The document type is for informational purposes only in the 6.0 interface.
In the 5.0 interface, the type determines where the document can be used or selected. For instance, in List Info, only HELLO type documents can be selected for the Hello document.
The types of documents are:
ABOUT
General message describing something. Used in List Info for Sponsor, Long Description, and Comments.
ACTION
A message explaining the reason why an action was taken. Used for action phrases.
ADDRESS
Physical address. Used for Address in Site Info.
BYE
Goodbye message user receives when leaving a list. Used for Bye in List Info.
CONFIRM
Confirmation message user receives when subscribing to a list. Used for Confirm in List Info.
FRAGMENT
Sentence fragment, such as a company name.
HELLO
Welcome message user receives when joining a list. Used for Hello in List Info.
HELP
General help message about using ListManager.
ORGANIZATION
Information about an organization. Used for Sponsor in List Info.
RESPOND
An auto-responder document. Also used for Held in List Info.
Language
The language in which this document is written. If multiple language version of a document exist, ListManager will try to use the most appropriate document for that person. It will look at the country code of the person's hostname address, and determine which languages that country uses. It will then look for the document in the languages that country uses. If it finds no match, ListManager will use either the English language version of the document (if multiple language versions exist, but none match the person's language) or the first document which matches the needed subject.
Headers to Add
The contents of this field will be added to the header of the outgoing message. This field is primarily used for creating documents with alternative character sets and content types. By default, no content-type or character set information is included when sending documents. Most mail clients will default to a standard character set which may not support the characters that were used to compose the message. If a document contains characters that aren't able to be represented by the standard character set, you must specify the character set information in the Additional Headers field.
For example, to use the ISO standard Central European character set in a document, the following lines must be inserted into the Additional Headers field:
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: 8bit
Other content-types are available. To determine which content-type specification you need, try using the technique explained below in the ‘Creating Unicode, HTML, and multipart messages’ section.
These lines do not affect the contents of the Body field so the text in this field will be in whatever character set is the default for your system. As a consequence, when viewing your message in the web interface, you may see different characters than what you entered.
For single-byte character sets, you should be able to cut-and-paste the text of your message into the web interface directly. Multi-byte character sets require a different technique, which is described below.
Creating Unicode, HTML, and Multipart Documents
Unicode, HTML, and multipart messages require special encoding and header specifications to
function properly. The following procedure will allow you to create documents of these types with proper
encoding.
1. Compose a message as you would like it to be viewed by those who receive it.
2. Send that message to a ListManager test list, which is configured to approve all mailings.
3. View the message in Mailings: Need Approval. Or, view it in Utilities: Mail Queues: Incoming.
4. Copy the relevant section from the header. For example:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="nqp=nb64=()p1KaLmIg2"
5. Copy the entire message body. For example:
--nqp=nb64=()p1KaLmIg2
Content-Type: text/plain
Test
--nqp=nb64=()p1KaLmIg2
Content-Type: application/pdf; name="test.pdf"
Content-Disposition: attachment; filename="test.pdf"
Content-Transfer-Encoding: base64
JVBERi0xLjIgDSXi48/TDQogDTggMCBvYmoNPDwNL0xlbmd0aCA5IDAgUg0vRmlsdGVyIC9M
WldEZWNvZGUgDT4+DXN0cmVhbQ0KgBCKgNGg1GwuGQ0EA2GoyFwzGQgEBUIgNGAgi8XORnEA
NF5Gi4xGYuHMRiZmiwuGA2G43iRUMcYlQ2Ggzl53EAoK5oNJ0MogKBhOBlOQgN5uFMTNQNIs
--nqp=nb64=()p1KaLmIg2--
6. Go to Utilities: List Documents, and click on Create New Document.
7. In the body, paste the entire message body from the message you sent to ListManager.
8. Click on Advanced. Paste the headers in Headers to Add.
9. Save the document.
Note that web based mail clients may not be able to render alternate character sets at all. You should carefully test and review the document content before using it in production.
Date Created
The date this document was created.
More
2. Utilities: List Documents Main Page
1. Utilities: List Document: New List Document
2. Utilities: List Document: New List Document: Advanced
3. Utilities: List Documents: Sample Documents
|
|