- dovecot - dovecot.org

Re: [Dovecot] dovecot - mac firewall problem
by Patrick Fay 30 Aug '10

30 Aug '10

> On 8/29/2010 8:51 PM, Patrick Fay wrote: >> Aug 26 20:43:45 hostname Firewall[55]: Deny ^L connecting from XX.XX.XX.XX:37310 uid = 0 proto=6 >> Aug 26 20:43:53 hostname Firewall[55]: Deny ^H?^U???^Z connecting from XX.XX.XX.XX:37310 uid = 0 proto=6 >> >> Both of these are dovecot hits--but the name is different each time. >> Also the ?'s aren't really "?" marks; they're trans-ascii characters >> with high bits set that my mailer doesn't like very much. It really >> looks like a misdirected pointer or something somewhere, but I'm not >> familiar enough with the codebase to know where to start looking, or >> if in fact it is something else that is misconfigured. Any thoughts >> on how to resolve this? > > Dovecot version? > > -- > > Best regards, > > Charles > My apologies-- dovecot version 1.2.11. Patrick

2 1

Re: [Dovecot] doveadm expunge -A mailbox Trash savedbefore 30d
by Jerrale G 30 Aug '10

30 Aug '10

Could you explain the iterate_query in any kind of sql. I'm guessing to just use the query, correctly, that's failing as iterate_query= and put it in the service auth file which includes password_query and user_query. then, I'm guessing to add something like: iteratedb { driver = sql args = /path/to/sql.conf } The wiki2 only says: "When the SQL userdb module is used make sure that the iterate_query setting in /etc/dovecot/dovecot-sql.conf.ext matches your database layout." it should give an example query. I don't know if its wanting to list the fields or the contents of a field. Thanks, Jerrale G Jerrale G. SC Senior Admin

1 0

[Dovecot] Can't get dovecot to see email folders
by Blaster 30 Aug '10

30 Aug '10

So I'm very frustrated, I've spent the better part of a day trying to get dovecot 2.0.1 working...Most of the documentation on the Wiki seems to think you are running an older version and therefore very little of it applies. I'm running 2.0.1 on OpenSolaris. I seem to have 2 remaining issues: 1) Dovecot is not able to determine the home directory 2) IMAP clients can not get to the mail folder directory. One client is reporting that it can't open it in read only mode. 3) I tried to get raw logging working, but apparently I couldn't because of #1. The architecture of Dovecot makes it difficult to transition from another IMAP server. If I force the MBOX to be /home/%u/mail, all of my clients think the folders are in /home/%u/mail/mail. If I set mbox location to /home/%u, then dovecot tries to create .subscription and .imap files/directories in the users home dir which it doesn't have permission to do. It would be nice if you could configure Dovecot in such a way as to make transition easier, such as the ability to strip off a duplicate trailing path, ie /home/%u/mail/mail becomes /home/%u/mail....Otherwise this necessitates visiting countless IMAP clients for reconfiguration... Here is my config file: /opt/sbin/dovecot -n # 2.0.1: /opt/etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc base_dir = /var/run/dovecot/ mail_debug = yes mail_gid = mail mail_location = mbox:/home/%u/mail:INBOX=/var/mail/%u mail_privileged_group = mail mail_uid = dovecot passdb { driver = pam } plugin { home = /home/%u } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { address = * port = 993 } } service pop3-login { inet_listener pop3 { address = * port = 0 } inet_listener pop3s { address = * port = 0 } } ssl_cert = </usr/local/ssl/certs/dovecot.pem ssl_key = </usr/local/ssl/private/dovecot.pem gremlin [/opt/bin] # gremlin [/opt/bin] #

4 9

[Dovecot] PAM authentication fails
by Egbert Jan van den Bussche 29 Aug '10

29 Aug '10

