> What would cause this error in a Digest message but not in the an individual post to a List?
> 
> [Message contains invalid MIME fields or encoding and could not be processed]
> 
> Krista Landon

Basically, when LISTSERV puts together a plaintext digest, it discards everything in the message that isn’t plaintext. If, at the end of that, there’s nothing left, then you get this error. (The error might also show up in other circumstances, if some other error occurs while LISTSERV is attempting to parse the message to put it in the digest.)

My guess is that the message in question was either an HTML message that did not include a plaintext version of the message, or was a message that just consisted of an attached document. Most email programs automatically generate and include a plaintext version of an HTML message, and contain at least a blank plaintext part of messages containing attachments, so this sort of error is rare.

The default wording of the message doesn’t specifically address that scenario, but if you want, you can customize it under ‘List Management’/‘Mail Templates’ (to customize it for a specific mailing list) or ’Server Administration’/‘Mail Templates’ (to customize the default site-wide version). The template’s name is MSG_DIGEST_FRAGMENT_MIME_ERROR.

Thanks,
jwgh
############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1