Re: [Dovecot] login processes from attacks staying for hours
On Thu, 24 Jul 2008, Kai Schaetzl wrote: Other programs have their own built-in values/parameters for timeouts, which makes sense as one program's typical timeout needs may be quite different from another one. So, each program should at least have a few *configurable* parameters that control timeouts like how long an authentication can take or when a data transfer timeout occurs. The IDLE timeout in dovecot seems to be 30 minutes. I would expect it to close any non-authenticated connection *at least* after this time - if not earlier. Indeed, as I recall, the IMAP protocol in general sets a 30 minute timeout across the board. So killing any connection with no data for that long seems like a very sane idea. Timo, what do you think? -- Asheesh. -- After the last of 16 mounting screws has been removed from an access cover, it will be discovered that the wrong access cover has been removed.
[Dovecot] Sieve Notify Error
Hello,
I'm using dovecot 1.1.1 and dovecot-sieve-1.1.5 .
I'm very interested in the notify plugin, I've tried many code which have
generated some errors (coding errors that have been arrived in the
.dovecot.sieve.err) but these errors are fixed.
But Notify is still not working, I've the following in mail.log :deliver([EMAIL
PROTECTED]): SIEVE ERROR: Unknown [unimplemented] notify method mailto:[EMAIL
PROTECTED] is my .dovecot.sieve :require [fileinto, notify];# Move spam to
spam folderif exists X-Spam-Flag { fileinto spam; # Stop here so that we
do not reply on spams stop;}notify :method mailto:[EMAIL PROTECTED]:message
Vous avez recu un message sur votre adresse; # Don't send any
further notifications stop;What's wrong? I've tried example from
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-12.txt but they are
not working.Thanks for helpPhilippe
_
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
Re: [Dovecot] Sieve Notify Error
Leroy Philippe wrote: notify :method mailto:[EMAIL PROTECTED] :message Vous avez recu un message sur votre adresse; This seems to work: notify :method mailto :options [EMAIL PROTECTED] :message Vous avez recu un message sur votre adresse; Cheers, Anders.
Re: [Dovecot] Error - Dovecot Permission denied
kbajwa wrote: Mouss: Here is the information you asked for: [EMAIL PROTECTED] ~]# ls -1 / | grep /etc no, it's a '-l' (letter l = L), not '-1' (number 1). I hate these fonts! [EMAIL PROTECTED] ~]# ls -l /etc/dovecot.conf -rw-r- 1 dovecot mail 46723 Jul 26 20:09 /etc/dovecot.conf so the delivery agent can't read the file since it is executed as the user who gets mail. thus permission denied.
Re: [Dovecot] Sieve Notify Error
Leroy Philippe wrote:
Hello,
I'm using dovecot 1.1.1 and dovecot-sieve-1.1.5 .
I'm very interested in the notify plugin, I've tried many code which have
generated some errors (coding errors that have been arrived in the
.dovecot.sieve.err) but these errors are fixed.
But Notify is still not working, I've the following in mail.log :deliver([EMAIL PROTECTED]): SIEVE ERROR: Unknown [unimplemented] notify method mailto:[EMAIL PROTECTED] is my .dovecot.sieve :require [fileinto, notify];# Move spam to spam folderif exists X-Spam-Flag { fileinto spam; # Stop here so that we do not reply on spams stop;}notify :method mailto:[EMAIL PROTECTED]:message Vous avez recu un message sur votre adresse; # Don't send any further notifications stop;What's wrong? I've tried example from http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-12.txt but they are not working.Thanks for helpPhilippe
_
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
Dovecot sieve implementation is based on RFC draft-ietf-sieve-notify-2.txt
notify
:method mailto
:options [EMAIL PROTECTED]
[...]
Mail address (one or more) must be specified as options to method.
Current dovecot's sieve code don't accept URI form mailto:[EMAIL PROTECTED] specified in latest versions of RFC. Use :options instead
Dovecot's sieve code originaly is taken from cyrus imapd. And cyrus
works this way. Notify method was unimplemented in first release of
dovecot's sieve plugin by Timo. I wrote patch which implements this
method. Most code actualy was taken form cyrus notifyd sources (as all
sieve parsing code Timo adopted form cyrus unchanged.). Later Timo
included this patch in 1.0 stable branch. Things changed... but notify
methods code remains unchanged... my be it's time to implement latest
RFC specifications.
Uldis
Re: [Dovecot] Sieve Notify Error
Uldis Pakuls schreef: Dovecot's sieve code originaly is taken from cyrus imapd. And cyrus works this way. Notify method was unimplemented in first release of dovecot's sieve plugin by Timo. I wrote patch which implements this method. Most code actualy was taken form cyrus notifyd sources (as all sieve parsing code Timo adopted form cyrus unchanged.). Later Timo included this patch in 1.0 stable branch. Things changed... but notify methods code remains unchanged... my be it's time to implement latest RFC specifications. That is the intent of the new Sieve implementation. However, the first release will omit support for the notify extension entirely. I should be able to add notify support quickly in subsequent releases though. Regards, Stephan.
Re: [Dovecot] Strange checkpassword issue
Figured it out. For whatever reason, I didn't need to set the userdb_mail
previously, but you definitely do now.
Thanks,
Andy
On Fri, 25 Jul 2008, Andy Dills wrote:
I'm helping a friend setup a small mailserver using dovecot, and I'm
finding a strange problem with checkpasswd that I haven't had on my
servers.
How is the following debug output even possible?
Jul 25 12:12:20 company2 dovecot: auth(default): master out: USER 5
joe home=/var/mail/joe.com/joe/Maildir/ uid=1005gid=1005
Jul 25 12:12:20 company2 dovecot: pop3-login: Login: user=joe,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Jul 25 12:12:20 company2 dovecot: POP3(joe): open(/var/mail/joe) failed:
Permission denied (euid=1005 egid=1005)
I don't see how, when it's clearly getting the correct home directory from
checkpassword, that it would then try the default mail directory.
(mail_location is commented out, version 1.1.1)
Here's the entire auth clause:
auth default {
mechanisms = plain login
passdb checkpassword {
args = /usr/local/sbin/checkpassword
}
userdb prefetch {
}
user = mailman # 1005,1005
socket listen {
master {
mode = 0666
}
client {
path = /var/run/dovecot/auth
mode = 0660
user = postfix
group = postfix
}
}
}
Any suggestions? I'm probably just missing something obvious, not having
messed with setting this up for 6 months.
Thanks,
Andy
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
Re: [Dovecot] Error - Dovecot Permission denied
On 7/26/2008, kbajwa ([EMAIL PROTECTED]) wrote: (1) (lost connection with mail.tibonline.net[12.179.81.11] while receiving the initial server greeting) (2) status=bounced (local configuration error. Command output: Fatal: open(/etc/dovecot.conf) failed: Permission denied ) Please don't edit log entries like that... a lot of times the entries immeditately before or after what *you* think are relevant actually are *more* relevant... -- Best regards, Charles
Re: [Dovecot] Strange checkpassword issue
On 7/25/2008, Andy Dills ([EMAIL PROTECTED]) wrote: Here's the entire auth clause: full output of dovecot -n is always preferred... -- Best regards, Charles
[Dovecot] limiting the per-time connections from one single IP address
Hi every we had a havy pop3 attach yesterday morning: about 400'000 connects in three hours from one single IP address within wandadoo.fr. the easiest way, to protect the dovecot server against such attacks would be to limit the number of connections anyone can open from one single IP address to the server in a certain time. this feature is available in newer versions of postfix, where i have limited the number of SMTP connections possible from one single IP address in one minute to three (3). i checked to see in the dovecot-wiki, but found only the #login_max_processes_count = 128 #login_max_connections = 256 which both do not contain neither a per-time constraint nor a per-IP-address constraint. is this already possible with current versions of deovecot? the dovecot -n: # 1.0.14: /etc/dovecot.conf ssl_cert_file: /etc/pki/ldap/mirador.cert.pem ssl_key_file: /etc/pki/ldap/mirador.key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 51 mail_location: maildir:%h/%m mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: ldap args: /etc/openldap/dovecot.conf userdb: driver: ldap args: /etc/openldap/dovecot.conf thank you very much for any valid hint. suomi
Re: [Dovecot] limiting the per-time connections from one single IP address
On Mon, 2008-07-28 at 17:23 +0200, suomi wrote: Hi every we had a havy pop3 attach yesterday morning: about 400'000 connects in three hours from one single IP address within wandadoo.fr. the easiest way, to protect the dovecot server against such attacks would be to limit the number of connections anyone can open from one single IP address to the server in a certain time. It's available in 1.1: # Maximum number of POP3 connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 3 Rick
[Dovecot] lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init
After upgrading our CentOS 5 box to the latest revisions last week (including Dovecot 1.1), we're seeing the following error message in the log files. Sieve was working fine with Dovecot 1.0. I have yet to turn up anything via Google for this particular error. SELinux is not logging any error messages at the moment, so I'm pretty sure that we've properly allowed all the SELinux permissions. # cat /var/vmail/dovecot-deliver.log deliver([EMAIL PROTECTED]): Jul 28 11:11:44 Error: dlopen(/usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init deliver([EMAIL PROTECTED]): Jul 28 11:11:44 Fatal: Couldn't load required plugins # ls -l /usr/libexec/dovecot/sievec -rwxr-xr-x 1 root root 165152 Jun 11 03:21 /usr/libexec/dovecot/sievec # ls -l /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so -rwxr-xr-x 1 root root 141328 Jun 11 03:21 /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so # yum list | grep dovecot dovecot.x86_64 1:1.1.1-2_76.el5 installed dovecot-sieve.x86_64 1.1.5-8.el5 installed dovecot.x86_64 1:1.1.2-2_77.el5 atrpms dovecot-devel.x86_64 1:1.1.2-2_77.el5 atrpms
[Dovecot] Server-side sieve for client-side copies
I know I could test this - but I'd rather ask first. To my knowledge, we haven't come up with a good server-side implementation for savings copies of sent messages (by all means correct my ignorance in this regard). So the typical way is to enable it in clients like Thunderbird (this prompted a whole discussion of how to save these messages without sending them to the server multiple times). My understanding is that sending a message from a client (use Thunderbird for simplicity of this conversation) is performed via SMTP. Saving a copy into a sent folder is performed via IMAP (hence the multiple transfers to the server). Now that I've laid a background - let's make it Dovecot specific. I don't know how behind-the-scenes Dovecot performs the act of saving mail messages that it receives from IMAP, instead of SMTP. Specifically, if I'm using sieve filters via deliver - can I setup a filter that will place mail copies to specific recipients into specific subfolders? -- Daniel
Re: [Dovecot] Server-side sieve for client-side copies
Daniel L. Miller escreveu: My understanding is that sending a message from a client (use Thunderbird for simplicity of this conversation) is performed via SMTP. Saving a copy into a sent folder is performed via IMAP (hence the multiple transfers to the server). Now that I've laid a background - let's make it Dovecot specific. I don't know how behind-the-scenes Dovecot performs the act of saving mail messages that it receives from IMAP, instead of SMTP. Specifically, if I'm using sieve filters via deliver - can I setup a filter that will place mail copies to specific recipients into specific subfolders? Thunderbird and other mail clients store a copy of the sent message by using the IMAP APPEND command, which is a generic command to store a mail message (or anything else, if you are brave enough) in a mailbox. Sieve filters are run for messages that are received via SMTP (usually from another host), and need to be saved in the user's mailbox. (Provided the mail server is configured to use dovecot's deliver to do that.) So, in short, these are two very different processes, and no filtering is done for messages saved in a folder (such as Sent).
Re: [Dovecot] Server-side sieve for client-side copies
on 7-28-2008 9:38 AM Daniel L. Miller spake the following: I know I could test this - but I'd rather ask first. To my knowledge, we haven't come up with a good server-side implementation for savings copies of sent messages (by all means correct my ignorance in this regard). So the typical way is to enable it in clients like Thunderbird (this prompted a whole discussion of how to save these messages without sending them to the server multiple times). My understanding is that sending a message from a client (use Thunderbird for simplicity of this conversation) is performed via SMTP. Saving a copy into a sent folder is performed via IMAP (hence the multiple transfers to the server). Now that I've laid a background - let's make it Dovecot specific. I don't know how behind-the-scenes Dovecot performs the act of saving mail messages that it receives from IMAP, instead of SMTP. Specifically, if I'm using sieve filters via deliver - can I setup a filter that will place mail copies to specific recipients into specific subfolders? Not easy, but set client to BCC yourself, and set filters for messages from you/to you. Until they modify the IMAP spec, and then every mail client is updated, it just isn't going to be an easy fix. -- 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] lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init
Thomas Harold wrote: After upgrading our CentOS 5 box to the latest revisions last week (including Dovecot 1.1), we're seeing the following error message in the log files. Sieve was working fine with Dovecot 1.0. I have yet to turn up anything via Google for this particular error. SELinux is not logging any error messages at the moment, so I'm pretty sure that we've properly allowed all the SELinux permissions. # cat /var/vmail/dovecot-deliver.log deliver([EMAIL PROTECTED]): Jul 28 11:11:44 Error: dlopen(/usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init deliver([EMAIL PROTECTED]): Jul 28 11:11:44 Fatal: Couldn't load required plugins # ls -l /usr/libexec/dovecot/sievec -rwxr-xr-x 1 root root 165152 Jun 11 03:21 /usr/libexec/dovecot/sievec # ls -l /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so -rwxr-xr-x 1 root root 141328 Jun 11 03:21 /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so # yum list | grep dovecot dovecot.x86_64 1:1.1.1-2_76.el5 installed dovecot-sieve.x86_64 1.1.5-8.el5 installed dovecot.x86_64 1:1.1.2-2_77.el5 atrpms dovecot-devel.x86_64 1:1.1.2-2_77.el5 atrpms Looks like you mixed up binaries from different versions of dovecot. I recommend completely remove dovecot, (manually rechecking after rpm remove). and reinstall. Uldis
Re: [Dovecot] limiting the per-time connections from one single IP address
suomi wrote: Hi every we had a havy pop3 attach yesterday morning: about 400'000 connects in three hours from one single IP address within wandadoo.fr. the easiest way, to protect the dovecot server against such attacks would be to limit the number of connections anyone can open from one single IP address to the server in a certain time. this feature is available in newer versions of postfix, where i have limited the number of SMTP connections possible from one single IP address in one minute to three (3). thank you very much for any valid hint. suomi There is no such feature in dovecot, but you can use iptables firewall to do this. An article with examples: http://www.debian-administration.org/articles/187 Uldis
Re: [Dovecot] Server-side sieve for client-side copies
Hi, On Mon, 28 Jul 2008 09:38:19 -0700, Daniel L. Miller [EMAIL PROTECTED] wrote: My understanding is that sending a message from a client (use Thunderbird for simplicity of this conversation) is performed via SMTP. Saving a copy into a sent folder is performed via IMAP (hence the multiple transfers to the server). Now that I've laid a background - let's make it Dovecot specific. I don't know how behind-the-scenes Dovecot performs the act of saving mail messages that it receives from IMAP, instead of SMTP. Specifically, if I'm using sieve filters via deliver - can I setup a filter that will place mail copies to specific recipients into specific subfolders? It seems to me, that you are assuming that Dovecot also speaks SMTP and is able to actually handle sending of mails to other hosts. To clarify: Dovecot is an IMAP/POP3 mail server (with integrated Mail Delivery Agent (MDA) or Local Delivery Agent (LDA) (synonyms)). SMTP is being handled by a Mail Transfer Agent (MTA) such as Postfix. So as you can see, the Mail User Agent (MUA) (for example Thunderbird) interacts with two different server programs, one for sending mail (via SMTP), one for accessing stored mail (via IMAP/POP3). The only way I can see to make the double uploading go away, would be, to change the MTA's configuration so that it automatically sends a blind carbon copy of the outgoing message to the sender. Then set up a sieve rule in Dovecot to file this mail into the Sent folder. Of course don't forget to switch off the 'copy sent mails to Sent folder' feature in every mail client which is using this setup. Patrick. -- STAR Software (Shanghai) Co., Ltd.http://www.star-group.net/ Phone:+86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005
Re: [Dovecot] Fix? available for mmap on FreeBSD zfs (corrupted index files)
Just as a heads up since some dovecot users do use ZFS, pjd recently posted a patch to upgrade ZFS in 8-current from v6 to v11 (latest from opensolaris). Its reported to fix a number of problems, and add new features. The patch does not apply to 7, that won't be available for a while apparently, but they are looking for feedback on the fs or current mailing lists to encourage sooner integration (possibly by 7.1). Quick instructions: fetch http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 bunzip2 zfs_20080727.patch.bz2 cd /usr/src/ patch -p0 /path/to/zfs_20080727.patch do a FULL upgrade of world/kernel. kmem tweaks may still be needed but its a little more resilient than before, also 8-current now lets you configure a larger kmem than the previous ~1.8G limit. It is recommended to remove other tweaks from loader.conf such as zil_disable, etc and see how it does. I've upgraded my laptop and so far so good, but I don't have dovecot on any systems with ZFS so I can't test that aspect. On Fri, Apr 04, 2008 at 02:06:40PM -0400, Dillon Kass wrote: Hi, I've applied this patch to my 7-STABLE box and it doesn't help with the corrupted dovecot index files. Anyone using dovecot with ZFS on FreeBSD should use mmap_disable = yes in their dovecot.conf Cheers, Dillon Adam McDougall wrote: Saw this just come through for 8-current, 7-stable ought to have it in a week or so. I have not encountered the problem so I would not be able to judge if this fixes it. Patch here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c.diff?r1=1.27;r2=1.28 pjd 2008-03-15 23:23:04 UTC FreeBSD src repository Modified files: sys/contrib/opensolaris/uts/common/fs/zfs zfs_vnops.c Log: Fix mmap(2) on ZFS after some changes in VM subsystem. Submitted by: alc Reported by:kris (originally) and many others Tested with:fsx MFC after: 1 week Revision ChangesPath 1.28 +4 -0 src/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c
Re: [Dovecot] Fix? available for mmap on FreeBSD zfs (corrupted index files)
Ugh, I forgot a step you might need. Due to the patching, /usr/src/sys/cddl/compat/opensolaris/sys/acl.h and /usr/src/sys/cddl/compat/opensolaris/sys/callb.h become empty and if they exist, should be deleted before compiling because they will cause the compile to fail. On Mon, Jul 28, 2008 at 10:29:05PM -0400, Adam McDougall wrote: Just as a heads up since some dovecot users do use ZFS, pjd recently posted a patch to upgrade ZFS in 8-current from v6 to v11 (latest from opensolaris). Its reported to fix a number of problems, and add new features. The patch does not apply to 7, that won't be available for a while apparently, but they are looking for feedback on the fs or current mailing lists to encourage sooner integration (possibly by 7.1). Quick instructions: fetch http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 bunzip2 zfs_20080727.patch.bz2 cd /usr/src/ patch -p0 /path/to/zfs_20080727.patch do a FULL upgrade of world/kernel. kmem tweaks may still be needed but its a little more resilient than before, also 8-current now lets you configure a larger kmem than the previous ~1.8G limit. It is recommended to remove other tweaks from loader.conf such as zil_disable, etc and see how it does. I've upgraded my laptop and so far so good, but I don't have dovecot on any systems with ZFS so I can't test that aspect. On Fri, Apr 04, 2008 at 02:06:40PM -0400, Dillon Kass wrote: Hi, I've applied this patch to my 7-STABLE box and it doesn't help with the corrupted dovecot index files. Anyone using dovecot with ZFS on FreeBSD should use mmap_disable = yes in their dovecot.conf Cheers, Dillon Adam McDougall wrote: Saw this just come through for 8-current, 7-stable ought to have it in a week or so. I have not encountered the problem so I would not be able to judge if this fixes it. Patch here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c.diff?r1=1.27;r2=1.28 pjd 2008-03-15 23:23:04 UTC FreeBSD src repository Modified files: sys/contrib/opensolaris/uts/common/fs/zfs zfs_vnops.c Log: Fix mmap(2) on ZFS after some changes in VM subsystem. Submitted by: alc Reported by:kris (originally) and many others Tested with:fsx MFC after: 1 week Revision ChangesPath 1.28 +4 -0 src/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c
[Dovecot] Dovecot-auth connection problem
Hello I have this messages in log: Jul 29 00:02:56 10.0.4.16 dovecot: imap-login: Can\'t connect to auth server at default: Resource temporarily unavailable Jul 29 00:02:56 10.0.4.16 last message repeated 6 times Jul 29 00:02:56 10.0.4.16 dovecot: pop3-login: Can\'t connect to auth server at default: Resource temporarily unavailable Jul 29 00:02:56 10.0.4.16 last message repeated 6 times Jul 29 00:02:56 10.0.4.16 dovecot: imap-login: Can\'t connect to auth server at default: Resource temporarily unavailable Jul 29 00:02:56 10.0.4.16 last message repeated 15 times Jul 29 00:02:56 10.0.4.16 dovecot: pop3-login: Can\'t connect to auth server at default: Resource temporarily unavailable In this way users can't connect top pop3, imap services. Dovecot restart only help me to restore my services. I have 80k users and ~250k sessions per day. i thank you very much for any valid hint. Debian Linux 2.6.18-4-686 dovecot -n output: # 1.1.2: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: local0 protocols: imap pop3 disable_plaintext_auth: no shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_process_size: 512 login_processes_count: 33 login_max_processes_count: 1000 login_max_connections: 1000 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 99 mail_location: maildir:%h mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap-gaa mail_executable(imap): /usr/lib/dovecot/imap-gaa mail_executable(pop3): /usr/lib/dovecot/pop3-gaa mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_log_max_lines_per_sec: 0 auth default: cache_size: 16384 cache_ttl: 600 verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf passdb: driver: sql args: /etc/dovecot/dovecot-sql1.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 511 user: mail -- Best regards, Alexey Gorbov [EMAIL PROTECTED]
