Re: Using the not-dash-escaped option

2012-02-02 Thread Werner Koch
On Wed, 1 Feb 2012 21:47, expires2...@rocketmail.com said: I'm not sure that helps me. See below. - --=20\n :-) Sure it does not work if you use Content-Transfer-Encoding: 7bit Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

Re: Using the not-dash-escaped option

2012-02-02 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Thursday 2 February 2012 at 9:50:34 AM, in mid:874nv9va1h@vigenere.g10code.de, Werner Koch wrote: Sure it does not work if you use Content-Transfer-Encoding: 7bit The message body looks exactly the same in the copy in my

Re: Using the not-dash-escaped option

2012-02-02 Thread brian m. carlson
On Thu, Feb 02, 2012 at 08:45:56PM +, MFPA wrote: On Thursday 2 February 2012 at 9:50:34 AM, in mid:874nv9va1h@vigenere.g10code.de, Werner Koch wrote: Sure it does not work if you use Content-Transfer-Encoding: 7bit The message body looks exactly the same in the copy in my

Re: Using the not-dash-escaped option

2012-02-02 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Thursday 2 February 2012 at 9:53:00 PM, in mid:20120202215300.ga6...@crustytoothpaste.ath.cx, brian m. carlson wrote: I think what Werner is saying is to use quoted-printable encoding; then, the space will be represented as =20 (when

Re: Using the not-dash-escaped option

2012-02-01 Thread Werner Koch
On Tue, 31 Jan 2012 23:29, paul.hart...@gmail.com said: It's still missing the trailing space, assuming you put one there in the first place... many people don't realize it's supposed to be there. The best way to make sure that it does not get removed is by using QP encoding. (--=20\n).

Re: Using the not-dash-escaped option

2012-02-01 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Wednesday 1 February 2012 at 5:20:46 AM, in mid:ui@r78.nl, Remco Rijnders wrote: And for what it's worth... my client tells me the signature on this particular post you made is invalid. Your other posts to this list all pass the

Re: Using the not-dash-escaped option

2012-02-01 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Wednesday 1 February 2012 at 8:48:53 AM, in mid:87ehuf0wi2@vigenere.g10code.de, Werner Koch wrote: The best way to make sure that it does not get removed is by using QP encoding. (--=20\n). I'm not sure that helps me. See below. -

Re: Using the not-dash-escaped option

2012-01-31 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hi On Monday 30 January 2012 at 4:27:44 PM, in mid:ab8b81216d496cec1af6fe8144c99...@biglumber.com, Greg Sabino Mullane wrote: That's exactly what the --not-dash-escaped option is for.

Re: Using the not-dash-escaped option

2012-01-31 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Tuesday 31 January 2012 at 10:29:53 PM, in mid:caeh5t2p4u+3nt7nlgwfjr6qh_72wlj7ygw5gabw1a1zjpss...@mail.gmail.com, Paul Hartman wrote: It's still missing the trailing space, assuming you put one there in the first place... many people

Re: Using the not-dash-escaped option

2012-01-31 Thread Remco Rijnders
On Tue, Jan 31, 2012 at 09:41:16PM +, MFPA wrote in 516876184.20120131214116@my_localhost: That's exactly what the --not-dash-escaped option is for. Granted, it's not portable to some other PGP implemetations, but if there is any mailing list in world in which it would be acceptable, I