Re: [Dovecot] xexec and dovecot 1.1
For the 'Copy to Sent' function... if you sent a message somehow using the IMAP connection, maybe you could save the Client having to upload the same message AGAIN just to copy it to the Sent folder (think 10MB email sent over a 512Kb connection)... No need for a new extension, it's easier to make your MTA deliver a copy of outgoing mail to the 'Sent' folder for those users that want it. OK, I'm game. Design this for me assuming Postfix + Dovecot. Lets assume they are on different servers just to examine the more general situation. We can probably assume an authenticated sasl connection or else it becomes fairly intractable, but we have to assume that customers can choose their FROM address (for many setups the incoming connection might be both unauthenticated AND have random (even forged) FROM addresses...) So what should the config look like? Ed
Re: [Dovecot] sieve header :matches for multiline header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 26, 2008 at 05:38:35PM -0400, Mark E. Mallett wrote: On Mon, Mar 17, 2008 at 10:49:16PM +0300, Anton Yuzhaninov wrote: RFC3028 say: Not an answer, but note that RFC3028 has been superseded by RFC5228. ...which both refer to RFC2822 resp. RFC822 in header folding and unfolding matters, which in turn, to my (admittedly superficial scanning) have the same to say in this point (it's 2.2.3. Long Header Fields in both cases). So the OP's point seems still to hold. Regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFH63ZHBcgs9XrR2kYRAvoQAJ9GKwgGdRDyLcRJC94wZ5F8B6TY0ACeIkpc UfP/n+XUQbW2wqKOE3qO6Pc= =qw+K -END PGP SIGNATURE-
[Dovecot] pop3 with out LAST command
Hi, One user has your client in Yahoo Webmail and he had configured pop3 acount with our servers. The Yahoo Webmail said to him: The server not have the LAST command. We have dovecot 1.0.10 in linux. ¿This command is in Dovecot? ¿how? Regards.
Re: [Dovecot] pop3 with out LAST command
Am Donnerstag, 27. März 2008 12:51 schrieb Antonio Casado Rodríguez: One user has your client in Yahoo Webmail and he had configured pop3 acount with our servers. The Yahoo Webmail said to him: The server not have the LAST command. We have dovecot 1.0.10 in linux. ¿This command is in Dovecot? ¿how? Set pop3_enable_last = yes in protocol pop3 section. Amon Ott -- Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571
Re: [Dovecot] dovecot-1.1.rc3 segmentation fault in fetch_bodystructure
On Tue, Mar 11, 2008 at 09:55:02AM +0100, Diego Liziero wrote: On Tue, Mar 11, 2008 at 9:09 AM, Timo Sirainen [EMAIL PROTECTED] wrote: Well, I'm not sure how you managed to cause this, but this should fix it: http://hg.dovecot.org/dovecot-1.1/rev/7e27d67d3abe Thank you Timo for the quick fix, here we have latest rc3 in a production environment. It has been used by over 600 users in the last 2 days. The most failing assertion (9694 times in 2 days) is the one I posted yesterday: Panic: IMAP(username): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(ibox-recent_flags, uid)) It happens when users are moving messages to Trash folder with thunderbird. The workaround for the user is to delete directly the messages without moving them to Trash. Today, we received several complaints about being unable to delete messages (by moving to Trash) not working, and discovered we were getting the same assertion failure as you: assertion failed: (seq_range_exists(ibox-recent_flags, uid)) The only client being used was Squirrelmail with no external access from any other client. Can you confirm that the patch Timo submited in the above link fixes this problem for 1.1rc3? If so, will this be committed for rc4 or beyond? -- Dean Brooks [EMAIL PROTECTED]
Re: [Dovecot] dovecot-1.1.rc3 segmentation fault in fetch_bodystructure
On Thu, 2008-03-27 at 12:47 -0400, Dean Brooks wrote: On Tue, Mar 11, 2008 at 09:55:02AM +0100, Diego Liziero wrote: On Tue, Mar 11, 2008 at 9:09 AM, Timo Sirainen [EMAIL PROTECTED] wrote: Well, I'm not sure how you managed to cause this, but this should fix it: http://hg.dovecot.org/dovecot-1.1/rev/7e27d67d3abe Today, we received several complaints about being unable to delete messages (by moving to Trash) not working, and discovered we were getting the same assertion failure as you: assertion failed: (seq_range_exists(ibox-recent_flags, uid)) The only client being used was Squirrelmail with no external access from any other client. Can you confirm that the patch Timo submited in the above link fixes this problem for 1.1rc3? If so, will this be committed for rc4 or beyond? The patch will be in rc4, but it's for a completely different problem. Easiest way to get rid of this problem for now is to just comment out the assert, but it would be nice if you could figure out a way to reproduce this so I could properly fix it. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] (userdb/ldap) Set home dovecot variable - How?
Hi,
you should see this related thread
http://www.dovecot.org/list/dovecot/2008-March/029206.html and
especially the two last posts.
sam
k bah a écrit :
Dovecot version dovecot-1.0.rc14-7 (opensuse)
Postfix is using Dovecot LDA.
I'm getting this error message, and I guess it's going to be a problem on my
next task, which is to set up sieve scripts.
Is there something wrong/contraditory on my config or I forgot something? I
want:
/var/dovecot-tests/: where user's inbox resides
/var/dovecot-tests/home/: home dir (users will not be system users, this home
is for sieve)
/var/dovecot-tests/data/: mbox
--- error msg --- --- --- ---
auth(default): client in: AUTH 1 PLAIN service=IMAPlip=dovecot_machine_ip rip=client_ip
auth(default): client out: CONT1
auth(default): client in: CONT 1 AHRoYWlzY2diAHRyb2NhcjEyMw==
auth(default): ldap(someuser,client_ip): bind search: base=dc=mydomain,dc=me
filter=((object
class=inetlocalmailrecipient)(uid=someuser))
auth(default): ldap(someuser,client_ip): result: mail(user)=someuser
auth(default): ldap(someuser,client_ip): bind:
dn=cn=112345,ou=people,dc=mydomain,dc=me
auth(default): client out: OK 1 user=someuser
auth(default): master in: REQUEST 9 13177 1
auth(default): ldap(someuser,client_ip): user search: base=dc=mydomain,dc=me
scope=subtree fi
lter=((objectclass=inetlocalmailrecipient)(mail=someuser)) fields=uid, uid
auth(default): master out: USER9 someuseruser=someuser
uid=1500
gid=12
imap-login: Login: user=someuser, method=PLAIN, rip=client_ip,
lip=dovecot_machine_ip
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Effective uid=1500, gid=12
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Namespace: type=private, prefix=, sep=/, inbox=yes, hidden=no,
subscriptions=no
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')mbox: data=/var/dovecot-test/data/someuser:INBOX=/var/dovecot-test/someuser
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')mbox: root=/var/dovecot-test/data/someuser,
index=/var/dovecot-test/data/someuser, inbox=/var/dovecot
-teste-mailspool/someuser
auth(default): client in: AUTH 1 PLAIN service=IMAPlip=dovecot_machine_ip rip=client_ip
resp=dGhhaXNjZ2IAdGhhaXNjZ2IAdHJvY2FyMTIz
auth(default): ldap(someuser,client_ip): bind search: base=dc=mydomain,dc=me
filter=((object
class=inetlocalmailrecipient)(uid=someuser))
auth(default): ldap(someuser,client_ip): result: mail(user)=someuser
auth(default): ldap(someuser,client_ip): bind:
dn=cn=112345,ou=people,dc=mydomain,dc=me
auth(default): client out: OK 1 user=someuser
auth(default): master in: REQUEST 10 16172 1
auth(default): ldap(someuser,client_ip): user search: base=dc=mydomain,dc=me
scope=subtree fi
lter=((objectclass=inetlocalmailrecipient)(mail=someuser)) fields=uid, uid
auth(default): master out: USER10 someuseruser=someuser
uid=1500
gid=12
imap-login: Login: user=someuser, method=PLAIN, rip=client_ip,
lip=dovecot_machine_ip
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Effective uid=1500, gid=12
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Namespace: type=private, prefix=, sep=/, inbox=yes, hidden=no,
subscriptions=no
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')mbox: data=/var/dovecot-test/data/someuser:INBOX=/var/dovecot-test/someuser
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')mbox: root=/var/dovecot-test/data/someuser,
index=/var/dovecot-test/data/someuser, inbox=/var/dovecot
-teste-mailspool/someuser
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Disconnected: Logged out
debug ('someuser' 'someuser' '' 'IMAP'
'/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB' '1500
')Disconnected: Logged out
auth(default): client in: AUTH 1 PLAIN service=IMAP
lip=dovecot_machine_ip rip=client_ip
auth(default): client out: CONT1
auth(default): client in: CONT 1 AHRoYWlzY2diAHRyb2NhcjEyMw==
auth(default): ldap(someuser,client_ip): bind search: base=dc=mydomain,dc=me
filter=((object
class=inetlocalmailrecipient)(uid=someuser))
auth(default): ldap(someuser,client_ip): result: mail(user)=someuser
auth(default): ldap(someuser,client_ip): bind:
dn=cn=112345,ou=people,dc=mydomain,dc=me
auth(default): client out: OK 1 user=someuser
auth(default): master in: REQUEST 11 70141
--- error msg --- --- --- ---
-- dovecot.conf --- --- --- ---
login_user = dovecot
mail_extra_groups = mail
valid_chroot_dirs = /var/dovecot-test
mail_location =
Re: [Dovecot] xexec and dovecot 1.1
Ed W wrote: For the 'Copy to Sent' function... if you sent a message somehow using the IMAP connection, maybe you could save the Client having to upload the same message AGAIN just to copy it to the Sent folder (think 10MB email sent over a 512Kb connection)... No need for a new extension, it's easier to make your MTA deliver a copy of outgoing mail to the 'Sent' folder for those users that want it. OK, I'm game. Design this for me assuming Postfix + Dovecot. Lets assume they are on different servers just to examine the more general situation. We can probably assume an authenticated sasl connection or else it becomes fairly intractable, but we have to assume that customers can choose their FROM address (for many setups the incoming connection might be both unauthenticated AND have random (even forged) FROM addresses...) So what should the config look like? Ed Assuming you are talking about my idea that IMAP have an outgoing mail extension and copies the outgoing message to the sent folder. After dovecot receives he outgoing message it will just do an SMTP connection to a server that is set up to receive it and relay it. smtpserver = 1.2.3.4 copyfolder = sent Is this what you are asking?
[Dovecot] Proxy Problems
Hi, I'm trying to use dovecot as a proxy as described on http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy but without much success. The problem is that when I send a IMAP login command dovecot is responding with BYE Internal login failure. Refer to server log for more information. Can anyone help me shed light on this problem? Here's the log (Username, password and IPs have been anonymised): dovecot: Mar 27 13:07:11 Info: Dovecot v1.0.rc15 starting up dovecot: Mar 27 13:07:12 Info: auth(default): passwd-file /root/ dovecot-proxy-test.passwd: Read 1 users dovecot: Mar 27 13:07:29 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.0.1 rip=192.168.0.2 resp=WWVzIEkgYW5vbnltaXNlZCB0aGlzIHRvbyA7LSk= dovecot: Mar 27 13:07:29 Info: auth(default): client out: OK 1 user=test_proxy proxy host=192.168.0.3 port=143 pass=password dovecot: Mar 27 13:07:29 Info: auth(default): master in: REQUEST 1 11786 1 dovecot: Mar 27 13:07:29 Error: auth(default): Master request 11786.1 not found dovecot: Mar 27 13:07:29 Info: auth(default): master out: NOTFOUND 1 dovecot: Mar 27 13:07:29 Info: imap-login: Internal login failure: user=test_proxy, method=PLAIN, rip=192.168.0.2, lip=192.168.0.1 And here's my config according to dovecot -n # /root/dovecot-proxy-test.conf base_dir: /var/run/dovecot-proxy-test log_path: /dev/stderr protocols: imap listen: *:10143 login_dir: /var/run/dovecot-proxy-test/login login_executable: /usr/libexec/dovecot/imap-login auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /root/dovecot-proxy-test.passwd userdb: driver: static args: uid=0 gid=0 /root/dovecot-proxy-test.passwd contains a single line: test_proxy:::proxy=y host=192.168.0.3 port=143 I am on Cent OS 5 using dovecot version 1.0.rc15 from their official yum repositories. If I connect my client directly to 192.168.0.3:143 using the same username and password everything works correctly. Thanks in advance. - Richard
Re: [Dovecot] xexec and dovecot 1.1
On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: After dovecot receives he outgoing message it will just do an SMTP connection to a server that is set up to receive it and relay it. The question I have is how would you configure the Client to do this? I guess just point it to the same server address as the incoming server? -- Best regards, Charles
Re: [Dovecot] Proxy Problems
on 3-27-2008 11:46 AM Richard Cooper spake the following: Hi, I'm trying to use dovecot as a proxy as described on http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy but without much success. The problem is that when I send a IMAP login command dovecot is responding with BYE Internal login failure. Refer to server log for more information. Can anyone help me shed light on this problem? Here's the log (Username, password and IPs have been anonymised): dovecot: Mar 27 13:07:11 Info: Dovecot v1.0.rc15 starting up dovecot: Mar 27 13:07:12 Info: auth(default): passwd-file /root/dovecot-proxy-test.passwd: Read 1 users dovecot: Mar 27 13:07:29 Info: auth(default): client in: AUTH1 PLAINservice=IMAPlip=192.168.0.1rip=192.168.0.2 resp=WWVzIEkgYW5vbnltaXNlZCB0aGlzIHRvbyA7LSk= dovecot: Mar 27 13:07:29 Info: auth(default): client out: OK1 user=test_proxyproxyhost=192.168.0.3port=143pass=password dovecot: Mar 27 13:07:29 Info: auth(default): master in: REQUEST1 117861 dovecot: Mar 27 13:07:29 Error: auth(default): Master request 11786.1 not found dovecot: Mar 27 13:07:29 Info: auth(default): master out: NOTFOUND1 dovecot: Mar 27 13:07:29 Info: imap-login: Internal login failure: user=test_proxy, method=PLAIN, rip=192.168.0.2, lip=192.168.0.1 And here's my config according to dovecot -n # /root/dovecot-proxy-test.conf base_dir: /var/run/dovecot-proxy-test log_path: /dev/stderr protocols: imap listen: *:10143 login_dir: /var/run/dovecot-proxy-test/login login_executable: /usr/libexec/dovecot/imap-login auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /root/dovecot-proxy-test.passwd userdb: driver: static args: uid=0 gid=0 /root/dovecot-proxy-test.passwd contains a single line: test_proxy:::proxy=y host=192.168.0.3 port=143 I am on Cent OS 5 using dovecot version 1.0.rc15 from their official yum repositories. If I connect my client directly to 192.168.0.3:143 using the same username and password everything works correctly. Thanks in advance. - Richard Try getting a newer version of dovecot from atrpms.net and see if it works. Current is 1.0.13, at least a year newer then the release candidate you are using. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] xexec and dovecot 1.1
on 3-27-2008 11:50 AM Charles Marcus spake the following: On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: After dovecot receives he outgoing message it will just do an SMTP connection to a server that is set up to receive it and relay it. The question I have is how would you configure the Client to do this? I guess just point it to the same server address as the incoming server? Someone would have to re-write the clients also. This looks like something else that Outlook will break. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] xexec and dovecot 1.1
Charles Marcus wrote: On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: After dovecot receives he outgoing message it will just do an SMTP connection to a server that is set up to receive it and relay it. The question I have is how would you configure the Client to do this? I guess just point it to the same server address as the incoming server? Clients would have to be rewritten to support the new IMAP extensions. If the IMAP server supported outgoing email then the client would know it through CAPABILITIES. It would then not need to have any outgoing email settings. It would cut client configuration in half.
Re: [Dovecot] xexec and dovecot 1.1
On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: Clients would have to be rewritten to support the new IMAP extensions. If the IMAP server supported outgoing email then the client would know it through CAPABILITIES. It would then not need to have any outgoing email settings. It would cut client configuration in half. My server currently uses: Incoming: imap.example.com Outgoing: smtp.example.com If dovecot 'understands' smtp, then why couldn't you just point the outgoing to 'imap.example.com', so no Client mods would be needed? -- Best regards, Charles
Re: [Dovecot] xexec and dovecot 1.1
on 3-27-2008 12:30 PM Charles Marcus spake the following: On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: Clients would have to be rewritten to support the new IMAP extensions. If the IMAP server supported outgoing email then the client would know it through CAPABILITIES. It would then not need to have any outgoing email settings. It would cut client configuration in half. My server currently uses: Incoming: imap.example.com Outgoing: smtp.example.com If dovecot 'understands' smtp, then why couldn't you just point the outgoing to 'imap.example.com', so no Client mods would be needed? But the clients send to port 25 on the outgoing server, unless you force them to use something different. Port 25 is SMTP. You can have incoming and outgoing on the same server, you just need a MTA running along with the dovecot server. signature.asc Description: OpenPGP digital signature
Re: [Dovecot] xexec and dovecot 1.1
Scott Silva wrote: on 3-27-2008 12:30 PM Charles Marcus spake the following: On 3/27/2008, Marc Perkel ([EMAIL PROTECTED]) wrote: Clients would have to be rewritten to support the new IMAP extensions. If the IMAP server supported outgoing email then the client would know it through CAPABILITIES. It would then not need to have any outgoing email settings. It would cut client configuration in half. My server currently uses: Incoming: imap.example.com Outgoing: smtp.example.com If dovecot 'understands' smtp, then why couldn't you just point the outgoing to 'imap.example.com', so no Client mods would be needed? But the clients send to port 25 on the outgoing server, unless you force them to use something different. Port 25 is SMTP. You can have incoming and outgoing on the same server, you just need a MTA running along with the dovecot server. That's right. I'm assuming that anyone who is running Dovecot also runs an MTA. My idea for using IMAP as an outgoing transport is just to move the outgoing message from the client to dovecot, then dovecot hands it off locally to the MTA, and the MTA sends it to the destination. I'm not suggesting Dovecot become an MTA.
Re: [Dovecot] dovecot-1.1.rc3 segmentation fault in fetch_bodystructure
On Thu, Mar 27, 2008 at 5:47 PM, Dean Brooks [EMAIL PROTECTED] wrote:
Can you confirm that the patch Timo submited in the above link fixes
this problem for 1.1rc3? If so, will this be committed for rc4 or beyond?
No, the above patch was about another issue (segmentation fault in
fetch_bodystructure) and I forgot to change the subject about the assertion
failure you are getting.
As Timo told you, I changed the assert with a i_error waiting for a proper
fix.
Diego.
--- ./src/lib-storage/index/index-sync.c-orig 2008-03-13 16:46:
36.0 +0100
+++ ./src/lib-storage/index/index-sync.c2008-03-13 16:51:
38.0 +0100
@@ -36,7 +36,9 @@
void index_mailbox_set_recent_uid(struct index_mailbox *ibox, uint32_t uid)
{
if (uid = ibox-recent_flags_prev_uid) {
- i_assert(seq_range_exists(ibox-recent_flags, uid));
+ /*i_assert(seq_range_exists(ibox-recent_flags, uid));*/
+ if (!seq_range_exists(ibox-recent_flags, uid))
+ i_error(seq_range_exists(ibox-recent_flags,
uid));
return;
}
ibox-recent_flags_prev_uid = uid;
[Dovecot] Imap sent folder sometimes dosen't get updated in dovecot-1.1-rc3(+some current hg patches)
Yes, again, some sent emails don't get copied to sent folder. This time I get the following error: Error: IMAP(username): UIDs broken with partial sync in mbox file /maildir/username/Sent This happened at least with thunderbird and with evolution. Dovecot is running on vith fcntl locking on Centos5, sendmail should use fcntl, too. Filesystem is ext3 on drbd partition. After a grep vith dovecot.log I see the same error message also with other imap folders as well (mainly Trash imap folder). Should I try to get a rawlog? Regards, Diego.
[Dovecot] Dovecot Startup error on FreeBSD
Hi, I have installed latest Dovecot 1.0.13 on a FreeBSD 6.2 with XMail (www.xmailserver.org). It works OK except one thing: error on startup. After each reboot there are lots of such error: dovecot: Mar 28 08:54:38 Error: child 916 (login) returned error 89 dovecot: Mar 28 08:54:54 Error: imap-login: No authentication sockets found When I restart dovecot by running startup script /usr/local/etc/rc.d/dovecot.sh restart the problem disappears. I have to manually restart dovecot after each reboot. Below is used conf file $ dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: maildir:~/Maildir dotlock_use_excl: yes maildir_copy_with_hardlinks: yes mail_plugins: antispam imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: verbose: yes passdb: driver: checkpassword args: /var/MailRoot/bin/dovecot_xmail userdb: driver: static args: uid=vxmail gid=vxmail home=/var/MailRoot/domains/%d/%n allow_all_users=yes socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vxmail plugin: antispam_signature: X-DSPAM-Signature antispam_trash: Trash antispam_spam: SPAM antispam_dspam_binary: /usr/local/bin/dspam antispam_dspam_args: --user;%u I googled and found similar post at http://www.mail-archive.com/dovecot@dovecot.org/msg01793.html, http://www.mail-archive.com/dovecot@dovecot.org/msg01798.html and http://www.mail-archive.com/dovecot@dovecot.org/msg01831.html but answers there don't meet my case. I don't use sql backend. And startup script doesn't delete /var/run/dovecot/ directory after Dovecot is started. After booting when error still there I have in this directory: $ ls /var/run/dovecot auth-master dict-server login master.pid If restart dovecot (working OK): $ ls /var/run/dovecot auth-master auth-worker.960 dict-server login master.pid As we see dovecot works when there appears a file named auth-worker.960 (the number 960 changes each time it restarted). Please help me to fix this. Thanks in advance. Dien Phan
