On 2006-11-13 06:02, Carlos E. R. wrote: > > The Monday 2006-11-13 at 12:31 +0100, Carlos E. R. wrote: > > > No spaces, lost. > > > I'll try this one without pgp signing. > > That's it! Pine barfs on the pgp signature. When using pgp signing, the > dashes are replaced with "- --", and Pine, which is not really pgp-aware, > doesn't see it at the signature mark. This is a bug or a missing feature. > > Balsa also has this problem. Thunderbird and Kmail both work fine in that > respect, at least here. > > Therefore, if you have a problem as well, it is your mail client that is > broken or misconfigured somehow. See http://bugzilla.mozdev.org/show_bug.cgi?id=15526 about the "--" being replaced with "- --". That bug was marked as "resolved invalid" because it doesn't occur if you use the PGP/MIME option. However, there is another bug, https://bugzilla.mozilla.org/show_bug.cgi?id=99922 which is 3 or 4 years old, which is still active, and which says about the same things as the first one.
That really isn't the problem here, Carlos. When you sign a message, everything between the double-dash signature indicator and the "end pgp" part, inclusive, is stripped. Everything that is added by the suse mail server is kept as "new" text. This is Seamonkey, which should behave the same as Thunderbird. The double-dash-space is being properly added to your messages, but something is confusing the Seamonkey mua into believing that everything *after* the pgp end should be kept. I am going to add a comment to the second of those bug reports in case this is a related problem. If it isn't, I guess someone at mozdev will let me know the proper bug number, if there is one :-) -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
