- dovecot - dovecot.org

[Dovecot] POP3 Setup help
by Thomas I Higgins 09 Oct '13

09 Oct '13

I am lost as to what I am missing. I am setting up dovecot 2.0.9 on a RHEL 6.4 machine as provided by my provider. I have IMAP up and running, and I have POP3 up and running. Testing confirms this. Also, if it makes a difference, I enabled dovecot as my LDA. Sendmail was setup as well due to our 1.x version using it and I though I had to. Anyway, everything is working perfectly with the services, except the mail is sending to the wrong location for POP. I am trying to use Maildir for both services, but it keeps delivering the POP3 mail to /var/spool/mail/u% instead of to Maildir as specified in the configuration files. I have rechecked every setting at least twice and still can't see what I am doing wrong. I suppose I can use mbox and redirect after making the appropriate namespace changes, but that has it's own potential drawbacks and seems more like a kludge than the correct way around this (unless I misunderstand how it should work). Can anyone point me in the right direction on how to fix this? Thanks in advance, Thomas Higgins

3 2

[Dovecot] cas proxy ticket as password
by b m 08 Oct '13

08 Oct '13

Hi everybody. Hi I'm tryingto use CAS for authenticating in dovecot. I have installed pam_cas and when I try castest i get "<cas:authenticationSuccess>" for my service (imaps://mywebmail.com) But when I actually try to login, dovecot uses the PT from the cas server as password. Any ideas what I'm missing? Thanks a lot.

1 0

Re: [Dovecot] Proxy to gmail not working
by Joseph Tam 08 Oct '13

08 Oct '13

On Mon, 7 Oct 2013, Alex Wanderley writes: > passdb { > args = proxy=y nopassword=y user=remotemail destuser=remotemail(a)gmail.comhost= > pop.gmail.com port=995 proxy_timeout=15 starttls=y > driver = static > } > ... > Oct 7 09:33:13 dserver dovecot: auth: Debug: client passdb out: OK > 2 user=remotemail proxy nopassword=y destuser= > remotemail(a)gmail.com host=pop.gmail.com port=995 proxy > _timeout=15 starttls=y hostip=74.125.142.108 pass=123456789 > Oct 7 09:33:13 dserver dovecot: pop3-login: Debug: Ignoring unknown passdb > extra field: nopassword > Oct 7 09:33:28 dserver dovecot: pop3-login: Error: proxy(remotemail): > Login for pop.gmail.com:995 timed out in state=0 (after 15 secs, > local=162.106.yyy.zzz:59282) Idle speculation, but remote port 995 usually means SSL type connection (i.e. dive right into SSL protocol), whereas "starttls=y" starts out in plaintext, and SSL negotiations starts after a STARTTLS directive. Looking at http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy methinks you want to replace "starttls=y" with "ssl=yes". Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Proxy to gmail not working
by Alex Wanderley 07 Oct '13

07 Oct '13

