[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: knode doesn't strip signatures



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Gomu?ka on Sunday 11 Jun 2006 13:35 wrote:

> Dnia niedziela, 11 czerwca 2006 01:55, Ritesh Raj Sarraf napisa?:
>> <posted & mailed>
>>
> [cut]
> It would help a lot if you provide exact steps to reproduce and/or msgid for
> which this behaviour occurs.
> I have tried to search google groups for your name but it hasn't revealed too
> much - actually you have used many signature indicators ("--", "-- ", "- --")
> and also signed your messages.
> It is hard to help when you have so many things to guess.
> 
> Regards,
> Robert
> 
> --------------------
> W polskim Internecie s? setki milionów stron. My przekazujemy Tobie tylko
> najlepsze z nich! http://katalog.panoramainternetu.pl/

My signature file uses just the text and not any of the signature indicators
you've mentioned. I guess that's the job of the News/Email application to add
proper signature indicator when you define it to use signature from a file.

So that makes me wonder why my posts would include multiple signature indicators
as you've mentioned.

Do signed messages fall into this category ?

But then I've tried my own messages with Kmail and Kmail does the job correctly.

Interestingly when I see my own messages in Knode, it's all scrambled. It's
shown exactly as you've mentioned.

The charset shown for the composer is iso8859-1. Can this be the issue ?
Also I use gmane for all mailing lists. I'm not sure if that's the reason.

Ritesh
- -- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is research."
"The great are those who achieve the impossible, the petty are those who
cannot - rrs"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEjECN4Rhi6gTxMLwRAt49AJ4rfl64wdvHWRqdaEEV1wW4vDcY5ACfUIND
qdP/CMiU5ag5jHi5mHheUKM=
=+fo2
-----END PGP SIGNATURE-----



Reply to: