Bug 1544 - Issue receiving mail from local spool
Summary: Issue receiving mail from local spool
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.3.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
: 1545 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-05 22:48 UTC by Jason Stare
Modified: 2008-03-10 10:33 UTC (History)
0 users

See Also:


Attachments

Description Jason Stare 2008-03-05 22:48:15 UTC
Please bear with me, this is my first bug report and I'm not sure exactly what information you might need, but I'll explain the problem I'm having as best I can.

Up front, though, I'm not sure if this is a problem with Claws Mail or with procmail, but the problem I'm experiencing is similar to bug #1434:

  http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1434

and I'm unable to reproduce the problem at will, making the problem difficult to troubleshoot.

We're using a local delivery method where procmail delivers mail to an NFS-mounted mailspool file (/var/mail/<username>) that claws picks up. Unlike the bug link above, our messages do not get out of sync.

Occasionally, I run into a problem where Claws Mail won't pickup the mail from the spool file because, for some reason, the first character in the spool file is missing. 

For example, a normal spool file will begin with:

  From user@foo.com  Wed Mar  5 16:30:41 2008

but we end up with this:

  rom user@foo.com  Wed Mar  5 16:30:41 2008

and CM refuses to pull in the spool file because of the missing character.

I'm not sure what causes the missing "F" or why CM refuses to import the mail with it missing, but my administrative staff claims it's because CM isn't doing file locking properly. As a result, they've just written the problem off as a client issue and I've been left to fend for myself.

Any information you may need to help me track this down, I'll gladly provide.

My configure command that I use to build CM is:

./configure --prefix=${HOME}/platform/${CPU} \
--enable-shared \
--disable-static \
--disable-valgrind \
--disable-libetpan \
--disable-clamav-plugin \
--disable-trayicon-plugin \
--disable-spamassassin-plugin \
--disable-jpilot \
--with-aspell-prefix=${HOME}/platform/${CPU} \
--with-aspell-libs=${HOME}/platform/${CPU}/lib \
--with-aspell-includes=${HOME}/platform/${CPU}/include

and I build the pdf_viewer plugin using:

./configure --prefix=${HOME}/platform/${CPU} \
--enable-shared \
--disable-static

Again, given my inability to reproduce this problem at will, I'm not sure where the problem lies, so any help in either fixing it or at least pointing to where the issue lies would be extremely helpful.
Comment 1 Colin Leroy 2008-03-06 07:22:39 UTC
*** Bug 1545 has been marked as a duplicate of this bug. ***
Comment 2 Paul 2008-03-06 08:34:31 UTC
Which version of procmail do your administrative staff run? I've read that this behaviour, (dropping the 'F' off 'From'), is a procmail bug which is fixed in procmail 3.22
Comment 3 Brian Morrison 2008-03-06 09:17:30 UTC
From what I've seen, the fix is in 3.23pre but not in 3.22, and that pre version is from 2001 so their release schedule is glacial.
Comment 4 Colin Leroy 2008-03-10 10:33:11 UTC
Marking INVALID as it looks like a procmail bug. (Claws Mail does locking properly).
Comment 5 users 2015-08-04 10:10:03 UTC
Changes related to this bug have been committed.
Please check latest Git and update the bug accordingly.
You can also get the patch from:
http://git.claws-mail.org/

++ ChangeLog	2015-08-04 10:10:02.933791380 +0200
http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=d92be0be8339026a03b6d41ff9726d58a2cc17e0
Merge: 2223605 200a466
Author: Colin Leroy <colin@colino.net>
Date:   Tue Aug 4 10:10:02 2015 +0200

    Merge branch 'master' of file:///home/git/claws

http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=200a466aad1859b890283e959c715c279f04373c
Author: Andrej Kacian <ticho@claws-mail.org>
Date:   Tue Aug 4 09:18:19 2015 +0200

    Do not build libfeed if RSSyl plugin is disabled.
    
    Closes bug #1544, fix based on patch by Jean Diraison.

Note You need to log in before you can comment on or make changes to this bug.