(answering both to LukreMe and Dallman in one message:
LukreMe wrote:
Point out to the maintainers of those lists that Message-id MUST BE
UNIQUE
In a few cases, it would be like talking to a wall, but anyway,
something else must be going on. See below.
Dallman wrote:
My suggestion would be one that I saw someone else write the other
day. Please turn on verbose logging and submit a log extract of the
failure.
I never received that answer, was it in this thread? In any case, I've
looked directly into the msgid cache, and found that some Msgid are
truncated, or so it looks to me:
# more msgid.cache
<46F84B1B(_dot_)4080105(_at_)ntm(_dot_)org>.net>06CrT014736(_at_)pimin(_dot_)wan(_dot_)vpn>1906797
etc etc... see the ".net>" piece? isn't that a truncated record? Also,
the log file does contain lines like:
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."
There are no "Lock failure" messages related to msgid.cache
What now?
Thanks,
Marco
--
Help *everybody* love Free Standards and Free Software
http://digifreedom.net/
____________________________________________________________
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