Hi, I've been trying to build a password forwarding proxy to Gmail without success... The SSL connection to Dovecot is happening no problem (as far as I can tell), but for some reason the conversation between Dovecot and Gmail is getting timed out. I know this is supposed to be simple... :-( But could somebody please give me some help by pointing what I'm not doing right? No matter how much I've been researching about this, I can't find the solution. Thanks a lot, Alex # 2.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final) auth_cache_negative_ttl = 10 mins auth_cache_size = 1 k auth_cache_ttl = 10 mins auth_debug = yes auth_debug_passwords = yes auth_mechanisms = cram-md5 digest-md5 apop login plain auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@% auth_username_translation = %@AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz auth_verbose = yes base_dir = /var/run/dovecot/ listen = 162.106.yyy.zzz login_greeting = Dovecot Ready login_log_format_elements = %u %r %m %c mail_debug = yes mail_max_userip_connections = 100 passdb { args = proxy=y nopassword=y user=remotemail destuser=remotemail(a)gmail.comhost= pop.gmail.com port=995 proxy_timeout=15 starttls=y driver = static } protocols = pop3 service pop3-login { client_limit = 200 inet_listener pop3 { address = dserver port = 110 } process_limit = 1 process_min_avail = 1 service_count = 0 vsz_limit = 256 M } ssl = required ssl_ca = </etc/pki/tls/certs/ca-bundle.crt ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = EECDH+AES:EDH+AES:-SHA1:EECDH+RC4:EDH+RC4:RC4-SHA:EECDH+AES256:EDH+AES256:AES256-SHA:HIGH:!aNULL:!eNULL:!EXP:!MD5:!LOW:!SSLv2 ssl_client_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_client_key = </etc/pki/dovecot/private/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = static uid=10000 gid=10000 home=/dev/null driver = static } verbose_ssl = yes version_ignore = yes Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Oct 7 09:32:51 dserver dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Oct 7 09:32:51 dserver dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Oct 7 09:32:51 dserver dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Oct 7 09:32:51 dserver dovecot: auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat Oct 7 09:32:51 dserver dovecot: auth: Debug: auth client connected (pid=25878) Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [162.106.xxx.yyy] Oct 7 09:32:51 dserver dovecot: pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [162.106.xxx.yyy] Oct 7 09:33:13 dserver dovecot: auth: Debug: client in: AUTH 2 PLAIN service=pop3 secured session=oePRXijoMQCiat/X lip=162.106.yyy.zzz rip=162.106.xxx.yyy lport=995 rport=502 25 resp=AHNtYXJ0YnVzZWRtAHMwbWV0aGluZw== (previous base64 data may contain sensitive data) Oct 7 09:33:13 dserver dovecot: auth: Debug: static(remotemail,162.106.xxx.yyy,<oePRXijoMQCiat/X>): lookup Oct 7 09:33:13 dserver dovecot: auth: Debug: static(remotemail,162.106.xxx.yyy,<oePRXijoMQCiat/X>): Allowing any password Oct 7 09:33:13 dserver dovecot: auth: Debug: client passdb out: OK 2 user=remotemail proxy nopassword=y destuser= remotemail(a)gmail.com host=pop.gmail.com port=995 proxy _timeout=15 starttls=y hostip=74.125.142.108 pass=123456789 Oct 7 09:33:13 dserver dovecot: pop3-login: Debug: Ignoring unknown passdb extra field: nopassword Oct 7 09:33:28 dserver dovecot: pop3-login: Error: proxy(remotemail): Login for pop.gmail.com:995 timed out in state=0 (after 15 secs, local=162.106.yyy.zzz:59282) Oct 7 09:33:34 dserver dovecot: pop3-login: Aborted login (internal failure, 1 successful auths): remotemail, 162.106.xxx.yyy, PLAIN, TLS Oct 7 09:33:34 dserver dovecot: pop3-login: Debug: SSL alert: close notify [162.106.xxx.yyy]

3 2

[Dovecot] Replication: long detalys
by Lucas Rothamel - Eye Catching Webdesign 07 Oct '13

07 Oct '13

