>   Two problems are causing havoc with our lists' readability/usefulness:
>
>   (1) What causes =20, =B7, =FA etc. to appear at the end of lines, start of
>   lines, or after an indent at the start of a line?  Just as importantly,
>   how can Joe/Jo User solve this problem or prevent it if say they're
>   causing it by pulling external material into the message? Setting up test
>   list(s) hasn't worked yet.

This typically means that the user is using quoted-printable to display
special characters.  Some email clients have an option to disable
quoted-printable (in the version of Eudora I use it's in the 'Sending
Email' section of the settings); if that's not the case with your user than
he or she should attempt to avoid using the extended characters.  (Apart
from obvious things like accented characters, ths includes things like
smart quotes.)

If it's showing up in every message, they may have one or more special
characters in their .sig file.

>   (2) What causes the user to send out a message, seemingly innocent,
>   (usually with an attachment initially), but to get gibberish results?
>   Again how to solve & prevent? Attachment (gibberish) appears in body. Body
>   often has the =20 =FA gibberish. Example:
>
>   [Headers]
>   Body ...
>   [Headers e.g. "Boundary..."/"Application"/"Attachment"/ "<filename>"/
>   "...encoding"]
>   /1dQQ5ALAAABCgIBAAAAAgUAAAC0RAAAAAIAAGUJo3sFcBYhMSF1zi45HgErB2ZF
>   ecUPLEnwFQRPiRz1bWOwZA/9sQRora2eZJq+v4T0QEdixZCdNWD0dJvXt8gW518v
>   [more gibberish]
>   ["Boundary"]

This I'm not familiar with.  Do you know what email client they are using
to compose and send their email?

-jwgh