Thunderbird, using TLS (imapS) with Dovecot, locks the Maildir/new directory for writing by procmail with

RESOLVED INVALID

Status

--
major
RESOLVED INVALID
11 years ago
10 years ago

People

(Reporter: nanno.schering, Assigned: Bienvenu)

Tracking

1.8 Branch
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.11) Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11
Build Identifier: kernel 2.6.22-14-generic

If Thunderbird is open, while using SECURE (TLS) imaps (with Dovecot), new mail arriving through Postfix in Maildir/new cannot be written there by procmail. This is the case for window and linux clients, both. This problem does NOT occur with Evolution as the mail client.
From procmail.log while TB is open:
procmail: No match on "^X-Spam-Flag: YES"
procmail: Couldn't create or rename temp file "/home/XXXX/Maildir/new/msg.A"
procmail: Assigning "LASTFOLDER=/var/mail/XXXX"
procmail: Opening "/var/mail/XXXX"
procmail: Acquiring kernel-lock
procmail: Notified comsat: "XXXX@143675:/var/mail/XXXX"


Reproducible: Always

Steps to Reproduce:
1.configure TLS on imap.
2.open Thunderbird
3.new mail arriving is announced, registered (indexed), but empty (Nod header, no body)
Actual Results:  
I am loosing mail, while Thunderbird is open.

Expected Results:  
New mail arriving should be written into new. Thunderbird is blocking this.

Thunderbird should not keep a lock the on new directory for writing
(Reporter)

Updated

11 years ago
Version: unspecified → 2.0
Is there really some way imap clients can lock a directory on the server? Even if there is, sounds like a server bug to me.
Assignee: dveditz → bienvenu
Component: Security → Networking: IMAP
Product: Thunderbird → Core
QA Contact: thunderbird → networking.imap
Version: 2.0 → 1.8 Branch
(Reporter)

Comment 2

11 years ago
Sorry, The bug is in Dovecot not Thunderbird, courier IMAPS does not have the problem.
(Reporter)

Updated

11 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
->INVALID (FIXED is only used when known code changes resolved the issue)
https://bugzilla.mozilla.org/page.cgi?id=fields.html#resolution
Resolution: FIXED → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.