Hi, I'm fighting all weekend on with auth and pam to authenticate local system users. testuser is such local user and is in passwd and shadow. I want to have local system users (testuser is one of them) and virtual users. The virtual part works fine but I cannot get the local user to connect. Still pam fails finding the user. The suggested password mismatch at the end is, in my eyes, because there is no user in the first place. I verified the password by interactive login to the account. The pam module (dovecot) is just the default file with three @includes in it. Syslog: Aug 29 20:18:02 mail-dev dovecot: auth(default): client in: AUTH#0112#011LOGIN#011service=imap#011lip=2a02:968:1:2:212:72:224:16#011rip=2001:888:1740:10:250:daff:fe41:4d1c#011lport=143#011rport=1093 Aug 29 20:18:02 mail-dev dovecot: auth(default): client out: CONT#0112#011VXNlcm5hbWU6 Aug 29 20:18:02 mail-dev dovecot: auth(default): client in: CONT#0112#011dGVzdHVzZXI= Aug 29 20:18:02 mail-dev dovecot: auth(default): client out: CONT#0112#011UGFzc3dvcmQ6 Aug 29 20:18:02 mail-dev dovecot: auth(default): client in: CONT#0112#011dmF4dm1z Aug 29 20:18:02 mail-dev dovecot: auth-worker(default): pam(testuser,2001:888:1740:10:250:daff:fe41:4d1c): lookup service=dovecot Aug 29 20:18:02 mail-dev dovecot: auth-worker(default): pam(testuser,2001:888:1740:10:250:daff:fe41:4d1c): #1/1 style=1 msg=Password: Aug 29 20:18:02 mail-dev dovecot: auth(default): cache(testuser,2001:888:1740:10:250:daff:fe41:4d1c): miss Aug 29 20:18:04 mail-dev dovecot: auth(default): cache(testuser,2001:888:1740:10:250:daff:fe41:4d1c): hit: Aug 29 20:18:04 mail-dev dovecot: auth(default): cache(testuser,2001:888:1740:10:250:daff:fe41:4d1c): User unknown Aug 29 20:18:04 mail-dev dovecot: auth-worker(default): pam(testuser,2001:888:1740:10:250:daff:fe41:4d1c): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: xxxxxxxx) Aug 29 20:18:06 mail-dev dovecot: auth(default): client out: FAIL#0112#011user=testuser Relevant settings in dovecot: root@mail-dev:/etc/dovecot# dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-server x86_64 Ubuntu 10.04.1 LTS ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 imaps pop3s managesieve listen: *, [::] ssl_cert_file: /etc/ssl/certs/ssl-mail.pem ssl_key_file: /etc/ssl/private/ssl-mail.key ssl_cipher_list: ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM disable_plaintext_auth: no verbose_ssl: yes 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_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_max_userip_connections(managesieve): 10 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n:INDEX=/home/vmail/%d/%n mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve 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_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmaster deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login realms: kader.hcc.nl hobby.nl cache_size: 1024 user: vmail verbose: yes debug: yes debug_passwords: yes passdb: driver: pam args: setcred=yes failure_show_msg=yes cache_key=%u dovecot passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail Where should I look further for this dovecot pam problem? Is there such a thing as pam debugging? TIA Egbert Jan

1 1

[Dovecot] Sent mail issue
by Piyush Joshi 29 Aug '10

29 Aug '10

Dear All, I have few question regarding dovecot configuration for specific need which are as follows:- 1. I have IMAP folder with the name Sent Mail and i want whenever client uses any MUA to send mail from my server his mail must be kept in server's IMAP folder which is Sent Mail instead of local Sent folder. 2. Whenever user configures account in MUA, MUA automatically create some new folder like Junk Mail etc. while i am already using Spam folder to keep spam message in that folder so let me know how can i save myself from this. 3. Is there any thing which can also put deleted message in my server's Trash folder. Thanks

4 3

[Dovecot] "Multiple Commands in Progress" support
by Mike Cardwell 29 Aug '10

29 Aug '10

Section 5.5 of RFC3501 discusses the ability of IMAP servers to receive and execute multiple commands asynchronously on a single IMAP connection, not necessarily responding in the same order the commands were received: http://tools.ietf.org/html/rfc3501#section-5.5 Does Dovecot take advantage of this ability, or does it simply queue up the commands and execute them synchronously in order? -- Mike Cardwell - Perl/Java/Web developer, Linux admin, Email admin Read my tech Blog - https://secure.grepular.com/ Follow me on Twitter - http://twitter.com/mickeyc Hire me - http://cardwellit.com/ http://uk.linkedin.com/in/mikecardwell

