search for: delivering

Hello, there are problems with quota dict when multiple dovecot deliver processes are launched in parallel. It can be reproduced by sending a mail with multiple different recipients - the mail is delivered OK to all recipients, but the quota are not updated correctly in sql. I looked at the code and it seems that the problem is somewhere in dict cache. If I configure in Postfix max number of

I was playing around with dovecot-1.1 and maildir++ quotas, and ran into a reproducible error with indexing. This only seems to be a problem for new maildirs. If I send a message without the quota plugin on, and "seed" the index/control files, future deliveries with the quota plugin seem to succeed without errors. Version: 1.1alpha6 OS: Debian etch/x86 (ext3 filesystem) #

Hello. I asked about the problem in http://markmail.org/message/zsry62fcig5hqka3 . And I created simple example plug-in for deliver. It is attached (I don't want to paste so much code) For compile in command-line run: # DOVECOT=<path to dovecot> gmake ...send mail... ...view dovecot lda log... # gmake clean # WITH_ONLY_HEADERS=1 DOVECOT=<path to dovecot> gmake ...send mail...

Hi there I'm redirecting e-mails from mikkel at euro123.dk to another account (mikkel2 at euro123.dk) using sieves "redirect" with sieve 1.1.3. The e-mail is redirected just fine. But deliver still creates a core dump and returns an "e-mail undeliverable" to the sending account (even though delivery is successful). My .dovecot.sieve contains just this: redirect

One of our servers running Dovecot 1.0.beta3 and dovecot-lda has failed to deliver a few messages and I can't figure out why. Very few messages bounce and I don't see any common thread between them other than time. The 15:19:11 message was a company wide announcement and the other 4 servers (identical configuration) were able to deliver it. Feb 26 20:24:46 rental deliver:

Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion failed: (ret...

Hi, I'm running dovecot (1.1.7) deliver and sieve (1.1.5) on a Fedora 9 platform, using selinux targetet mode. Most of the mail deliveries goes well, but once deliver tried to copy the mail to the /tmp directory, which it seems it not allowed by selinux. I guess that deliver wants to sanitize the mail or something and therefore copies it to /tmp. Before I ask for selinux to allow this, I

We recently upgraded to dovecot v1.0.15 (from v1.0.0 + some local fixes), and after this upgrade we've started to get a couple of failures from deliver: Jan 12 20:34:34 smtp1.ulh.mydomain.net deliver(someuser at somedomain.net): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45577c] -> /usr/local/dovecot/libexec/dovecot/deliver [0x45537c] ->

On Dec 22, 2007, at 5:00 AM, dovecot-request at dovecot.org wrote: (stuff cut out) > Message: 10 > Date: Sat, 22 Dec 2007 11:12:30 +0200 > From: arvids <arvids at mpe.lv> > Subject: [Dovecot] v1.1.beta12 deliver crashes > To: Dovecot Mailing List <dovecot at dovecot.org> > Message-ID: <200712221112.30760.arvids at mpe.lv> > Content-Type: text/plain;

Hello! Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program. Do you think this is a good concept? For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the logging configuration from the environment (as non root user): setenv INFO_LOG_PATH $HOME/deliver.log s...

...run/dovecot/login login_executable: /opt/libexec/dovecot/imap-login login_user: nobody login_processes_count: 1 auth default: verbose: yes debug: yes passdb: driver: passwd-file args: /opt/etc/passwd.imap userdb: driver: passwd-file args: /etc/passwd How can I fix this mail delivering problem? Thanks in advance for any ideas/suggestions/answers. And sorry for my bad English ;) -- Ilya Galanin

Hi all, I'm a bit baffled. I have an OS X server 10.6.8 and everything was working fine. Now however I seem to be having some issues and I'm unable to find log entries to help point me to the error. I have an alias, sales at cirrusav.com, which forwards mail to myself and two others. This works fine most of the time, but on occasion messages are not delivered to one user. It is possible

Would it be sensible/"cost effective" to make dovecot-deliver generated X-Delivered-To header(s) based on command line parameter(s)? [after striping such existing headers, before consulting sieve] I need it to: a) *clearly* mark POP/IMAP account fetched by fetchmail [with fetchmail using directly dovecot-deliver in --mda option] b) cleanly implement "shared mailboxes" with

Hello folk, I have trouble running /usr/libexec/dovecot/deliver with ACL plugin enabled from my exim configurarion. Everything is working fine if I disable plugin ACL from lda section in dovecot config. This is the string from exim.conf, which request delivery to take place: command = /usr/libexec/dovecot/deliver -e -d $local_part@$domain In dovecot error-log I see this, when deliver tries to

..."/tmp/dovecot.deliver."); -- -- -- On most of my systems, /tmp is relatively small (a few hundred MB, and sometimes on ramdisk), and I like to use /var/tmp for larger temp space. I just had a problem where I exceeded the space available in /tmp while delivering a (multi recipient) message and had to modify the above line to use an alternative location, and recompile. Would it be appropriate to make this a configurable option instead? Thanks. Feb 3 15:14:51 mh1-pl7 deliver(169 at example.com): write_full(/tmp/dovecot.deliver....) failed: No space left...

Hi, I've got the problem that dovecot's deliver prints the authentification information to the syslog. Like this: Sep 18 12:11:22 mail deliver(user at domain.tld): auth input: user=user at domain.tld Sep 18 12:11:22 mail deliver(user at domain.tld): auth input: password=XXXX Sep 18 12:11:22 mail deliver(user at domain.tld): auth input: home=/home/mail/domain.tld/user Sep 18 12:11:22

...Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" procmail: Locking "/var/spool/mail/kris.lock" procmail: Assigning "LASTFOLDER=/var/spool/mail/kris" procmail: Opening "/var/spool/mail/kris" ####" It's not working out and he falls back to delivering his mail to /var/spool/mail/%u Could you guys point me out in the right direction please ? Another question about the logging with deliver... I've put the following in my deliver.conf : deliver.conf in the lda section : log_path = /var/log/dovecot/deliver.log info_log_path = /var/log/dovecot...

Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying with an assertion failure when it delivers to my mailbox. Other mailboxes on the same system are unaffected, but I can read my mailbox fine through IMAP. Dovecot and sieve were compiled with -march=nocona -pipe -ggdb I've commented out my entire sieve script and the problem still occurs. file index-mail-headers.c: line

Hi, I get a lot of these after updating to the current 1.1 hg version: > Nov 6 16:05:35 seba deliver(jh): file mail-cache-transaction.c: line 736 (mail_cache_header_add_field): assertion failed: (cache->field_file_map[field_idx] != (uint32_t)-1) > Nov 6 16:05:35 seba deliver(jh): Raw backtrace: /usr/local/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2b) [0x80bbeab] ->

Hi! I've set up postfix(2.4.1) + dovecot(1.0-cvs) + dovecot-lda(1.0-cvs). Dovecot's deliver is running as vmail:vmail (according to postfix's master.cf). Now the problem (when receiving mail): deliver(leva): auth input: leva deliver(leva): auth input: uid=8006 deliver(leva): auth input: gid=8000 deliver(leva): auth input: home=/var/mail/virtual/leva deliver(leva): setuid(8006)