On 9/24/07, M. Fioretti <mfioretti(_at_)nexaima(_dot_)net> wrote:
something else must be going on. See below.
You're right that something else must be going on, but not about what.
looked directly into the msgid cache, and found that some Msgid are
truncated, or so it looks to me:
# more msgid.cache
msgid.cache is not a text file, you can't examine it with "more". Try
strings msgid.cache | more
procmail: Lock failure on "email_base_dir/INBOX/in-waiting.lock"
procmail: Error while writing to "email_base_dir/INBOX/in-waiting"
procmail: Error while writing to "email_base_dir/INBOX/_a5C%bFu3GB.hostname."
procmail: Error while writing to "email_base_dir/INBOX/_a5C.jFu3GB.hostname."
I suspect this means that you're incorrectly attempting to use locking
with a maildir-format mailbox, but since the error is not on the
".duplicates" recipe this is likely a problem with some other part of
your procmail config. Whether that ends up being related to this is
impossible to tell.
There are no "Lock failure" messages related to msgid.cache
Does the VERBOSE=yes log show the "formail -D" executing?
My guess would be that some earlier filter in your procmail config is
damaging the messages so that they appear not to have any message-id
at all -- possibly such that procmail becomes confused and treats the
entire message header as part of the body.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail