-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 13:49 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

when I get an email going to my gmail account, with a from address with accented letters, it is corrupted; copying directly from the mbox file with less, I see this:

Date: Mon, 6 Oct 2008 11:48:18 +0200 From: =?ISO-8859-1?Q? "Camale=F3n" _ <....@gmail.com>, ?=@nimrodel.valinor To: "opensuse-es@opensuse.org"

or:

Date: Sat, 04 Oct 2008 18:48:14 -0400 From: =?ISO-8859-1?Q?Cristian_Rodr=EDguez_ <....@suse.de>, ?=@nimrodel.valinor

The MIME encoded From-header is being broken up, and continued on the next line with a <tab> character prepended.

Mmm... Any guess about who or what might be doing that? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjp/moACgkQtTMYHG2NR9WxUgCfSUKQwXwOnj/h/WnZxrr0XFLL sf4AoIWd918FHD3SZrE407za6OrpT6AF =yx+M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 14:31 +0200, Per Jessen wrote:

...

...

The MIME encoded From-header is being broken up, and continued on the next line with a <tab> character prepended.

Mmm... Any guess about who or what might be doing that?

Outlook does it quite regularly, although it's usually the Subject: line.

Ah, no such abomin... er... programs here. Linux only.

But it's a different pronlem, I think -

you said one original line was:

From: "=?ISO-8859-1?Q?Camale=F3n?=" <....@gmail.com>

which got 'translated' into this:

From: =?ISO-8859-1?Q? "Camale=F3n" _ <....@gmail.com>, ?=@nimrodel.valinor

That's really weird - it's not just being broken up, the MIME encoding is being extended ...

yep.

Dunno what might be doing that.

My very wild guess is amavis or spamassassin, triggered with something from gmail. But then somebody else might be seeing it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjqKJUACgkQtTMYHG2NR9V+lQCgmLmsAOaUn5LDxqWOpXNGvZEl LEgAnRw5my5QtT6F8pZiiIiVT0H+NL1G =ZNzc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 17:12 -0400, Patrick Shanahan wrote:

I would bet you are accessing your gmail via imap[s] and I believe that this is caused by gmail's imap utility. I observed the same corruption after trying imap and the condiiton was gone upon returning to pop[s] access.

Try it and see :^)

Argh. Ok, switching to pop3, I'll try. If so, they have a bad imap server implementation. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjqhykACgkQtTMYHG2NR9V1yQCfYf8Cq5WUfbI8nWiR3etHV4Nz eHQAn1Bot2vwzuwk92XBEkWutO3HGOe4 =6t2/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 23:46 +0200, I wrote:

On Monday, 2008-10-06 at 17:12 -0400, Patrick Shanahan wrote:

...

I would bet you are accessing your gmail via imap[s] and I believe that this is caused by gmail's imap utility. I observed the same corruption after trying imap and the condiiton was gone upon returning to pop[s] access.

Try it and see :^)

Argh. Ok, switching to pop3, I'll try. If so, they have a bad imap server implementation.

Good news: yes, that is the problem. Bad news: the imap server and the pop server are not synced. I started getting all my emails since 2007-12-28, so I had to kill fetchmail, which must be thousands. I'll have to return to imap :-( And on 2007-12-28 I got my first bad mail from them, so it seems I switched to imap on that date. I wonder if they know? Reporting problems to gmail is not that easy, I think. Curious! If I had kept a diary of what I changed when, I could have discovered that the culprit was imap myself. But I'm not that meticulous. Or fastidious, I think is the English word. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjqjXMACgkQtTMYHG2NR9UuwwCggj6KzQ1C9ekzqfn36W4a6q35 1dcAnjW/99RsDw1RtHFzvJ32mBgPDwZ2 =sg2b -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 18:28 -0400, Patrick Shanahan wrote:

* Carlos E. R. <> [10-06-08 18:14]:

...

Good news: yes, that is the problem.

