Tag Info

New answers tagged

0

I finally found how to make my StartSSL certificate works with Dovecot and OpenSMTPD (5.4.2p1) : For Dovecot, you need to concatenate the key and the certificate into a pem file - thanks @Alexus - and add these lines into your dovecot configuration file : # blablabla ssl = required ssl_key = </home/mail/ssl/dovecot.pem # Key ssl_cert = ...


0

per that document that you provided, try to put just private key & certificate into .pem and use same for file ssl_cert and ssl_key. following from my own system: [root@j /usr/local/etc/dovecot/conf.d]# grep ^ssl_ 10-ssl.conf ssl_cert = </usr/local/etc/dovecot/alexus.biz.pem ssl_key = </usr/local/etc/dovecot/alexus.biz.pem [root@j ...


0

Dovecot is indeed email server but it serves to the clients - not to other mailservers. IMAP and POP are not enough to send emails outbound - SMTP is needed.


2

Okay, after some more research I found the solution: Problem was inside the postfix configuration, not dovecot! Postfix had a wrong entry in the mydestination line - so it never used the virtual transport to deliver the messages to Dovecot, but delivered them directly to the local mailbox. After removing the entry from mydestination in the postfix config, ...


2

As I expected, the solution to this was tremendously simple: /etc/dovecot/conf.d/10-auth.conf includes two files: auth-system.conf.ext for system users, and auth-mydomain.conf.ext for virtual users. The order these files are included is important important, system users lookup after virtual users is easily performed by swapping both lines: [...] !include ...


0

The right answer is to use the ACE format (xn--XXXXX.tld). In theory, Dovecot does not have a problem working with more or less any characters in domain name (but it has to be enabled in its configuration via auth_username_chars). On the other hand, MUAs doesn't seem to support this, they expect the ascii-encoded string (though i thing they could support ...


2

As I got no answers, I've experimented myself and finally did the switch – which went smoothly. The advantage is, as initially stated, having at least CRAM-MD5 available for authentication on unencrypted transport, should encrypted transport not be available (yes, that happens) – plus making the migration from the old server smoother for those already using ...


2

The first line of the dovecot error indicates it doesn't have permission write to /var/mail/. This indicates the dovecot is running under an account without permission to write to the folder. /var/mail/ is owned by root:mail (UID/GID 0:8), giving full read/write/execute permissions to both root and the group mail. Dovecot is running under nicolai to access ...


1

I believe I've solved this problem, and hoping that this will serve as help for others who encounter this issue. A little disappointed that there wasn't a lot of help here, but I guess the act of writing it out may have helped. Anyway: In main.cf, the myorigin and mydestination variables need to be set to localhost. So: myorigin = localhost mydestination = ...


3

Since you have dovecot you can do that with doveadm(1). For example deleting mail saved in the Trash folder for user before 30 days: doveadm expunge mailbox Trash savedbefore 30d -u <user> You can use -A flag for all users and if you want to check first for the mails that match use the search/fetch commands - see doveadm-search(1): doveadm search ...


2

Notice this part in main.cf: smtpd_recipient_restrictions = permit_mynetworks ... So smptd will permit IP address from mynetworks to relay emails. Add your IP to mynetworks part. Let say your IP address is 192.168.1.123, change the parameter to mynetworks = 127.0.0.0/8 192.168.1.123 Then you can send emails if your IP address is 192.168.1.123.


0

If you use the separate configuration directory option of dovecot (for example, on my system, this setting is in /etc/dovecot/symbiosis.d/40-imap-settings/10-plugins),you need to do a make at the toplevel to merge all the separate files into one before you stop and start the server. This answer applies to the bytemark symbiosis environment but others ...


0

You don´t have configured the port for IMAPs. service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } If you enter netstat -tulpen you should now see a line like tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 0 5728257 23418/dovecot Now the server will be listen on Port 993.


3

It depends on the address classes of your domain. That's why I ask postconf -n output and some maillog lines). There are four address classes in postfix, two of them has capabilities to deliver it directly to mailbox: local domain class and virtual mailbox domain class. If your domain listed on mydestination parameter, then it falls into local domain ...



Top 50 recent answers are included