LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Ben Parker <[log in to unmask]>
Thu, 7 Oct 2004 13:08:48 -0600
text/plain (67 lines)
On Thu, 7 Oct 2004 10:27:06 -0700, Randy Klumph <[log in to unmask]> wrote:

>I recently posted a message on our newsletter list. The posting failed
>to include the Subject-Tag and did not process the Top_Banner template.
>It has included these in all other postings for the past 2 years. What
>would cause the sudden failure?

LISTSERV doesn't misbehave in this way.  If you are sure the message you
received is not a CC: or BCC: from another party that did not pass through
LISTSERV, then the only possible interpretation is that the settings were
somehow changed.

SUBJedthdr is an individual subscriber setting.  Your subscription setting may
have been changed by you (inadvertently) or by some backup/restore process.

the command

 Query Listname

will return your current subscription settings.  If you are keeping a
listname.CHANGELOG you may also want to examine that for record of any recent
changes.

The definition of the TOP_BANNER may also have been changed, again by a
backup/restore process or by another person.  Verify that it is correctly in
place.  If necessary, copy it to a test list and verify it works correctly
there.  If this is 1.8e and is a moderated list, then the bottom_banner and
top_banner are added to a  message before it is presented to you for approval.
Check for this being done properly.  (in 1.8d the *_BANNER is added after
approval so this won't work)

If you are keeping list message archives, verify that the TOP_BANNER is
present in the archived message.  If it is not, then the TOP_BANNER was not in
effect for that message.

Finally, examine the LISTSERV-yyyymmdd.LOG file for the date in question.
When the message is approved and mailed out, assuming you have some people set
to SUBJ and some to FULL (or some other settings) you will see separate
mailngs in the log file something like this :

27 Sep 2004 20:00:31 Processing mail from [log in to unmask] for L1
27 Sep 2004 20:00:31 Distributing mail ("L1") from
owner-l1@MOBIL2.BESTEFFORT.COM...
27 Sep 2004 20:00:31 Mail posted via SMTP to [log in to unmask]
27 Sep 2004 20:00:31 Done - 1 outbound file (1 rcpt).
27 Sep 2004 20:00:32 Distributing mail ("L1") from
owner-l1@MOBIL2.BESTEFFORT.COM...
27 Sep 2004 20:00:32 Mail posted via SMTP to [log in to unmask]
27 Sep 2004 20:00:32 Done - 1 outbound file (1 rcpt).
27 Sep 2004 20:00:32 Distributing mail ("L1") from
owner-l1@MOBIL2.BESTEFFORT.COM...
27 Sep 2004 20:00:32 Mail posted via SMTP to [log in to unmask]
27 Sep 2004 20:00:32 Done - 1 outbound file (1 rcpt).
27 Sep 2004 20:00:32 Message DISTRIBUTEd to 3 recipients.

(The above was a test done for other purposes, but it shows how the separate
user subscription types are handled as separate mailings.  The subscription
types are not normally so obvious as in these made-up test addresses, but you
can figure it out by correlating actual addresses in your file to subscription
settings.)

Lastly, examine the LISTSERV-yyyymmdd.LOG files for every day back to the last
correct posting (if you have them) and look carefully for any editing of the
listname.MAILTPL file, or any other changes to subscribers of that list, etc.
This can be a long, slow hunt, but if the files were changed by LISTSERV
commands somewhere along the way, there will be some record in the LOG file.

ATOM RSS1 RSS2