1 0

Re: [Dovecot] dovecot - mac firewall problem
by Patrick Fay 28 Aug '10

28 Aug '10

>> Hi, >> I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works >> perfectly with the application-level firewall off, but enabling the >> application firewall prevents dovecot connections. I have tried >> explicitly authorizing dovecot in the firewall, but it does not work. I >> have searched everywhere I can think of to look, and haven't found a >> solution, but have seen a couple other reports of what seems to be the >> same problem. The firewall logs the activity with what looks like a >> corrupt process name: a typical appfirewall.log entry looks like: >> >> Aug 26 20:43:45 hostname Firewall[55]: Deny ^L connecting from >> XX.XX.XX.XX:37310 uid = 0 proto=6 >> Aug 26 20:43:53 hostname Firewall[55]: Deny ^H?^U???^Z connecting from >> XX.XX.XX.XX:37310 uid = 0 proto=6 >> Aug 26 20:44:09 hostname Firewall[55]: Deny ^L connecting from >> XX.XX.XX.XX:37310 uid = 0 proto=6 >> Aug 26 20:44:34 hostname Firewall[55]: Deny ^L connecting from >> XX.XX.XX.XX:37312 uid = 0 proto=6 >> Aug 26 20:44:45: --- last message repeated 6 times --- >> >> where "hostname" is my server name and the XX's are my client's IP >> address. For all of the other services I've used, the process name >> (e.g. dovecot) should appear after "Deny" when blocking traffic, instead >> of the funny characters. Any advice on how I could resolve this issue >> would be greatly appreciated. Thanks! > > The application level firewall in OSX is aimed at _client_ use, not > server use. It's similar to Novell's AppArmor, etc. Leave it turned off. > > Simply because a piece of software (in this case an OS) offers any given > option does not mean every system needs it. Can you offer a compelling > reason why you _need_ the OSX application level firewall enabled? > Please point us to documentation that advises using it for any of your > services/daemons. > > -- > Stan > Hi was hoping to use the application firewall because this machine gets used both as a server as well as a client machine for more general use. I haven't been able to find any specific documentation for it, but I have found that the firewall works fine with postfix and several file services I use (enabling/disabling works as expected, process names get logged as expected, etc). Thanks! Patrick

2 1

[Dovecot] When should dictionary entries for the expire plugin be added/updated?
by Ralph Seichter 28 Aug '10

28 Aug '10

I've set up Dovecot 2.0 with the expire plugin using an SQLite DB, and when mail is delivered via dovecto-lda, the DB gets updated as expected. However, when I use Thunderbird 3.1.2 for Mac OS X to move a message to any of the folders known to the expire plugin (e.g. the 'tmp' folder), the SQLite DB is not updated. Here is an excerpt of my current configuration: # /etc/dovecot/dovecot.conf dict { expire = sqlite:/etc/dovecot/dict-expire.conf } plugin { expire = Junk expire2 = Trash expire3 = tmp expire4 = *.News expire5 = *.Reports expire_dict = proxy::expire sieve = /etc/dovecot/sieve/%u.sieve } service dict { unix_listener dict { # Ensure that there is no permission-related problem mode = 0666 } } protocol lda { mail_plugins = expire sieve postmaster_address = postmaster(a)domain.tld sendmail_path = /usr/sbin/sendmail } # /etc/dovecot/dict-expire.conf connect = /var/lib/dovecot/expires.sqlite map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire fields { username = $user mailbox = $mailbox } } # Schema dump of /var/lib/dovecot/expires.sqlite PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE expires ( username VARCHAR(75) NOT NULL, mailbox VARCHAR(255) NOT NULL, expire integer NOT NULL, PRIMARY KEY (username, mailbox) ); CREATE TRIGGER mergeexpire BEFORE INSERT ON expires FOR EACH ROW BEGIN UPDATE expires SET expire=NEW.expire WHERE username=NEW.username AND mailbox=NEW.mailbox; SELECT RAISE(IGNORE) WHERE (SELECT 1 FROM expires WHERE username=NEW.username AND mailbox=NEW.mailbox) IS NOT NULL; END; COMMIT; With these settings, rows will be inserted to (or updated within) expires.sqlite when dovecot-lda stores messages to any of my "Reports" folders using sieve rules. When I manually move messages to "tmp" or "Junk", the database remains unchanged. Also, when I delete messages in Thunderbird, I'd expect database additions for the folder "Trash", but this does not happen either. What am I doing wrong here? -Ralph

