🚀 go-pugleaf

Gary Priest <gary@the-gap.demon.co.uk> wrote:

> I've recently had someone ask me to stop POPwatch prefixing the signature
> file with <CRLF>--<CRLF>
> 
> I'm reasonably happy to do this, but can someone tell me what the
> standards/rules are for this? 

It's contianed in Son of RFC 1036, the actually synatax is 
<CRLF>-- <CRLF> but you seem to be using that anyway or my newsreader
(unlike many) doesn't care about the space.  If you want a copy try
ftp.demon.co.uk/pub/doc/rfc/so1036.txt

> It was my understanding that all sigs should
> be prefixed with the above, that way programs can truncate any sigs or
> binaries etc. when you reply to an email/article.

It is IMHO a very good devic, it should be encouraged to make life
easier and to help stop idiots quoting sigs.

> I know Oasis2, Oasis1.3 (although it uses __ in error), and I'm guessing
> NOS all prefix the sig with this. NEWSie doesn't. Turnpike on the PC does.

Most moder software adopts it, it's not compulsory or anything but it's
the only standard we have so people have quickly taken to using it.

> POPwatch only acts this way when sending from NEWSie, because it has to
> append the signature to the end before sending email. All other POPwatch
> formats will be unaffected.
>  
> Anybody got any ideas as to what is correct?

It is basically one of those things that just advised to make life
easier, I've no idea why anyone would actually dislike it enough to want
it removed, if you decide to go with this persons idea then I suggest
you just make the sig-sep an option which is set to on by default.