similar to: No subject

Hi, The bug reported in http://dovecot.org/list/dovecot/2006-July/014786.html still exists in 1.0.rc6 % grep "$ ./configure" dovecot-1.0.rc6/config.log $ ./configure --prefix=/srv/software/dovecot Install prefix ...................... : /srv/software/dovecot File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method

This part of the body will be zapped by Dovecot's deliver... This is bad.... Injecting the message: % cat /tmp/mail.txt | /var/qmail/bin/qmail-inject Having qmail process the message: % sudo /var/qmail/rc status: local 0/10 remote 0/20 new msg 1596241 info msg 1596241: bytes 364 from <csa at csa-net.dk> qp 23105 uid 1000 starting delivery 1: msg 1596241 to local csa at csa-net.dk

Hi, I'm using Dovecot's (1.0.rc2) 'deliver' (no sieve) as LDA - calling it from a .qmail file. It seems that 'deliver' destroys "message/rfc822" attachments (forward as attachment). My .qmail file looks like this, and use qmail to deliver a copy directly to my Maildir, and 'deliver' to deliver a second copy of the same message to the same Maildir: %

Testing - mail -------------------- As we see, Dovecot's 'deliver' zapped everything in the message from and including the MBOX From line.... If more info is needed, please let me know. Regards /Claus A

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

Hi, we are using dovecot's deliver to deliver mails to a virtual mailbox tree owned by the vmail user, by piping the message to the following command spawned by vmail: /usr/bin/env HOME=/srv/vmail/mydomain.ch/myaccount /usr/lib/dovecot/deliver When a message is delivered to an account that has reached its quotum, deliver issues a failure message saying: From: Mail Delivery Subsystem

Hi, I'm trying to get Dovecot's deliver to create and use mailboxen with one uid per user. Reading the wiki, I decided to go with the sudo attempt, but I'm stuck because deliver fails to create the intermediate directories. The auth.log has this on the matter: sudo: dovelda : TTY=unknown ; PWD=/var/spool/postfix ; USER=root ; COMMAND=/usr/lib/dovecot/deliver -f toni at

From the digest: On Aug 14, 2007, at 1:04 PM, dovecot-request at dovecot.org wrote: other messages cut out? > > > Message: 9 > Date: Tue, 14 Aug 2007 19:03:58 +0200 > From: martin f krafft <madduck at madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot at dovecot.org > Message-ID: <20070814170358.GA17390 at

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I

valid incoming email. It is rare, but it does occasionally happen on large, busy systems. Clearly it is fundamentally an "nscd" bug. But that bug is nevertheless out there, in the wild, on such systems, potentially affecting dovecot's delivery of valid user email. We have had a source code hack since October (in "deliver.c", simply replacing a "return ret"

Hi, I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through a postfix daemon on the same box. I'm talking about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS 5 host). Configuration ------------- # /etc/dovecot.conf ssl_cert_file: /etc/pki/selfmade/server.crt ssl_key_file: /etc/pki/selfmade/server.key login_dir:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 18 Jan 2015, alvin wrote: > > - Configuration > FreeBSD-9.3 > sendmail -d0.1 == sendmail-8.14.9 <<-- > dovecot --version == dovecot-2.2.15 > > # =================================================================== > # I'm trying to get sendmail to invoke dovecot.m4 ( dovecot-lda ) to > # deliver

Hi there, I have two questions: - Is there a dovecot documentation for developers (apart from the source itself)? - In the site I am concerned with, it happens very often that one

hi all, i've exim 4.53RC2 + dovecot-cvs on OSX 10.4.2. i'm working on implementing recipient-delimiters for delivery from exim to a user's imap store using dovecot's cvs-lda. reading on the wiki (Jakob's latest comments?): " ... the part after the delimiter is passed to the lda as an additional parameter. so dovecot-lda should handle that parameter and leave the

home FROM mailbox WHERE username = '%u' Added the following to a users maildir: .dovecot.sieve require "fileinto"; fileinto "test"; --- Restart all daemons.. Mail still delivers to inbox. Nothing appears in /var/log/maillog or /usr/local/vmail/dovecot-deliver.log that shows anything but the message being delivered to the inbox. HELP! Brent.

Hi, I've read at least one e-mail on this list about making delivered-to in lmtpd optional, but now I need this too, so I made a patch. The default remains as is now (enabled). Rationale: I would like to dsync users and I have catchall POP mailboxes (meaning: a single mailbox gets the mails for a lot of e-mail addresses). If I deliver the e-mails to Dovecot's lmtpd as the original

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

Hi, I'm transitioning my server over from using the deliver LDA and LMTP. Suddenly a bunch of sieve filters stopped working, and I noticed the contents of the Delivered-To header are different. Using Dovecot's deliver LDA, the contents are a bare email address (foo at bar.com). Using Dovecot LMTP, they are in brackets (<foo at bar.com>). Is there a reason why this isn't

Greetings - I'm having trouble working out where to alter this behaviour (so please forgive me if it turns out to be an Exim thing rather than Dovecot!)... My test service is using Exim as the MTA and Dovecot's "deliver" for the LDA. We are using Maildir mailboxes with filestore quotas. When I send a large test message to myself that cannot be delivered because I

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