Your message dated Thu, 2 Oct 2014 02:16:56 +0200 (CEST)
with message-id <[email protected]>
and subject line Re: Bug#763586: procmail: Procmail will not deliver to 
~/mail/inbox
has caused the Debian Bug report #763586,
regarding procmail: Procmail will not deliver to ~/mail/inbox
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
763586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763586
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: procmail
Version: 3.22-22
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages procmail depends on:
ii  libc6  2.19-11

Versions of packages procmail recommends:
ii  fetchmail                     6.3.26-1
ii  ssmtp [mail-transport-agent]  2.64-8

procmail suggests no packages.

-- no debconf information

I just rebuilt my server a few days ago, installing Debian "jessie" from 
scratch.  Previously it ran "wheezy".  I am using fetchmail and procmail to 
deliver the inbound mail to the users, but despite setting up the 
configurations so the mail will be delivered to /home/<user>/mail/inbox, 
procmail insists on delivering to /var/mail/<user>.  I have tried everything of 
which I can think, to no avail.  For temporary purposes, I have a cron script 
running that detects any new mail and tosses it to the appropriate inbox, but 
this causes an additional delay of up to 2 minutes in mail delivery, and in any 
case represents something of a kludge.

/etc/fetchmailrc (also in ~/.fetchmailrc):
# Configuration created Sat Jan  9 00:35:57 2010 by fetchmailconf 1.54 
$Revision: 5165 $
set no syslog
set logfile "/var/log/fetchmail.log"
set postmaster "postmaster"
set nobouncemail
set no spambounce
set properties ""
set daemon 60
poll mail.xxxxxxxxx.net via mail.xxxxxxxxx.net
 with proto POP3
       user 'lrhorer' there with password 'XXXXXXXXXXXX' is 'lrhorer' here 
options fetchall forcecr stripcr
 mda "/usr/bin/procmail -f %F -d %T"
    user 'ljrhorer' there with password 'XXXXXXXXXXXX' is 'ljrhorer' here 
options fetchall forcecr stripcr

~/.procmailrc:
# .procmailrc
# routes incoming mail to appropriate mailboxes
PATH=/usr/bin:/usr/local/bin
MAILDIR=$HOME/Mail
PMDIR=/var/log
LOGFILE=$PMDIR/procmail.log
LOGABSTRACT=no
SHELL=/bin/sh

~/.forward:
"|IFS=' '&&exec /usr/bin/procmail -f-||exit 75 #user"

--- End Message ---
--- Begin Message ---
Hello.

Your problem is hardly a bug in procmail but most probably a bad
configuration on your side.

You say that you want your email at /home/<user>/mail/inbox but
your .procmailrc file says MAILDIR=$HOME/Mail (note the capital M).

My guess is that procmail waits for a while for "Mail" to exist.
After a while, procmail gives up and decides to deliver to
/var/mail as a last resort.

You could easily tell if this is the case or not by looking at the log
file, but you also did this:

> PMDIR=/var/log
> LOGFILE=$PMDIR/procmail.log

which IMHO is not very orthodox and I don't think it will work,
because by the time procmail is reading .procmailrc, it lost its
setuid-root privileges and most probably the user for which email is
being delivered has not write permission to such logfile.

You might better use a log file which is owned by the user for which
email is being delivered (i.e. somewhere under $HOME).

You might also want to simplify yout .forward file:

> "|IFS=' '&&exec /usr/bin/procmail -f-||exit 75 #user"

Such convoluted example is not even in the manpage for the Debian
procmail package. If you really need a .forward file, this should be
enough:

|/usr/bin/procmail


Hope this helps.

--- End Message ---

Reply via email to