5 27

[Dovecot] Error: service(auth): child 2212 killed with signal 11
by Toorop 28 Aug '10

28 Aug '10

Hi, Auth always crash (segfault) using vpopmail backend. Any idea ? vpopmail 5.5.0 os: ubuntu 10.04 on rackspace cloud # dovecot -n dovecot -n # 2.0.1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.35.1-rscloud x86_64 Ubuntu 10.04.1 LTS auth_debug = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no first_valid_uid = 89 log_path = /var/log/dovecot/dovecot.log mail_debug = yes passdb { driver = vpopmail } protocols = imap pop3 service auth { unix_listener auth-userdb { group = vchkpw mode = 0600 user = vpopmail } user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = vpopmail } Log: Aug 28 10:59:48 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Aug 28 10:59:48 auth: Debug: auth client connected (pid=2211) Aug 28 10:59:49 auth: Debug: client in: AUTH 1 CRAM-MD5 service=imap secured lip=184.106.217.69 rip=178.32.33.247 lport=143 rport=49099 Aug 28 10:59:49 auth: Debug: client out: CONT 1 PDM3MjI0MzQ4NjQzNTI3NjUuMTI4Mjk5MzE4OUByYWNrc3BhY2UuZGVkaW1haWwuZXU+ Aug 28 10:59:49 auth: Debug: client in: CONT<hidden> Aug 28 10:59:49 auth: Debug: vpopmail(toorop(a)respublica.fr,178.32.33.247): lookup user=toorop domain=respublica.fr Aug 28 10:59:49 auth: Debug: client out: OK 1 user=toorop(a)respublica.fr Aug 28 10:59:49 auth: Debug: master in: REQUEST 1 2211 1 e4920e51f96ae453663098df19c5b374 Aug 28 10:59:49 auth: Debug: vpopmail(toorop(a)respublica.fr,178.32.33.247): lookup user=toorop domain=respublica.fr Aug 28 10:59:49 imap-login: Info: Internal login failure (auth failed, 1 attempts): user=<toorop(a)respublica.fr>, method=CRAM-MD5, rip=178.32.33.247, lip=184.106.217.69, mpid=2214, TLS Aug 28 10:59:49 master: Error: service(auth): child 2212 killed with signal 11 (core dumps disabled) strace : http://pastebin.com/kYsWHP5J Thanks, -- Toorop «Ils ne savaient pas que c'était impossible, alors ils l'ont fait.» Mark Twain

2 3

[Dovecot] Roff typo in sievec.1.in
by Mike Abbott 27 Aug '10

27 Aug '10

There is a roff typo in pigeonhole's sievec.1.in. Roff treats the leading apostrophe on line 54 as an invalid command and produces bad output: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as for a com- piled Sieve binary file. Note that this option is not The output should be: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as '-'. The output is identical to what the sieve-dump(1) command pro- duces for a compiled Sieve binary file. Note that this Here is a patch: --- a/doc/man/sievec.1.in +++ b/doc/man/sievec.1.in @@ -50,8 +50,9 @@ Don\(aqt write the binary to \fIout\-file\fP, but write a textual dump of the binary instead. In this context, the \fIout\-file\fP value '\-' has special meaning: it causes the the textual dump to be written to \fBstdout\fP. -The \fIout\-file\fP argument may also be omitted, which has the same effect as -'\-'. The output is identical to what the \fBsieve\-dump\fP(1) command produces +The \fIout\-file\fP argument may also be omitted, which has the same effect +as '\-'. +The output is identical to what the \fBsieve\-dump\fP(1) command produces for a compiled Sieve binary file. Note that this option is not allowed when the \fIout\-file\fP argument is a directory. .TP

2 1