Hello everybody, I am running dovecot 2.1.7 on Debian Wheezy on two servers with replication set up, MTA is postfix. The idea is to have a redundant mail system so that when one server fails, users can continue using the other server (failover of POP/IMAP through DNS redirection). Servers are called srv06 and srv07: Below is the dovecot config, both servers have identical config, only the replica srv0x address is different. I read to put this line into 10-mail.conf and I did: mail_plugins = $mail_plugins notify replication My Problem: When E-Mail arrives on one server, it is only available on the other server many hours later. Same behaviour in both directions. This means I see different mailboxes via IMAP depending on which server I connect to - in theory I want the client not to be able to tell which server it is connected to. dovecot -n: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/%d/%n/Maildir mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:vmail@srv07.xxx quota = maildir:User quota quota_rule = *:storage=1GB replication_full_sync_interval = 1 hours } protocols = imap pop3 service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = vmail } unix_listener replication-notify { mode = 0600 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service config { unix_listener config { user = vmail } } service doveadm { user = vmail } service replicator { process_min_avail = 1 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = quota postmaster_address = mk@xxx } output of cat /var/log/mail.log | grep dsync: Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1522, file=1381075321.V902I19a2a66M626453.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1523, file=1381075381.V902I19a2bb2M737865.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1524, file=1381075441.V902I19a3185M959529.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1525, file=1381075501.V902I19a3187M989935.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1526, file=1381075561.V902I19a3188M971187.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1527, file=1381075622.V902I19a3189M60093.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1528, file=1381075682.V902I19a318aM231725.srv07.xxxxx:2,) Oct 7 05:31:45 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1529, file=1381075741.V902I19a318bM353115.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1530, file=1381075801.V902I19a318cM609633.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1531, file=1381075861.V902I19a318dM392514.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1532, file=1381075921.V902I19a318eM521040.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1533, file=1381075981.V902I19a318fM611775.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1534, file=1381076041.V902I19a3190M734263.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1535, file=1381076101.V902I19a3191M850303.srv07.xxxxx:2,) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1536, file=1381076881.V902I19a3192M362845.srv07.xxxxx:2,S) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1537, file=1380998413.V902I19a315bM206668.srv07.xxxxx:2,e) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1538, file=1380999043.V902I19a315cM413578.srv07.xxxxx:2,e) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1539, file=1380574384.V902I19a3146M616434.srv07.xxxxx:2,e) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Error: remote: dsync-remote(sysop@xxxxx): Warning: Maildir /home/xxxxx/sysop/Maildir: Expunged message reappeared, giving a new UID (old uid=1540, file=1381110251.V902I19a3186M993173.srv07.xxxxx) Oct 7 05:31:46 srv06 dovecot: dsync-local(sysop@xxxxx): Warning: Mailbox changes caused a desync. You may want to run dsync again. However, I cannot understand what this log wants to tell me? Please advise. Thanks. Lucas -- Lucas Rothamel Eye Catching Webdesign info(a)eye-catching-webdesign.de - www.eye-catching-webdesign.de You know, we go to the gym to keep the body fit. Similarly the mind needs some rest. The mind is bombarded with so many impressions. Our mind has been bombarded by impressions the whole time. It needs a different kind of rest other than sleep. And meditation is such a rest. It calms the mind. energizes the spirit and makes the body more strong and vibrant. improves the immune system. The immune cells, the T-cell count go higher through Sudarshan Kriya and meditation. And you feel so nice inside. - Sri Sri Ravi Shankar I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams

2 1

[Dovecot] retr errors
by Bill Morgan 07 Oct '13

07 Oct '13

My ISP uses Dovecot and I have had an ongoing problem for a while using several email clients. Sometimes the response to a retr request is mal-formed. The expected response "+OK nnn octets" is not returned. The response looks like it started somewhere in the message headers. Sometimes a retry can clear the problem but I usually need to delete the first message via a putty session. The problem, when present, is always on the first message. Never seen it in the middle of a series of messages. This problem has been seen on different machines, different versions of Windows, at home and on the road. I have wireshark traces showing good and bad sessions.... ====================== stat +OK 93 1000437 retr 1 +OK 6946 octets Return-path: ..... ========================= retr 1 of blahblah(a)blah.com designates 2607:f8b0:4001:c03::235 as permitted sender) smtp.mail=blahblah(a)blah.com; dkim=pass header.i=(a)blah.com Reply-To: android-developers(a)googlegroups.com Precedence: list Mailing-list: ...... ================== My ISP has been non-helpful. Any ideas how I can track down the problem? Thanks Bill

5 6

[Dovecot] Yet another going from 1.2 to 2.X question: authentication
by Mauricio Tavares 07 Oct '13

