June 2016 - dovecot - dovecot.org

tlsv1 alert unknown ca: SSL alert number 48
by Maurizio Dall'Acqua 19 Jun '16

19 Jun '16

The version of Roundcube I am using is 0.9.5+dfsg1-4.1

3 6

Custom storage backend
by Cornelius Charlie 18 Jun '16

18 Jun '16

Hello, We use a storage backend that is using non-standard apis. We would like to know if there is some way to write a storage backend as a plugin instead of hardcoding our changes directly into the dovecot source ? Thanks.

2 1

archive all saved IMAP messages
by KT Walrus 18 Jun '16

18 Jun '16

I need to archive (i.e., send to another mail server) all messages saved on my mail servers. I’ve implemented for SMTP submission, but haven’t figured out how to archive messages saved by IMAP (like to Drafts, Sent, etc.). How would I best implement this? Can I enable Sieve plugin for IMAP? Or, some other method? Like one way backup to archive server? I really only need to archive the messages sent/saved by a user and not the messages received from other users. Kevin

2 4

tlsv1 alert unknown ca: SSL alert number 48
by Maurizio Dall'Acqua 18 Jun '16

18 Jun '16

Hi, I have set up a mail server with postfix+dovecot 2.2.13 on my raspberry pi running Raspbian Jassie OS. Now I would like to add an on-line e-mail client like Squirrelmail or Roundcube. I was able to start up these two clients but when I try to login I get this error message in the dovecot log: tlsv1 alert unknown ca: SSL alert number 48 But I have inserted the self-signed certificate and key in /etc/dovecot/conf.d/10-master.conf Moreover, I can send and receive e-mails from/to my server, and I can login successfully to dovecot IMAP with Thunderbird. Can somebody give me a clue on how to solve this problem? Any help would me much appreciated. Regards, Maurizio

4 9

Mail dates
by ＠lbutlr 18 Jun '16

18 Jun '16

Where exactly does dovecot get the date that it reports via IMAP? I have a lot of messages that were restored from an archive and so all have the same date, despite being over the span over several years. I tried setting the timestamps of the files to the date in the Received header, but that didn’t seem to make any difference to what my IMAP clients see. Do I have to rename the files to the right epoch seconds in order for dovecot to show the right dates to the IMAP clients? … It seems I’ve been here before, but I don’t remember the solution … -- 'What is this thing, anyway?' said the Dean, inspecting the implement in his hands. 'It's called a shovel', said the Senior Wrangler. 'I've seen the gardeners use them. You stick the sharp end in the ground. Then it gets a bit technical.' --Reaper Man

2 7

Advice needed: SMTP/LMTP or IMAP for internal message delivery
by KT Walrus 17 Jun '16

17 Jun '16

I’ve implemented “next day” delivery this week by taking messages submitted through Postfix, queuing the messages in a MySQL database, and sending them out for delivery through another Postfix instance/Dovecot LMTP proxy with final delivery using the destination mail servers LMTP service. Delivery is sent to a “next day” mail server which is sync’d to the recipient’s mail server using “doveadm sync -A tcp:next-day-mail:12345” on each mail server in the early morning. This all appears to be working well. I do have a need to deliver these messages into specific mail folders in the recipient’s mailbox and I was planning on using global Sieve scripts running on the “next day” mail server to place the messages in the proper folder (not all messages are delivered to the INBOX folder). I am using a PHP script to move the messages from Postfix to the MySQL database and then later sending them via SMTP to the internal Postfix instance for delivery to the “next day” mail server. I started investing how to code the Sieve scripts today and it occurred to me that I could greatly simplify message delivery by using IMAP to deliver the messages to the “next day” mail server. The PHP script would be able to deliver the exact message that should be stored to the proper folders setting the \Seen flags appropriately. My backend “next day” mail server already supports Master password login so I figure the PHP script should be able to login via IMAP to access the folders in the recipient mailboxes. Also, the PHP script could do other mailbox maintenance tasks when it connects to the user’s mailbox such as purge folders by age, message count, etc. The PHP script could also retrieve info about the current state of the user’s mailbox folders (like the date of the oldest unread message, how many messages have been read in the last week or so, etc) and store this data in the MySQL DB. I’m looking for any advice on whether to scrap the current plan of deploying internal Postfix SMTP/Dovecot LMTP proxy/Dovecot LMTP/Sieve script for “next day” mail delivery and just write PHP script to access Dovecot IMAP (direct to the “next day” mail server or to the user’s mail server for “immediate” delivery). This would allow me to drop using Dovecot LMTP at all. Postfix SMTP would only be configured to invoke a PHP script to deliver messages to the database (which is already implemented). Postfix would still use Dovecot IMAP authentication, but only Dovecot IMAP service would need to be “highly available”. Any opinions? Should I dump LMTP? Kevin

1 0

Migrate email account from Dovecot to Dovecot servers
by Marco Usai 17 Jun '16

17 Jun '16

Hello, 1) I needto migrate some mbox imap email accounts from a shared webhosting provider toanother one. 2) Bothservers seem to use Devecot, as a telnet command on port 143 shows an identicalresponse:* OK[CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACESTARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 3) I don'tknow Dovecot version because I don't have access to "dovecot --version"command. 4) I can'tuse "doveadm-sync" because the command is not available on my sharedhosting account. 5) I preferto leave imapsync perl script as the last option because I want to preserve theUID. So, I needto know what migration procedure can be adopted: if I copythe /home/user/mail/ directory containing all email account from the sourceserver to the destination server, can I expect to see all accounts working withall the emails transferred ? Should I firstcreate from cPanel all the email account with identical names and password onthe destination server ? Anysuggestion will be much appreciated. Thanks in advance!

1 0

Double variable expansion / multiple password mechanisms
by Leon Kyneur 17 Jun '16

17 Jun '16

Hi, Trying to solve the problem of supporting multiple auth mechanisms + proxy and really don't want to store user passwords in plain test and fine to do master user to backend. I had the crazy thought I could do something like the following: For each user Store supported password schemes as LDAP attributes: userPasswordCRAM-MD5: {CRAM-MD5}xxx userPasswordDIGEST-MD5: {DIGEST-MD5}xxxx userPasswordSCRAM: {SCRAM-SHA-1}xxxx userPasswordNTLM: {NTLM}xxxx then: =password=%{ldap:userPassword%m} <- Though this doesn't work.. just wondering if it could possibly work or if I should give up on this crazy idea :) Thanks Leon

3 5

Multiple ACTIVE Sieve scripts
by Aaron Müller 17 Jun '16

17 Jun '16

Hi! Is there a reason the email filter sieve can only activate one single script? > list "mailinglists.sieve" "spam.sieve" ACTIVE > activate mailinglists.sieve > list "mailinglists.sieve" ACTIVE "spam.sieve" > I can't see the logic here ... I am doing something wrong? Aaron

2 1

Mailbox location
by Doug Hardie 17 Jun '16

17 Jun '16

I am running a small server with a fixed number of users. Postfix is using dovecot lda so that I can run pigeonhole. I have setup a user file with the ids and passwords and everything authenticates properly. Postfix uses that also. However, mail is consistently delivered to user@domain. How do I tell it to deliver to just user? I have tried setting a variety of different things like: 10-mail.conf:mail_location = maildir:/var/mail/home_mail/%u userdb { driver = static args = uid=2222 gid=2222 home=/var/mail/home_mail/%u } and a few other things. None of them affected the mailbox location. Fortunately, this is a test system as I probably have mucked up the config files by now. — Doug

2 2