similar to: LDA delivery problem

I was getting these errors below and after fixing it delivery errors were introduced dovecot/error_log ============== dovecot: Jul 11 06:19:28 Error: auth-worker(default): sql(user at domain.com): User query failed: Table 'postfix.users' doesn't exist deliver(user at domain.com): Jul 11 06:19:28 Error: BUG: Unexpected input from auth master: FAIL 1 dovecot: Jul 11 06:21:41 Error:

Hi, I'm using dovecot 2.1.7 on debian Squeeze with ldap integration. Almost everything is working fine and I would link to thank all developers for this amazing piece of software. But after changing my qmail-ldap to do LDA integration get all the benefits from LDA and sieve, some emails return with failure like this: <sar at mondialline.com.br>: lda(sar): Fatal: Unknown argument: sar

Hi all, I'm testing a dovecot-2.0-beta4 and it is great so far, except that I can't get the sieve plugin for the LDA configured. It doesn't find the user's homedir and uses /tmp instead. Thus it never finds any sieve scripts. The log shows that the SQL queries return the correct home path, namely /mnt/data/vmail/example.com/me dovecot: auth: prefetch(me at example.com): passdb

Hi I'm very new to Dovecot (been using Courier for 5 years), but I've been persuaded of the merits of Dovecot and since the server needs upgrading that seems like the perfect time/excuse. On a test server, I set up postfix and installed Dovecot (running 32-bit Debian Squeeze, installed from apt-get). I mirrored the mail store (Maildirs, for historical reasons located under

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

Hi! I've upgraded from 2.0.11 to 2.0.12. I've experienced errors during delivery with dovecot-lda. The error log attached contains the errors. Since then I had to downgrade to 2.0.11, to make it work again. When starting 2.0.12, it couldn't chown() the files under /var/dovecot (eg.: dict) to the user specified in the configuration file. Configuration: # doveconf -n # 2.0.11:

Hello list, I'm really hoping someone can point me in the right direction on this. I set up a server using Postfix with LDAP lookups to Active Directory. Postfix delivers to maildir. Dovecot IMAP and POP are working correctly using PAM Kerberos to authenticate via Active Directory. I want to add spam filtering, so I'm trying to set up Postfix to use dspam which is then supposed to use

Can anyone give me an idea of whether or not dovecot-lda can solve the following issue: We seem to have constantly-corrupting dovecot* files for people who fit one (or more) of the following categories: 1) 1000+ message inboxes; 2) multiple clients simultaneously checking mail; 3) people receiving a lot of mail, and/or the server receiving and trying to deliver a single message to all users at

Hi, I'm migrating an existing dovecot (1. series) to new hardware. The new dovecot is a 2. series. I copied the old config and did a doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf Then I moved the dovecot-2.conf to dovecot.conf and restarted dovecot. When Postfix tries to deliver a message I get this error : 2013-09-16 11:00:10 auth: Fatal: net_connect_unix(auth-worker) in

Scenario: Sogo/Mysql+Postfix+Dovecot(only IMAP)+LDAP (Active Directory) To make clean the understand of my issue I've performed those step go to /var/vmail/utente2 and perform in this directory "rm -rf *" After I send email to utente2 via "telenet localhost 25" I return to /var/vmail/utente2 and perform "ls -la" that shows me: maildir |-maildir |-cur

No support help needed, just a success report having Dovecot integrate with Vexim (exim with web based frontend and sql db): http://silverwraith.com/vexim/ Just wanted to forward some configs to the list if anyone finds them useful. I just switched from vexim's normal "virtual_delivery" to "dovecot_virtual_delivery" so I could use sieve, which works nicely with

[apologies for postfix/dovecot cross-post] How, exactly, do postfix and dovecot communicate when postfix attempts to determine whether to deliver a message to the dovecot LDA, or to bounce it? In other words, how does postfix decide to bounce foo, and deliver bar, in these log messages: postfix/pipe[11857]: 933BCA071A: to=<foo at example.com>, relay=dovecot, ... status=bounced (user

Hello all, Is there a way to use LMTP (or LDA) so that maildir index and dovecot-uidlist are not updated? My setup is such that mail delivery sees user's maildir as write only. This setup works well when using postfix for mail delivery, but when I try to switch to dovecot LMTP the lmtp process wants to read the dovecot-uidlist and fails on insufficient privileges. Is there a way around this

We're investigating the possibiliy to migrate our mail system from Sendmail+Cyrus to Sendmail+Dovecot. The system must use authentication against Windows AD (supposedly using LDAP) and must use virtual hosting. So far we managed to work around a bug reported in [1], and IMAP/POP3 authentication on LDAP works OK. LDAP auth is set up using binds (Cyrus and Ejabberd authenticate against the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 15 Mar 2014, Alessandro Menti wrote: Dear Alessandro, see below mail_location, SQL query and debug output ... . IMHO, the behaviour matches your config. > I'm setting up a Postfix+Dovecot stack with virtual domains and public > mailboxes. > > I set up a shared mailbox "office at mydomain.com" as described in the

I'm trying to follow the instructions for configuring Dovecot LMTP with postfix for virtual domains but whenever mail arrives, in /var/log/maillog, I see Sep 23 16:01:20 mybox postfix/pipe[572]: 999C83206C6: to=< user at mytest.domain.com>, relay=dovecot, delay=0.08, delays=0.04/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: pipe: fatal: pipe_command: execvp

Hi I've added a server-side feature where authenticated customers sending through our SMTP server have their outbound mail copied to their Sent folder (like Gmail does). The delivery script called by qmail calls dovecot-lda to deliver it to the user's Sent folder. The problem now, is that the Sent folder shows the mail as unread, which MUAs flag (and notify, in the case of some).

Hello, I try to set up dovecot LDA with virtual domains/mailboxes to use sieve. I use dovecot 1.0_rc7 with sieve dovecot-sieve-20060726 . All datas about the virtual domains and mailboxes are stored in a mysql-database. And without using the LDA delifer agent, everything works fine. But when I try to use LDA (even without sieve), I got a delivery failture. I followed the wiki-howto

Hi I currently have to execute the following command everytime I restart Dovecot : chown dovenull:vmail /var/run/dovecot/login What should I change in my config files to avoidhaving to do this ? thanks yann ========= Dovecot -n: ========= # 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.0 ext4 auth_debug = yes auth_mechanisms = plain login

In upgrading from 2.0.2 to 2.0.3, Dovecot deliver has started putting new emails into user at host/.user at host/new instead of user at host/new. This change was reversed by downgrading to 2.0.2, so it's due to the minor version change. Has anyone else seen this? dovecot.conf follows: # 2.0.0: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.2-xenU i686 Debian 5.0.5 ext3 auth_mechanisms =