- dovecot - dovecot.org

[Dovecot] [+]: Exim / Dovecot and AUTH LOGIN
by Frank Elsner 08 May '12

08 May '12

On Tue, 8 May 2012 15:22:11 +0200 Frank Elsner wrote: > > Hi to both adressed mailing lists, > > I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL Forgot to mention the versions :-( exim 4.77 dovecot 2.1.6 self compiled under Fedora 14. --Frank Elsner

1 0

[Dovecot] dovecot smtp authentication with sendmail
by Hadi Salem 08 May '12

08 May '12

Hi, It’s possible to use sasl dovecot smtp authentication with sendmail ? Hadi.Salem

4 3

[Dovecot] Exim / Dovecot and AUTH LOGIN
by Frank Elsner 08 May '12

08 May '12

Hi to both adressed mailing lists, I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL exim.conf: | plain: | driver = dovecot | public_name = PLAIN | server_socket = /var/run/dovecot/auth-client | server_set_id = $auth1 | | login: | driver = dovecot | public_name = LOGIN | server_socket = /var/run/dovecot/auth-client | server_set_id = $auth1 10-master.conf for dovecot: | service auth { | # auth_socket_path points to this userdb socket by default. It's typically | # used by dovecot-lda, doveadm, possibly imap process, etc. Its default | # permissions make it readable only by root, but you may need to relax these | # permissions. Users that have access to this socket are able to get a list | # of all usernames and get results of everyone's userdb lookups. | # unix_listener auth-userdb { | #mode = 0600 | #user = | #group = | # } | | # Exim SMTP AUTH | unix_listener auth-client { | mode = 0660 | user = exim | group = exim | } PLAIN Authentication works perfect, LOGIN gives 2012-05-08 15:08:43 login authenticator failed for xxxxxx.tu-berlin.de [130.149.X.YY]: 435 Unable to authenticate at present: authentication socket protocol error Where is the problem? Kind regards, Frank Elsner

1 0

Re: [Dovecot] Shared namespace
by Daniel L. Miller 08 May '12

08 May '12

On 5/7/2012 6:46 AM, Daniel L. Miller wrote: > On 5/6/2012 8:34 PM, Daniel L. Miller wrote: >> I'm not sure what's triggered it - I THINK it has something to do >> with a force-resync, but not sure. >> >> I'm no longer viewing my full list of shared mailboxes. I used to >> have a number of users shown - they had all had their ACL's set >> individually and were shown in the list. "doveadm acl debug" shows >> they SHOULD be shown - at least I think so, as the output for the >> mailboxes that DO appear is identical for those that don't. >> >> Where should I look for breakage? > > After upgrading to 2.1.6 - mailboxes are back. Not sure I want to TRY > to break it again... > Ok - I broke it again. Tried changing mail_shared_explicit_inbox to no - problem mailboxes disappeared again. Changed back to yes - they came back. Problem with both Thunderbird and Roundcube as clients. -- Daniel

2 9

[Dovecot] courier to dovecot
by Grafibit Rendszergazda 08 May '12

08 May '12

Dear All, I know there were many threads on this topic. I was searching the archive and the net also, but did not find a solution on my problem. I hope you can help me. I am migrating from an old server using courier to a new server with dovecot and i can not manage to have the same uids after the migration. After copying the message files from the old server to the new, and executing the script from the wiki page the messages are still re-downloaded by the mail clients. After telnet and logging in to the old server port 110, I got the following on the command *uidl*: 1 UID377-1278276092 2 UID387-1278276092 3 UID394-1278276092 4 UID498-1278276092 5 UID499-1278276092 6 UID564-1278276092 On the new server i set up the *pop3_uidl_format = UID%u-%v* because it seems for me that the old server is using the same uidl format. Either if i execute the /./courier-dovecot-migrate.pl --to-dovecot --recursive --convert /command or i don't the uidls on the new server won't be the same. Both the %u and %v numbers are differ. Please give me any hints how to continue the investigation to have a successful migration. Thank you in advance, Tamás * dovecot -n* # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-0.bpo.2-amd64 x86_64 Debian 6.0.4 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /var/lib/dtc/etc/ssl/dovecot/new.cert.cert ssl_key_file: /var/lib/dtc/etc/ssl/dovecot/new.cert.key disable_plaintext_auth: 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_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location: maildir:%h/Maildir 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(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 pop3_uidl_format: UID%u-%v managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: mail(a)exemple.com mail_plugin_dir: /usr/lib/dovecot/modules/lda auth_socket_path: /var/run/dovecot-auth-master log_path: /var/log/sieve.log info_log_path: /var/log/sieve.info mail_plugins: sieve quota auth default: passdb: driver: sql args: /var/lib/dtc/etc/dovecot-mysql.conf userdb: driver: prefetch userdb: driver: sql args: /var/lib/dtc/etc/dovecot-mysql.conf socket: type: listen client: path: /var/run/dovecot/dovecot-auth-client mode: 438 master: path: /var/run/dovecot-auth-master mode: 384 user: dtc plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve quota: maildir

3 3

Re: [Dovecot] Upgrading known problems (2.0 to 2.1) ?
by Timo Sirainen 08 May '12

08 May '12

Yes, that's possible. The IMAP/POP3 servers behind Dovecot director wouldn't even need to be Dovecots at all. Although you really want to use v2.1 director since it has a lot of fixes compared to v2.0. On 8.5.2012, at 0.02, Jean Michel wrote: > Thanks, an other thing is that I didnt saw anything about a cenario like this, its possible to have a director working on 2.0 and a backend with 2.1 simultaneously and vice-versa? > > 2012/5/7 Timo Sirainen <tss(a)iki.fi> > On 7.5.2012, at 23.21, Jean Michel wrote: > > > Is there any known/possible problem while upgrading from dovecot 2.0 to 2.1 > > ? > > Did anybody had any trouble with this ? > > http://wiki2.dovecot.org/Upgrading/2.1 lists all known problems. > > > > > -- > ------------------------------ > Jean Michel Feltrin >

1 0

[Dovecot] Upgrading known problems (2.0 to 2.1) ?
by Jean Michel 07 May '12

07 May '12

Is there any known/possible problem while upgrading from dovecot 2.0 to 2.1 ? Did anybody had any trouble with this ? ------------------------------ Jean Michel Feltrin

2 1

[Dovecot] dsync with virtual users
by Ken Stevenson 07 May '12

07 May '12

I'm using dovecot v2.0.16

3 3

[Dovecot] Panic in index-sync.c: line 25 on dovecot-1.2.17
by Leon Meßner 07 May '12

07 May '12

Hi, with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error after doing a system upgrade. May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) May 7 22:04:27 mail kernel: pid 79989 (deliver), uid 4873: exited on signal 6 (core dumped) this only happens to one user and only with mail from one mailinglist (this one). Mails do get filtered by sieve. After some delivery attempts the mail finaly gets stored alright in the maildir. May 7 22:23:27 mail dovecot: deliver(elon): sieve: msgid=<assp.047487a390.4FA82AA5.60907 09(a)amfes.com>: stored mail into mailbox 'dovecot' May 7 22:23:27 mail postfix/local[82289]: 7DED511402: to=<elon(a)physik.tu-berlin.de>, orig_to=<l.messner(a)physik.tu-berlin.de>, relay=local, delay=1141, delays=1141/0.01/0/0.26, dsn=2.0.0, status=sent (delivered to command: /usr/local/libexec/dovecot/deliver) May 7 22:23:27 mail postfix/qmgr[1303]: 7DED511402: removed After that a new mail does the same dance (perhaps until the next one to this ML arrives). The maildirs are on NFS and in this case only beeing used with my instance of mutt and two other postfix+dovecot servers which are quite idle. Whats the way to debug this ? Thanks, Leon

2 2

[Dovecot] Proxying for some users and having the rest local?
by Dr Josef Karthauser 07 May '12

07 May '12

I'm migrating a load of mailboxes from cyrus to a new dovecot server. What I'd like to do is to switch the DNS to dovecot, and set things up so that all old imap mailboxes are accessed through the dovecot proxy. That way I can migrate them one at a time independent of DNS issues. I've got a load of users specified in mysql, and that configuration works well for local mailboxes. How do I configure things so that I can switch proxy access on and off? What's I've got so far is: password_query = SELECT user, domain, password, "masteruser" as master, "masterpass" as pass, proxy, "remoteimap.server" as host FROM mailboxes \ WHERE user = '%n' AND isMailbox AND active AND domain = '%d' I imagined that I could switch the proxy per user by setting proxy='n' or proxy=null for any users that want to be local, and proxy='y' for any users that I want to forward on to the original server. It doesn't appear to work that way though. Irrespective of the proxy value dovecot appears to try and proxy all users. What am I doing wrong? I can't work it out from the docs, and the source will take quite a bit of studying to get to the bottom of it all. Thanks :), Joe

2 3