[Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve

[Timo Sirainen]

Does procmail still log the same thing about "error writing to.."? Maybe
a slightly different script:

#!/bin/sh

file=/tmp/deliver.`date +%s`.$$
cd /tmp
cat > $file
ulimit -c unlimited
/opt/dovecot/libexec/dovecot/deliver $* < $file
code=$?
rm $file
if [ $code != 0 ]; then
  echo 'deliver failed' >> /tmp/deliver.err
fi
exit $code

On Wed, 2010-01-13 at 10:40 +0100, Steve Wagner wrote:
> Hi Timo, deliver works with the script and ive got some fails while 
> using it, but the script dose not wrote anything.
> 
> Any further ideas?
> 
> Steve
> 
> On 29.12.2009 22:19, Timo Sirainen wrote:
> > On Mon, 2009-12-28 at 14:34 +0100, Steve Wagner wrote:
> >> The only error message i have, come from procmail.log:
> >>
> >> 24918-Folder: /opt/dovecot/libexec/dovecot/deliver
> >>             3720
> >> 24919-procmail: Error while writing to
> >> "/opt/dovecot/libexec/dovecot/deliver"
> >> 24920:From KeineAntwortAdresse at web.de  Tue Dec  8 07:19:55 2009
> >
> > This probably means that deliver crashed. Maybe instead of executing
> > deliver directly, you could execute deliver.sh that works something
> > like:
> >
> > #!/bin/sh
> >
> > cd /tmp
> > ulimit -c unlimited
> > /opt/dovecot/libexec/dovecot/deliver $*
> > code=$?
> > if [ $code != 0 ]; then
> >    echo 'deliver failed'>>  /tmp/deliver.err
> > fi
> > exit $code
> >
> > Then see if deliver wrote a core file to /tmp or to user's home dir (if
> > user has one). If you do get a core file, get gdb backtrace:
> >
> > gdb /opt/dovecot/libexec/dovecot/deliver core
> > bt full
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20100119/e559891e/attachment.bin