Re: crm114 and procmail: eating mails

Bill Y <[email protected]>
Newsgroups gmane.mail.spam.crm114
Message-ID <[email protected]>
   From: Antoine Junod <[email protected]>

I was hoping Reto would answer this- he's the Procmail guru.

   Hello, World!

   I'm playing a bit with crm114, more precisely the mailfilter stuff.

   I've followed the howto and I'm a bit stuck at the integration
   part. I'm using the 20070810-BlameTheSegfault version. I'm trying to
   integrate the mailfilter.crm with procmail. Here are the lines of my
   .procmailrc file

   ### ->
   :0fw: .lockmsg
   | /usr/bin/crm114 -u /usr/share/crm114/ --fileprefix /usr/share/crm114/ mailfilter.crm

   :0
   /var/vpopmail/domains/my.domain.com/tickets/.maildir/
   ### <-

   All the crm files are in /usr/share/crm114/ directory. I'm not sure of
   what means the -u argument. But I use that setting for only one email
   address so I think it should be fine to let all that there.

Yes.  In fact, you might be able to leave off the -u stuff entirely.

   The problem is that every time I inject a mail in the system, with the
   above setup, the following line appears,

   Folder: /var/vpopmail/domains/my.domain.com/tickets/.maildir 0

   that means the mail have been eaten by the system (burp). If I remove
   the crm related lines in the .procmailrc file, the mail is not eaten:

   >From [email protected] Thu Apr 10 09:50:38 2008
     Folder: /var/vpopmail/domains/my.domain.com/tickets/.maildir 344

   Does any body have an idea of what's going on / what I'm doing wrong?

No, I don't.  Anybody else?

    - Bill Yerazunis

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.