Re: [twsocket] Message-Id is not valid, according to RFC 2822

2006-07-17 Thread Arno Garrels
Hello Piotr, >> Is there something I can do to pacify X-Spam? > > Remove that space (the one between Roland and Couvela). Shall we modify function GenerateMessageID? Something like: {* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *} function GenerateMessageID : Stri

Re: [twsocket] Message-Id is not valid, according to RFC 2822

2006-07-17 Thread Piotr Dałek
Hello! > Thank you, Arno, for your help, project now working, but on sending > myself a message I get back > X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on > as002.apm-internet.net > X-Spam-Report: > * 1.7 INVALID_MSGID Message-Id is not valid, according to RFC 2822 > [..] > Mess

Re: [twsocket] Message-Id is not valid, according to RFC 2822

2006-07-17 Thread Arno Garrels
kaythorn wrote: > BTW: You can always search the list archive at: > http://www.elists.org/pipermail/twsocket > > Actually I did try this first, but got "Page not available" Possibly it was temporarily not available, usually it works. > > Thank you, Arno, for your help, project now working, but

[twsocket] Message-Id is not valid, according to RFC 2822

2006-07-17 Thread kaythorn
BTW: You can always search the list archive at: http://www.elists.org/pipermail/twsocket Actually I did try this first, but got "Page not available" Thank you, Arno, for your help, project now working, but on sending myself a message I get back X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-

Re: [twsocket] HttpCli in v5 - Different Encoding Perhaps?

2006-07-17 Thread Marcelo Grossi
Hi JP, I thought at first it was some Unicode format but then why don't I have a #0 before each character? Shouldn't it be like this: "#0F#0u#0n#0k#0y#0 #0T#0e#0x#0t" ? Two Bytes per Char ... So I'll have to make a converter for this right? This makes me sad :'( Thanks for your time, Cheers,