07 Oct '13

So in 1.2.9 I had something like this: [...] socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = virtual # User running Dovecot LDA's deliver } } # Dovecot as SASL Auth socket listen { client { path = /var/spool/postfix/private/dovecot-auth mode = 0660 user = postfix group = postfix } } I see I can, per http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL, setup the sasl entry as # Dovecot as SASL Auth service auth { unix_listener /var/spool/postfix/private/dovecot-auth mode = 0660 user = postfix group = postfix } what about the lda? From http://wiki2.dovecot.org/LDA I take it would be as simple as service auth { unix_listener auth-userdb { mode = 0600 user = virtual # User running Dovecot LDA's deliver } } Am I correct?

2 3

[Dovecot] couple of errors on new setup
by Dean Guenther 07 Oct '13

07 Oct '13

I have stood up a new test mail server as an upgraded version of my existing mail server. I have been fairly consistently getting two types of error messages. I'm thinking they may be related permissions issues, but I can't figure out what their problem is. Oct 4 12:45:47 digory dovecot: imap(guenther): Error: file_dotlock_open() failed with file /home/guenther/mail/ForUs/.imap/Home/dovecot.index.log: Resource temporarily unavailable Oct 4 12:46:16 digory dovecot: imap(guenther): Error: file_dotlock_open(/home/guenther/mail/ForUs/PCS/.imap/PCS misc/dovecot.index.log) failed: Permission denied (euid=500(guenther) egid=500(guenther), access(/home/guenther/mail/ForUs/PCS/.imap/PCS misc/dovecot.index.log, 4) failed: No such file or directory) Here are my specifics: OS: CentOS 6.4 - 2.6.32-358.11.1.el6.x86_64 MailScanner: 4.84.6 Postfix: 2.6.6 DoveCot: 2.2.4 NFS v4 (both the mail spool and /home are NVS v4 mounts to file server) Here are the non-default settings: dovecot -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.11.1.el6.x86_64 x86_64 CentOS release 6.4 (Fina auth_verbose = yes disable_plaintext_auth = no mail_access_groups = users,guenther mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/postfix/ssl/xxxxxxxxxx.crt ssl_key = </etc/postfix/ssl/xxxxxxxxxx.key userdb { driver = passwd } verbose_ssl = yes Thanks -- Dean Guenther

3 3

[Dovecot] Problems getting Squirrelmail and Avelsieve to connect to Pigeonhole
by Steve 06 Oct '13

06 Oct '13

Hi, I have been going around in circles trying to find the solution. Many others appear to have the same problem, but never a solution or explanation. I am running Dovecot 2.0.21 under Fedora 16. All components are running on the same server, whose IP address is shown as '192.168.x.y'. The dovecot -n output is: <quote> /SSH Secure Shell 3.2.0 (Build 267)/ /Copyright (c) 2000-2002 SSH Communications Security Corp - http://www.ssh.com// /This copy of SSH Secure Shell is a non-commercial version./ /This version does not include PKI and PKCS #11 functionality./ /Last login: Sun Oct 6 17:00:08 2013 from 192.168.2.196/ /[root@nsi-server2 ~]# /usr/sbin/dovecot -n/ /# 2.0.21: /etc/dovecot/dovecot.conf/ /# OS: Linux 3.6.11-4.fc16.x86_64 x86_64 Fedora release 16 (Verne) / /auth_debug_passwords = yes/ /auth_verbose = yes/ /auth_verbose_passwords = plain/ /log_path = /var/log/mail/dovecot.log/ /mail_access_groups = mail/ /mail_location = mbox:~/mail:INBOX=/var/mail/%u/ /managesieve_notify_capability = mailto/ /managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave/ /mbox_write_locks = fcntl/ /passdb {/ / driver = pam/ /}/ /passdb {/ / args = /etc/dovecot/users/ / driver = passwd-file/ /}/ /plugin {/ / sieve = ~/.dovecot.sieve/ / sieve_dir = ~/sieve/ / sieve_global_path = /var/lib/dovecot/sieve/default.sieve/ /}/ /protocols = imap pop3 sieve sieve/ /service imap-login {/ / inet_listener imap {/ / address = 192.168.x.y,localhost/ / }/ / inet_listener imaps {/ / address = 192.168.x.y/ / }/ /}/ /service managesieve-login {/ / inet_listener sieve {/ / port = 4190/ / }/ /}/ /service pop3-login {/ / inet_listener pop3 {/ / address = 192.168.x,y,localhost/ / }/ / inet_listener pop3s {/ / address = 192.168.x.y/ / }/ /}/ /ssl_cert = </etc/pki/dovecot/certs/dovecot.pem/ /ssl_key = </etc/pki/dovecot/private/dovecot.pem/ /userdb {/ / driver = passwd/ /}/ /userdb {/ / args = /etc/dovecot/users/ / driver = passwd-file/ /}/ </quote> On attempting to connect to the managesieve port from Squirrelmail, using the 'Filter' button i get the following error message: /*Could not log on to timsieved daemon on your IMAP server localhost.*/ /*Please contact your administrator*/ Running/*# /usr/sbin/ngrep -d lo port 4190 */produces the following trace: <quote> /[root@nsi-server root]# /usr/sbin/ngrep -d lo port 4190/ /interface: lo (127.0.0.0/255.0.0.0)/ /filter: (ip or ip6) and ( port 4190 )/ /####/ /T 127.0.0.1:4190 -> 127.0.0.1:35495 [AP]/ / "IMPLEMENTATION" "Dovecot Pigeonhole".."SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator/ / -i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave".."NOTIFY/ / " "mailto".."SASL" "PLAIN".."STARTTLS".."VERSION" "1.0"..OK "Dovecot ready.".. / /##/ /T 127.0.0.1:35495 -> 127.0.0.1:4190 [AP]/ / AUTHENTICATE "PLAIN" \{28+}.. / /##/ /T 127.0.0.1:35495 -> 127.0.0.1:4190 [AP]/ /c3RldmUAc3RldmUAbWFnaWNsaWs=.. / /##/ /T 127.0.0.1:4190 -> 127.0.0.1:35495 [AP]/ / NO "Invalid characters in atom"..NO "Error in MANAGESIEVE command received by server.".. / /###/ </quote> I hope that someone can provide a way to get the filter management working as I am more that happy with the way Dovecot and Squirrelmail are working, but just want to add server-side filtering, especially tagged mail produced by Spamassassin :) Many thanks Steve

2 1

[Dovecot] State of the FTS modules and packaging
by Benjamin Podszun 06 Oct '13

06 Oct '13

Hi there. I'm running a small (VPS) mail system just for myself for quite a while and want to support some friends and family now. For that I'm improving / documenting the setup. One thing I never cared to implement was FTS support. Looking at the options [1] now, I'm stuck. I don't want solr (no Java bashing here, I'm sure that's working awesome. But I don't want to pull all these dependencies in on my tiny VPS: Memory and disk will be as small as I can get away with). With that out of the way: What are my options? Squat: Why's squat deprecated? Did it stop working? Can someone shed some light on the original reasons for the deprecation? What are the risks to go with squat anyway? Clucene: That seems .. unusable. It would be my prefered choice (not deprecated, little dependencies), but .. it isn't packaged in deb based distributions (Debian, Ubuntu). It doesn't even _build_, because it doesn't use pkg-config to find the clucene includes (at least for 2.1.17) in these environments. Centos is even more out of date with 2.0.9. Given the experience above, is solr my only option to offer FTS? Can you guys share how you're having a stable base/os with a somewhat recent (and complete!) dovecot package? Thanks a lot & regards, Ben 1: http://wiki2.dovecot.org/Plugins/FTS

1 0