[Dovecot] Possible Caching Bug showing up as a MIME Boundary Issue
Possible Caching Bug showing up as a MIME Boundary Issue
I'm using Dovecot version 1.0.0. I was using Dovecot version 1.0.0 beta3 or alpha4. I upgraded to Dovecot 1.0.0 to make sure that was not the issue.
Over the past few weeks on a server running a stable dovecot, I have seem a few emails arriving where the MIME document structure dividers are visible. I've included a screenshot showing this.
Using OE6 as client. Have tried adding oe6-fetch-no-newmail per clients wiki but this seems to stop the ability to login at all.
I am using two different machines with Outlook Express to access the same email. The same problem will show up on both.
Usually, if I delete the .imap cache for the folder, the email comes down correctly.
My dovecot -n output is:
# /etc/dovecot.conf
listen: *:144
ssl_listen: *:994
ssl_cert_file: /usr/local/ssl/certs/stunnel.pem
ssl_key_file: /usr/local/ssl/certs/stunnel.pem
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
max_mail_processes: 50
verbose_proctitle: yes
default_mail_env: mbox:~/:INBOX=/var/spool/mail/%u
mail_location: mbox:~/:INBOX=/var/spool/mail/%u
imap_client_workarounds: outlook-idle delay-newmail
auth default:
passdb:
driver: pamuserdb:
driver: passwduserdb:
driver: prefetchThe server is on a heavily modified RedHat 7.2 on x86 box with ext3
Thanks in Advance,
KAM
On Thu, 2007-05-31 at 11:48 -0400, Kevin A. McGrail wrote:
I'm using Dovecot version 1.0.0. I was using Dovecot version 1.0.0 beta3 or alpha4. I upgraded to Dovecot 1.0.0 to make sure that was not the issue.
And after upgrade and deleting .imap/ directory this has still happened to new mails?
mail_location: mbox:~/:INBOX=/var/spool/mail/%u
I guess this might have something to do with mbox format as well, although I haven't heard other people having this problem for a long time.
When it happens, is it possible that you could send me the mbox file (through http://dovecot.org/tools/mbox-anonymize.pl is fine) and the mailbox's dovecot.index* files? The only problematic file (and the most important one in fixing this) is dovecot.index.cache which could contain email addresses, subjects and other headers.
Timo,
I continue to deal with this issue where the MIME Boundary appears on the bottom of the email and it is still happening as of Dovecot 1.0.5. Unfortunately, it continues to happen to me ONLY with one email box that I have seen and, of course, the email box has sensitive data in it.
I had been hoping the issue would occur with a folder that had something like an email from my mom's brother's cousin sending some forward of some joke that's gone around 200x's but no luck.
One update is that I have determined thanks to a colleague that if I move the email to another folder and back, the issue does not reappear so recreating this issue is a bear.
Anyway, will *just* the cache file help you because that is information we log anyway and doesn't fall under our privacy issues?
Otherwise would you be willing to login to our server via SSH and agree to SAGE's ethics guide and do the research as an administrator under those rules? http://www.sage.org/ethics/ethics_horiz.pdf
As an aside, the ethics guideline and SAGE are fantastic for ANY computer professional doing work for other people.
Regards, KAM
----- Original Message ----- From: "Timo Sirainen" <tss@iki.fi> Subject: Re: [Dovecot] Possible Caching Bug showing up as a MIME BoundaryIssue
When it happens, is it possible that you could send me the mbox file (through http://dovecot.org/tools/mbox-anonymize.pl is fine) and the mailbox's dovecot.index* files? The only problematic file (and the most important one in fixing this) is dovecot.index.cache which could contain email addresses, subjects and other headers.
On Thu, 2007-09-27 at 09:53 -0400, Kevin A. McGrail wrote:
I continue to deal with this issue where the MIME Boundary appears on the bottom of the email and it is still happening as of Dovecot 1.0.5. Unfortunately, it continues to happen to me ONLY with one email box that I have seen and, of course, the email box has sensitive data in it.
Sorry it took a while to reply. You were almost on the bottom of my "reply later" mails.
Anyway the mbox-anonymize.pl script's (that I mentioned) purpose is to modify the mbox so that it doesn't contain any sensitive data, only the mbox metadata is left there. But now that I think about it, it doesn't really help here because it also replaces all MIME headers and boundaries with 'x'..
One update is that I have determined thanks to a colleague that if I move the email to another folder and back, the issue does not reappear so recreating this issue is a bear.
Does it get fixed if you delete dovecot.index.cache and flush the client's cache to download the message again?
Anyway, will *just* the cache file help you because that is information we log anyway and doesn't fall under our privacy issues?
Not really.
Otherwise would you be willing to login to our server via SSH and agree to SAGE's ethics guide and do the research as an administrator under those rules? http://www.sage.org/ethics/ethics_horiz.pdf
That would work for me.
participants (2)
-
Kevin A. McGrail
-
Timo Sirainen