Sat, 29 May 1999 06:47:30 -0700
|
SET LSTOWN-L MAIL
END
On 29 May 99, at 8:35, Pete Weiss wrote: Re: INVALID OPTION, (w
> A related command processing problem relates to folks who include
> SIGNATURES in their LISTSERV command stream. LISTSERV "sees" the
> signatures as commands and can't decode them. Best advice:
>
> 1) don't use signatures files when commanding email automation processes;
>
> 2) if you do, make sure the first line contains a double-dash followed
> either by optional whitespace ending with a <LF><CR>
>
> See my .sig for an example of 2).
>
>
> --
> mailto:[log in to unmask] Tel: +1 814 863 1843
> 31 Shields Bldg; University Park, PA 16802-1202 USA
> Those headers aren't "forged" just creatively massaged
>
Another option on the use of signatures, (or if you want to send the
command and include an extra note as a CC: to some other party at the
same time) is to send the command(s) as the first line(s) of text
followed by the word "end" on a line by itself. You can then follow it
with whatever else you want to send and the server will ignore all
after the word "end".
|
|
|