Tag Info

Hot answers tagged

6

Use the recipient_delimiter directive in Postfix: recipient_delimiter = + There is no need to do configuration in dovecot.


3

Given that Maildir uses the filesystem exclusively, I feel it should be possible to just mv ~fred/Maildir ~oldemployees/Maildir/fred or similar It depends on dovecot configuration By default dovecot use Maildir++ layout to store the email. ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. The tmp directory ...


3

A little guess based on comparing your configuration to my. CONCAT('maildir:storage=',quota) AS quota should rather be CONCAT('maildir:storage=',quota) AS quota_rule I think you are overriding the quota= setting from configuration, by per-user entry. (But I am no expert, so really just a guess) Do not remember why, but my quota query is ...


3

To make this work you'll have to at least move these messages into a MailDir like structure. My Dovecot maildir looks like this for the account ahoy@iswhale.com ./iswhale.com/ahoy/.Drafts/tmp ./iswhale.com/ahoy/.Drafts/new ./iswhale.com/ahoy/.Drafts/cur ./iswhale.com/ahoy/cur ./iswhale.com/ahoy/new ./iswhale.com/ahoy/tmp If you make a new sub-folder, say ...


2

In mail architecture like above, you need synchronize two configuration The format* and location of where postfix stores the incoming email The format* and location of where dovecot retrieves the email When they are out of sync, dovecot won't find email that previously stored by postfix. The related dovecot parameter is mail_location = ...


2

Try verbose_ssl = yes. This will make Dovecot log all the problems it sees with SSL connections.


2

OK, worked this out. There were two simple issues: The reason I wasn't seen anything in the debug log, is that error messages were going to a different log. I assumed the debug log would contain ALL messages. I was wrong. Once I had realised that, and started looking in mail-err.log, I observed the error, which was namespace configuration error: list=yes ...


2

It's fine to use PAM for authentication, but separate the user accounts for the administrative access and applications on user-level like mail. You have to either separate the user database and authentication of dovecot and postfix from PAM, the system one's, or you have to create another system account you use for administration via SSH and not for mail. ...


2

At some level, a self-signed certificate will always appear in a certificate chain - most notably the case with CA certs, which are by definition self-signed, but are trusted. You are seeing that message because the StartSSL CA cert is self-signed. Your chain file is also wrong - you don't need the client certificates. The file should be in the following ...


1

I have found the solution now with the guys here at Server Fault. There were two problems going on: Why wasnt I able to receive Mails? I migrated the server and updated the DNS A records, but forgot to update the mx records, so the old server was still receiving the mails, where postfix and dovecot were still running. Updating the mx record solved the ...


1

There is a security flaw because you are using a privileged account (sudo account) to perform a task a normal user (without being privileged) would normally perform. I would add a simple system account and use it to authenticate against roundcube to reach my emails. Furthermore, I don't believe you needa system account for this. There must be another way ...


1

I think I found a way to set up a maildir structure without making any changes to the folders and files I have. I made a separate maildir folder in a different place, and used symlinks to point to my mail-containing folders, like this: maildir ├─ .2015-01 │ └─ cur -> path/to/2015-01 └─ .2015-02 └─ cur -> path/to/2015-02 I gave dovecot write ...



Only top voted, non community-wiki answers of a minimum length are eligible