[Roadsters] More on reply

[Mark J Bradakis]

Okay, I found another message from a while ago that I sent to some other
list, perhaps it might be helpful to some here.  I really should write up
a nice little FAQ for Team.Net.

mjb.

I should probably write up something about this like I did for setting
the nomail option when heading off on vacation.  RealSoonNow.

In general, assuming the message is sent to the proper address from a
subscribed address it will go through to the list.  Exceptions are when
it is too large, usually because people can not figure out how to highlight
and delete stuff that doesn't need to be sent out once again.  Or it may
show up as an empty message, or contain a line something like

/xiu0iqwy:  permission denied


In these cases it is the filter that all messages to Team.Net pass through.
The filter tries its best to convert all sorts of random stuff from who
knows what sort of brain dead software into plain, readable text.  For
the most part it works pretty well, stripping out useless. bloated RTF
crap from Microsoft, malformed HTML from AOL and various sources
and other such nonsense.   Ever notice those posts where there are odd
characters like 'B' in places you wouldn't expect it?  Standards are
great, there are so many to choose from ;-)

If you keep getting such behavior when posting, dig through the
documentation for your mail program and try to send in plain text.
[ This stuff isn't an issue with http://www.team.net/forums ]

If plain text isn't a readily apparent option, sometimes simply changing
fonts can remove the introductory setup crap that the filter can't
understand and will let it send your message through.