:^) or :^(

...

Bad news: the imap server and the pop server are not synced. I started getting all my emails since 2007-12-28, so I had to kill fetchmail, which must be thousands. I'll have to return to imap :-(

I believe that they mark differently

Has to be.

...

And on 2007-12-28 I got my first bad mail from them, so it seems I switched to imap on that date.

I wonder if they know? Reporting problems to gmail is not that easy, I think.

Yes, I had more difficulty determining the problem than dealing with novell's bugzilla, which is much easier now :^)

Yep. I'll have a look at gmail reporting, one day I'm bored.

...

Curious! If I had kept a diary of what I changed when, I could have discovered that the culprit was imap myself. But I'm not that meticulous. Or fastidious, I think is the English word.

I believe either would be applicable in this instance, or at least in the same ballpark. I'm going to confuse the issue with coloquialisms here :^)

for what it's worth, I keep a local database of the last three months message traffic and one of the message ids. I use procmail to check against each message id for dups and segregate matches. In the last three years I have never had a false positive. So, when I switched back to pop, I dl'ed a lot of mail, but didn't have to sort thru the dups.

Yes, I do keep both logs for a long time; but I had bad luck with duplicate testing so I don't do it (I can get the same message-id on two mail accounts, and I want both copies). In this case, I would be downloading mails for a long time. I can do it, but first I have to prepare a rule to move them somewhere else till the box empties. Or perhaps I can find or do a hack to correct the from header (first I'll have to get a raw copy of one).

If you are using fetchmail to gmail, it will only retrieve *new* mail unless you configure it otherwise. It will only see mail in the http *inbox*. Make sure that you have moved anything you don't want to retrieve from the *inbox* to "all mail".

Well, the http inbox is empty. The pop3 handler was feeding me all seen email since last December. They must keep one index for pop retrieval, another for imap; and when you fetch email, their http index get updated and emptied, too. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjqlZ8ACgkQtTMYHG2NR9XKqACgix97tn9l0qmDbPSctI1KXrLi GgYAn3SPkpRN1G02MiZazycGvUeNS/kU =i7gX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-06 at 20:01 -0400, Patrick Shanahan wrote:

* Carlos E. R. <> [10-06-08 18:49]:

...

Well, the http inbox is empty. The pop3 handler was feeding me all seen email since last December. They must keep one index for pop retrieval, another for imap; and when you fetch email, their http index get updated and emptied, too.

How are you fetching mail? I don't use their redirect. In fact, I only use their service to collect and retain mail. I do a pop3 fetch with fetchmail.

Same thing. fetchmail -> postfix -> procmail. The only difference, for now, is that I tell fetchmail to use imap when I know it is supported, becasue it is safer when downloading batches, emails are flagged as retrieved inmediately; an interrupted pop3 session will repeat all fetches. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjqq5wACgkQtTMYHG2NR9Ws3wCfYfwYnntBhSBO4CISsaWyfBLH 19EAn2COsIipTCMEYkalq4QPXu77YxJQ =li62 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-07 at 07:45 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

Bad news: the imap server and the pop server are not synced. I started getting all my emails since 2007-12-28, so I had to kill fetchmail, which must be thousands. I'll have to return to imap :-(

You could do a manual POP3 session and just delete emails.

Via telnet? Impossible. Gmail uses encrypted mode login (ssl). Mmmm... perhaps "kshowmail", but the version I have does not support ssl, afaik. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjrM8MACgkQtTMYHG2NR9VTGACdECjrZa7s8c0YpT0HjEvOiXup YkoAn3PCCC2RH7aJEVAXFUM27wn2gApC =VoGx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-07 at 12:13 +0200, Per Jessen wrote:

...

...

You could do a manual POP3 session and just delete emails.

Via telnet? Impossible. Gmail uses encrypted mode login (ssl). Mmmm... perhaps "kshowmail", but the version I have does not support ssl, afaik.

POP3S ? Hmm, well. Maybe avoid gmail altogether? :-)

