Yea, I was going down that path after I sent my initial posting. Glad to 
see that's all this problem is though. I see 6 template blocks in my 
existing 1.8d default.mailtpl that do NOT exist in 14.5's. I see the 
template names listed elsewhere in the new 14.5 default, so I will assume 
they were just renamed and not part of a custom template the original 
owners of this listserv added. Thanks for all of the help and have a great 
rest of your holiday week!

=============================
Ken Koch
Information Systems
314.935.8315
=============================



Ben Parker <[log in to unmask]> 
Sent by: "LISTSERV site administrators' forum" 
<[log in to unmask]>
12/28/2006 12:50 PM
Please respond to
"LISTSERV site administrators' forum" <[log in to unmask]>


To
[log in to unmask]
cc

Subject
Re: Mail templates not found, 1.8 to 14.5






On Thu, 28 Dec 2006 11:41:24 -0600, Ken Koch <[log in to unmask]> wrote:

>Greetings! I've recently upgraded from 1.8d to 14.5 and I'm getting a few 

>errors regarding templates. 
>
>>>> Mail template "MSG_POSTING_SUCCESS_ACK" not found <<<
>>>> Mail template "MSG_POSTING_REJECT_NOTAUTH" not found <<<
>>>> Mail template "MSG_SUBSCRIBE_FORWARD_OWNER" not found <<<
>>>> Mail template "MSG_SIGNOFF_NOSUBFOUND" not found <<<
>

The most likely cause is that the default.mailtpl file for 1.8d was not
updated (overwritten) by the 14.5 version.  You can copy this file from 
the
scratch directory where you untar'd the installation kit.  Be sure it
overwrites and replaces the existing (1.8d) default.mailtpl file.

>I have no site.mailtpl in the listserv/home directory.

Prior to 14.3 this file would have been called www_archive.mailtpl. 
However,
unless you had made certain modifications to the 1.8d www interface you 
would
not have this file at all.  In that case there would be no need for 
automatic
conversion of this file by 14.3 and later versions.

>I know site-wide template structures changed from 1.8d to 14.3+, but I 
>didn't seen any specific documentation as to how to compensate for it 
>other than let listserv convert when it's first started. I didn't see any 

>conversion messages when I first started it, but I did go directly to 
>14.5. Is that an issue?

Not necessarily, see above.