similar to: Maildir feature I'd like to see - SSD for newer messages

I just replaced my drives for Dovecot using Maildir format with a pair of Solid State Drives (SSD) in a raid 0 configuration. It's really really fast. Kind of expensive but it's like getting 20x the speed for 20x the price. I think the big gain is in the 0 seek time. Here's what I bought. Crucial RealSSD C300 CTFDDAC256MAG-1G1 2.5" 256GB SATA III MLC Internal Solid State

I'm advocating for a change in the IMAP specification to allow outgoing email to be sent over the same connection as incoming rather that having to separately configure outgoing SMTP email. There are two significant advantages to this concept. 1) It would greatly simplify setup for clients as they would only have to configure one connection rather than two. 2) Spam reduction by

Here's what I'd like. Limited master users, where someone can be a master users for some domains but not others. I think I could do what I want with the right kinds of variable passing that doesn't yet exist. Let me see if I can explain clearly. From the example in the wiki: auth_master_user_separator = * passdb { driver = sql args = /etc/dovecot/dovecot-sql-master.conf.ext

Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP

I just installed a limited test of RC10 last night. So far, all is great except for errors being logged for one user (out of about 150 users total). This one user has not yet complained or anything, but the log file has repeated entries of the following format for him (host and username changed to protect the guilty/innocent): Oct 24 06:13:02 mail dovecot: IMAP(username): file

I recently upgraded dovecot from 1.0.15 to 1.1.2 and since then I am getting the following types of things in the logs: Aug 21 17:23:13 mail1 dovecot: imap-login: Login: user=<myuser>, method=PLAIN, rip=172.16.78.20, lip=172.16.78.22 Aug 21 17:24:01 mail1 dovecot: Panic: IMAP(myuser): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed:

OK - I thought this was going to be easy. Maybe it is. I'm just not that good at reading directions. Trying to use dsync. Getting this error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) Currently using maildir. The setup is as follows: mail_uid = mail mail_gid = mail mail_location =

Hi, This small mail to share my observation about a recent move of mailboxes between two servers and ask about explanation and/or improvement about UIDL in dovecot. SV1 : Dovecot 0.99.14 / Red Hat Fedore Core 4 SV2 : Dovecot 1.07 / CentOS 5.2 Mailboxes in /var/spool/mail on the twoo servers. Test will be done with outlook express with option "leave message on server" checked. Goal is

And it's taking up more space on the 4T drive. What did I miss?

Is it possible to have some folders be mbox and some be maildir format? Why you might ask? Sometime for diagnostics I have the Exim MTA archive certain messages in MBOX format and then I want to copy them into an imao folder to look at them with Thunderbird. When I used MBOX all I had to do was copy the file into a folder and it worked. So what I'd like to do is have a folder with a

Here's what I'm trying to do. I have a spam filtering operation as a front end for other servers. I've created a virtual server for spam storage where the user will be able to log in using squirrelmail/dovecot to review and release their spam. The email is stored in maildir format. Piecing it together I can use squirrelmail to pipe the email into something so that if a use finds a

OK - here's whay I need to make it work for my Linuxconf compatible authentication system. First - a question: Will this work? I can find docs on "virtualfile. auth virtualfile { mechanisms = plain digest-md5 userdb = passwd-file /etc/vmail/passwd.%d passdb = passwd-file /etc/vmail/shadow.%d user = root } Then - since the dmain name selects the passwd file, if there were a

I'd like to make a suggestion. Let's drop the Alpha and come out with an official version 1.0. Here's my reasons. The 0.9x version are obsolete and people should be using the 1.0 Alpha versions which seem to me to do everything the previous versions did and more. It's as full featured and stable as all other IMAP servers and in my opinion is ready to be called 1.0. The

I am fighting this issue: Bug 1540376 ? Tiered volume performance degrades badly after a volume stop/start or system restart. https://bugzilla.redhat.com/show_bug.cgi?id=1540376 Does anyone have any ideas on what might be causing this, and what a fix or work-around might be? Thanks! ~ Jeff Byers ~ Tiered volume performance degrades badly after a volume stop/start or system restart. The

OK - Getting close to everything working in my weird configuration. Here's a problem I'm still having. I'm authenticating with this: userdb { driver = sql args = /etc/dovecot/master-combined-sql.conf } Default mail location: mail_location = maildir:/fakedir/%d/%n:INBOX=/email/%d/%n:LAYOUT=fs However - what I'd like to do is if the mail location doesn't exist then I

Not sure how this can be done. Right now I'm running a free backup MX record service. People point their high MX records to my servers and if they go down we store the email. When they come back up it's delivered. What I want to do is have a premium service that would allow them to view through IMAP the stored email. In order to do that I would have to deliver the email locally to a

Trying to clean out old undead messages from users to reduce disk space. Need a script that will recurse all the user directories and delete all unread email that is over 90 days old. Anyone have that?

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and

Or you can implement a policy server yourself. :)The protocol is not complicated, json over http. See?https://wiki.dovecot.org/Auth/Policy ---Aki TuomiDovecot oy -------- Original message --------From: Aki Tuomi <aki.tuomi at dovecot.fi> Date: 21/05/2018 19:13 (GMT+02:00) To: Marc Perkel <marc at perkel.com>, dovecot at dovecot.org Subject: Re: Dovecot blacklist?

Trying to get the master password to work. What am I doing wrong? Trying this test: /etc/dovecot.masterusers master:{plain}test auth_master_user_separator=* auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes #pass =yes } passdb passwd-file { # Path for