X'-) No, it's just another nuisance. I can clear that mailbox even if I have to download them all again, just I'd do some extra filtering to put them aside. Or I keep using imap with another nuisance. Dunno. I'm trying to recompile kshowmail to check what it supports. [...] Surprise! Kshowmail does support ssl (at least version 3.3.0 (kde3 only) does). I'm testing it right now. [...] It only displays 1400 emails at a time (a month, roughly). Trying to delete that bunch takes long and times out, so I'm trying to delete 500 now. [...] Ah, no, I can increase the timeout and delete a larger bunch. Also, I got a private reply; it is possible to connect to gmail on a terminal: openssl s_client -connect pop.gmail.com:pop3s -crlf -quiet but it doesn't work: cer@nimrodel:~> openssl s_client -connect pop.gmail.com:pop3s -crlf -quiet depth=0 /C=US/ST=California/L=Mountain View/O=Google Inc./CN=pop.gmail.com verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 /C=US/ST=California/L=Mountain View/O=Google Inc./CN=pop.gmail.com verify error:num=27:certificate not trusted verify return:1 depth=0 /C=US/ST=California/L=Mountain View/O=Google Inc./CN=pop.gmail.com verify error:num=21:unable to verify the first certificate verify return:1 +OK Gpop ready for requests from 81.*.*.* 5pf541900eyf.7 user ............. +OK send PASS pass ................. +OK Welcome. dele * - -ERR malformed command 5pf541900eyf.7 read:errno=0 cer@nimrodel:~> It appears I'm to use that "5pf541900eyf.7" string somehow :-? I have also learned the root cause of pop3 having so much mail in the queue: it is in my gmail webmail config: POP Download: Learn more 1. Status: POP is enabled for all mail that has arrived since 2007-12-29 ( ) Enable POP for all mail (even mail that's already been downloaded) ( ) Enable POP for mail that arrives from now on ( ) Disable POP so that's the reason. I can mark the 2 option and be done with deleting mails, and use pop3 instead of imap again. [...] Done, works. I have also read a thread talking about my problem: it appears they use 7 bits, and any char above 127 is replaced with "?". It also happened inside the body of email when using imap, and this part has been solved. The problem with the headers I dunno. http://groups.google.com/group/Gmail-Help-POP-and-IMAP-en/browse_thread/thread/c004f1207c045967/6a6845effb294f9d?lnk=gst&q= [,,,] I have found a "known problems link" here: https://mail.google.com/support/bin/static.py?page=known_issues.cs Searching there for "imap", the first one is the problem I have: Non-Latin characters can corrupt message headers Message headers contain technical information necessary for the successful delivery of messages between email servers. Gmail's IMAP implementation re-encodes the information stored in message headers, but non-ASCII characters may become garbled. For example, this can affect the 'To:' line in an email message if a name is written in a language that uses non-Latin characters. Several issues can result from corrupt message headers, including delivery problems. The Gmail Team is working to resolve this issue. And there is a "report button", which only gives a "thanks!" and no place to write anything. I assume they know about it and want no further reports. They are not very fast solving issues, it seems... this problem has been active for almost a year :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjsqy0ACgkQtTMYHG2NR9UQkQCgi3rTzEOPp9ikKPH91iqdv0h5 qX0An30jA+KeCn076GRi3YkrPnDvTnDd =lTCz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-10-08 at 15:12 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

+OK Welcome. dele * - -ERR malformed command 5pf541900eyf.7 read:errno=0 cer@nimrodel:~>

It appears I'm to use that "5pf541900eyf.7" string somehow :-?

I don't think you can do 'DELE *', I think you have to do it by numbers.

That's what I thought, but I was told otherwise. But it gives the same error with any command: for example dele 1 after a list. Anyway, I found the shortcut in gmail webmail configuration. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjsxYIACgkQtTMYHG2NR9XweQCghsv2VKrdXxyJlZeL/TIu+mMj fOQAnjIIeCrC3b/MiMYOTpVTsN99Y2/b =Fkq1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

j debert wrote:

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

Carlos E. R. さんは書きました: | | | Hi, | | when I get an email going to my gmail account, with a from address | with accented letters, it is corrupted; copying directly from the | mbox file with less, I see this: | | Date: Mon, 6 Oct 2008 11:48:18 +0200 | From: =?ISO-8859-1?Q? "Camale=F3n" _ <....@gmail.com>, | ?=@nimrodel.valinor | To: "opensuse-es@opensuse.org" | |

The header is not in a valid RFC2822 format. There is no guarantee that any MTA or any MUA will not mangle such a header since it is not standard.

The header above was already mangled - the original was fine.

See RFC2822. Also look at RFC5322, very recently published, which supersedes RFC2822.

Interesting. Any specific changes worth mentioning? /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: [ This email was lost during the power outage, so I repost it. ] [ 20081010 15:07:26 +0200 ] On Thursday, 2008-10-09 at 17:20 -0700, j debert wrote:

Carlos E. R. さんは書きました:

| | | Hi, | | when I get an email going to my gmail account, with a from address with | accented letters, it is corrupted; copying directly from the mbox file | with less, I see this: | | Date: Mon, 6 Oct 2008 11:48:18 +0200 | From: =?ISO-8859-1?Q? "Camale=F3n" _ <....@gmail.com>, | ?=@nimrodel.valinor | To: "opensuse-es@opensuse.org" | |

The header is not in a valid RFC2822 format. There is no guarantee that any MTA or any MUA will not mangle such a header since it is not standard.

The header may have been been converted into MIME by gmail. That is a no-no but it was apparently intended to only work with the gmail web interface. Such headers will likely be mangled by Postfix, which is RFC compliant, and probably by fetchmail, procmail, spamassassin and amavis as well.

Well, that's the already garbled header after been fetched. The original is probably closer to this: Date: Mon, 6 Oct 2008 11:48:18 +0200 From: "=?ISO-8859-1?Q?Camale=F3n?=" <....@gmail.com> To: "opensuse-es@opensuse.org" but I'd have to intercept an imap session to make sure of what I'm really getting. I also mentioned that the problem is known to gmail: https://mail.google.com/support/bin/static.py?page=known_issues.cs ] Non-Latin characters can corrupt message headers ] ] Message headers contain technical information necessary for the ] successful delivery of messages between email servers. Gmail's IMAP ] implementation re-encodes the information stored in message headers, ] but non-ASCII characters may become garbled. For example, this can ] affect the 'To:' line in an email message if a name is written in a ] language that uses non-Latin characters. Several issues can result ] from corrupt message headers, including delivery problems. ] ] The Gmail Team is working to resolve this issue. I'm trying to capture an imap session, but I can't. I use this procedure: pruebas@nimrodel:~> openssl s_client -connect imap.gmail.com.:imaps | tee gmail_imap.log depth=0 /C=US/ST=California/L=Mountain View/O=Google Inc/CN=imap.gmail.com ... * OK Gimap ready for requests from 88.24.186.237 z34if130280ikz.0 A0001 CAPABILITY * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA XLIST CHILDREN XYZZY A0001 OK Thats all she wrote! z34if130280ikz.0 A002 LOGIN "username" "password" A002 OK username authenticated (Success) A0003 SELECT "INBOX" Here I should be getting something like: " * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)", but I get nothing. Nothing I type produces any result. I have to type "control-D". Even the log file halts there: A002 OK username authenticated (Success) So the connection breaks somehow, gmail gets stuck. I have tested the procedure locally, against my imapd, and it works. On a previous test with gmail, before I knew the commands (nor that I know them now), I got further than that point. What can I do? I have fired a fetchmail session to try getting to gmail imap, and it worked fine, I got the test email I had sent with accents. Oct 10 14:18:37 nimrodel fetchmail[10543]: IMAP< A0002 OK username authenticated (Success) Oct 10 14:18:37 nimrodel fetchmail[10543]: IMAP> A0003 SELECT "INBOX" Oct 10 14:18:38 nimrodel fetchmail[10543]: IMAP< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) ... But there is no way I know of intercepting the raw data fetchmail gets. Interestingly enough, the test messages I sent to my gmail account were not broken, the headers get here correctly: From: =?UTF-8?Q?Carlos_E=2ER=2E_--Ac=C3=A9nto--?= Subject: =?UTF-8?Q?Prueba_ac=C3=A9ntos_en_gmail?= which displays correctly as: From: Carlos E.R. --Acénto-- Subject: Prueba acéntos en gmail So, either they have repaired the problem, or the problem is only with latin, not utf-8. Just a moment... yes, repaired: Date: Thu, 9 Oct 2008 23:25:38 +0200 From: "=?ISO-8859-1?Q?Camale=F3n?=" <....@gmail.com> To: "opensuse-es@opensuse.org" which displays correctly too. HA! So babbling here has made them repair the problem. Go figure! :-O Thanks to whoever it was, I'll have a drink to his/her health, who is invited - virtually, that is. Can't email a drink :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjxJvYACgkQtTMYHG2NR9Uo7gCgjZwffwugWTBSPUXf0oZXlEWJ oVoAn3n+NV52n6uTRUMaLjOLOanUPsVn =mfCJ -----END PGP SIGNATURE-----