Thanks, I'll give that a shot at work in the morning. Right now I'm
99.9% convinced that it's Listserv or LSMTP (both running on NT) doing it.

It does not seem to be an issue related to a recipient mail server. I
tested it to with multiple recipients, multiple destinations, multiple
recipient servers(Exchange, Sendmail, Postfix), multiple email clients
(Pine, OE, Outlook, Netscape Communicator, and it ALWAYS does it. I also
tested it to my home email account, and looked at the raw email spool
file on my home server in unix.

Also, I bcc'd a copy of my LISTSERV-L post to my home and work emails,
and the indents *work* in the example embedded in my post.

Also, I tried sending the distribute job from both Unix (shell script,
built headers, piped to sendmail), and from OE on Windows. Always, I
bcc'd that distribute job to my various mailboxes and it's indented in
that BCC copy, but not the resultant distribute job.

Also, it doesn't seem to be an issue I can chalk up to mime or other
encoding. Tried it as a mime text email and plain email with no mime and
same results.

If anybody's bored, enough, feel free to run that distribute job on your
LISTSERV and send it with [log in to unmask] as a recipient, as well as yourself.

Best regards,
Al Iverson

Jacob Haller wrote:
>
> >Say, I'm doing a distribute job for somebody, and the copy they used has
> >some indented spaces.
> >For example, an indent of 3 spaces when following up a bullet point
> >(actually a dash) in plain text.
> >
> >Also, they built a wacky text-graphic header with a line indented by a
> >couple dozen spaces.
> >
> >An example just like it is below.
> >
> >When I run the distribute job the spaces get removed, so that the
> >indented lines are no longer intended.
> >
> >Other than "don't do that," what I can I do to make sure purposely
> >indented lines stay indented? Any ideas?
>
> The following should tell you where the formatting change is
> occurring.  (I seriously doubt that LISTSERV is doing it, but if it
> is, this will tell you that.)
>
> If this is an NT installation:
>
> 1) Stop LISTSERV, but leave the SMTP listener (or LSMTP if that's
> installed) running.
>
> 2) Send the job.
>
> 3) Before long a .job file should appear in LISTSERV's spool
> directory.  View it using the jobview executable that should also be
> in the spool directory.  See if the formatting is as you want it to
> be.
>
> 4) Stop LSMTP (or whatever's handling LISTSERV's outgoing mail).
>
> 5) Restart LISTSERV.
>
> 6) LISTSERV should now read the .job file and act on it.  Any mail
> generated by the job will be written to one or more .mail files in
> LISTSERV's spool directory.
>
> 7) Open the .mail files (they're plaintext) and see if the formatting
> is as you want it to be.
>
> 8) Restart LSMTP (or whatever is handling LISTSERV's outgoing mail).
>
> If the formatting's OK in steps 3 and 7 then it's getting screwed up
> after it leaves LISTSERV.  If it's already incorrect at step 3 then
> the problem is occuring before it's getting to LISTSERV.  If it's OK
> in step 3 and not in step 7 then LISTSERV is at fault (you shouldn't
> see this, but if you do, that's what it means).
>
> Thanks,
>
> --
> Jacob Haller, Technical Support
> L-Soft international, Inc
> http://www.lsoft.com/

--
Al Iverson -- http://www.radparker.com -- Minneapolis, Minnesota, USA
Support Minnesota Jazz -- Disclaimer: All of my opinions are mine alone.