similar to: stale procmail pids

Displaying 20 results from an estimated 20000 matches similar to: "stale procmail pids"

2005 Nov 21
1
lock file 2nd attempt for help
Hi my last post got no replies so i am trying again. FC3 dovecot 1.0 stable, 1 user has a lock file using mbox under /var/spool/mail/username from the lock file the pid files are File Descriptor Type File size Inode Path Current dir Directory 4096 6426371 /home/domain/domain127 Root dir Directory 4096 2 / Program code Regular file 1212428 1229832
2005 Sep 25
1
stable 1.0 on FC3
Hi should this worry me dovecot: POP3(chelan): file mail-index-view-sync.c: line 60 (view_sync_get_expunges): assertion failed: (ret == 0) using mbox format under /var/spool/mail/ Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Member & IPStag Holder CentralNic Accredited Reseller
2007 Jan 19
2
stale locks
Hello Timo, I'm running dovecot-1.0.rc15 (imap and pop) postfix-2.3.5,1 procmail-3.22_6 (which is my LDA) on FreeBSD 6.1-STABLE I'm still using the mbox format (I'm planning to migrate to Maildir soon), mailboxes are on an NFS filesystem. I regulary see stale dotlocks files (either from dovecot (29 bytes, hold the pid of the process) or procmail (1 byte) and processes
2017 May 17
0
per user procmail filtering and dovecot-lda
So I'm confused as to why you're piping back from procmail to dovecot LDA, rather than having procmail be the final LDA. Why not use: :0 w * ^List-ID:.*jenkinsci-dev.googlegroups.com mailing-lists/jenkinsci-dev/ (The trailing slash tells procmail that jenkinssci-dev is a maildir, not an mbox) Also, procmail is way out of date, no longer maintained, and there are "semi" known
2008 May 22
1
procmail --> deliver question
Hi there, I use dovecot-1.1-rc4, got imap, imaps, pop3 & pop3s working fine with the mbox format. I use sendmail-8.14.2 as an MTA, sendmail uses procmail as an LDA. I migrated to maildir format now, and pipe all my mail to deliver right now to be able to make use of the indexing etc... Problem is I run into some errors : #My .procmailrc PATH=/usr/bin:/usr/local/bin:/usr/sbin
1999 Apr 23
0
Forw: new procmail package
___________________________________________________________________________ Dan Yocum | Phone: (630) 840-8525 Linux/Unix System Administrator | Fax: (630) 840-6345 Computing Division OSS/FSS | email: yocum@fnal.gov .~. L Fermi National Accelerator Lab | WWW: www-oss.fnal.gov/~yocum/ /V\ I P.O. Box 500 |
2006 May 03
1
dovecot, procmail, postfix & SpamAssassin working together
Hi there, i'm trying to get dovecot, procmail, postfix & SpamAssassin working together http://www.linuxquestions.org/questions/showthread.php?t=441062 But i'm not having a lot of luck, a question about dovecot, what kind of mail box am i using? mbox? if so does anyone know if procmail can use mbox? /etc/dovecot.conf protocols = imap pop3 imap_listen = [::] pop3_listen = [::]
2006 Jul 05
2
Procmail patch for dovecot delivery
Hello! As discussed in the previous thread about "Dovecot deliver logging problem and procmail" I have made a small patch for procmail to deliver through dovecot's deliver program (or any other delivery program). So Procmail does not write the mailboxes directly any more. So delivery is done through pipes and an external program which can deliver the files. Since dovecot's
2008 Sep 17
3
procmail -> deliver: file too large
I am using procmail with deliver as recommended on the wiki to send mail snagged by SpamAssassin straight to a spam folder. It seemed to be working fine, but now I'm finding messages like this: Sep 17 12:13:47 hosty deliver(whoey): write() failed with mbox file /var/mail/whoey: File too large I don't think this is a setrlimit problem -- the host operating system is OpenBSD 4.0. My
2007 Dec 03
2
procmail/formail --> Maildir
Hello List, i switched mailformat from mbox to maildir. Now i have a little problem with procmail/formail and headermanipulation of mails. Here an example: 0 * ^From.*gmx.de | (formail -t -I"procmail: gmx.de") >> /var/spool/mail/xxxxxx So, i can add some different headerlines for later evaluation and the result is attached to inbox. Now i have the problem that i don't know
2007 Dec 14
1
imap+unix users and pop3+virtual users
This should be simple, but I'm missing something. My virtual users cannot access their mail. I would like Unix users to get their mail via imap which is deposited in /var/spool/mail/username. (This works.) I would like virtual users to get their mail via pop3 which is deposited in /var/spool/mail/vhosts/example.com/auser/mail/inbox (postfix does in fact put the mail there). Those users
2005 Jul 13
3
file locks
Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec):
2008 Sep 17
5
Converting from MBOX to Maildir broke procmail and Spamassasin and halted incoming mail
I could use some help here - As I use Dovecot I started here when trying to figure out why I could not add new mail folders under my Mac's Mail program, but could under Thunderbird. It was quickly pointed out that my system was set up to use MBOX and not MAILDIR, and some helpful links and notes were sent back and forth giving me a good clue as to how to perform the conversion
2011 Aug 19
1
dovecot deadlock with procmail
I m using dovecot 1.0.7. I m having problems in mail delivery to my mail server locally. When a user sends a mail few mails are in mail Q for longer period of time. The local delivery agent(*procmail*) is trying to deliver the mail at regular interval but it is unable to deliver. But as soon as I *restart* *dovecot* the mails in the Q are delivered immediately. I suspect it is because of locking
2008 Aug 05
0
Vacation reply with Procmail and dovecot deliver
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Giving up on the sieve plugin and switching to procmail. I found the following link: http://wiki.dovecot.org/procmail This site doesn't saying anything about needing to modify the procmail source code like here: http://dovecot.org/pipermail/dovecot/2006-July/014656.html Thos shows how to make procmail work with dovecot deliver program. So
2006 Jun 03
3
Maildir, procmail, and locks
I'm using procmail as the local delivery agent for Maildir style mailboxes. I discovered that I was able to send mail to other users but was unable to send mail to myself. Examples from verbose procmail log: **** Successful message to another user **** procmail: [24589] Fri Jun 2 15:03:34 2006 procmail: Assigning
2014 Jun 13
1
procmail and dovecot
Does anyone know how to get procmail and dovecot to play happily together with mboxes? I'm on Centos 6.5, fully patched. I'm getting tons of lock timeouts which is killing performance. I tried using dovecot's lda from procmail, which prompted many adjustments to selinux, which I managed, but it still gives permission problems, and I haven't succeeded in getting it to deliver
2014 Nov 21
1
Centos 6.6 procmail trouble
I have a 6.5 machine that had everything set up and working correctly (fetchmail, sendmail w/ starttls, procmail, spamassassin) but the MB cratered. I bought a new machine, and installed Centos 6.6 and all is not well. I used the config from the previous incarnation (via backups) for fetchmail (works fine), sendmail (works fine for sending via relay and tls), but procmail now refuses to pick up
2009 Apr 03
0
procmail can't invoke spamc/spamassassin in 5.3 due to SElinux denials
I just discovered that my spam filters are not being properly executed in CentOS 5.3 because when procmail attempts to invoke spamc. I have spamd running properly, and can invoke spamassassin and spamc from the bash prompt manually without any issues, however procmail fails with "permission denied" then bails. Watching the procmail.log I get the following: procmail: Executing
2006 Jul 19
1
CentOS 4.3/postfix/procmail lock failures
Hello, What is the proper solution to the problem below the sig? For a similar issue, Phillip Guenther, procmail's maintainer, at <http://article.gmane.org/gmane.mail.procmail/1623/match=error+writing+var+spool+mail> suggests "chmod g+s /usr/bin/procmail", but I'm reluctant. There are also suggestions that in this configuration the packager must make certain that