Subject: | |
From: | |
Reply To: | |
Date: | Thu, 2 May 1996 17:18:03 +0200 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Wed, 1 May 1996 23:48:22 +0200 Nicolas Graner <[log in to unmask]>
said:
>Point well taken. However, even for my English speaking list, the choice
>of customizable messages seems rather restricted and arbitrary. I'm
>curious to know how the selection was made and if it's likely to be
>extended in the future.
The MAILTPL/MAILFORM files started as a repository of what used to be
called "administrative messages", ie messages that are sent by LISTSERV
under a separate envelope. The selection was simple: ALL administrative
messages were in that file, and NO other message was included. Then
people started asking for the inclusion of a few "linear messages" in the
file. This actually required a change in the mail template processor, but
it was indeed the most logical place to add customization for these
shorter, inline messages. This doesn't mean that we went over all 110,000
lines of code and checked every single message to decide if it should be
moved to a template or not. Again, while this is the logical place to
customize messages related to a list, this is not a good way to customize
large numbers of small messages, especially not messages that are likely
to change in a future version. Currently the MAILTPL files are not
version dependent (or at least you can take a file from a newer version
and it will work just fine, so we can distribute one copy of this file
for all supported versions). So, I can see having 5-10 short messages
listed in the MAILTPL file, but not 50-100.
>If one more message could be customized, I'd vote for the subscription
>confirmation request for Open;Confirm lists. It determines the first
>impression new subscribers get from the list, and as an ambassador it
>should reflect the owner's desires.
It's called CONFIRM1, but was added after the initial release of 1.8b.
Your server may or may not support it.
Eric
|
|
|