Tag Info

Hot answers tagged

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 ...


3

These are not error messages but debug messages and are clearly marked as these. Unless you need verbose_ssl to debug a problem you should just switch it off. More background: it is showing every state it is going through when doing an SSL handshake. To display the description of the state it is using the function SSL_state_string_long from OpenSSL. This ...


3

You're not using the virtual_mailbox_base parameter like you're supposed to. A prefix that the virtual(8) delivery agent prepends to all pathname results from $virtual_mailbox_maps table lookups. This is a safety measure to ensure that an out of control map doesn't litter the file system with mailboxes. This is only a safety measure and isn't designed ...


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.


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 ...


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 ...


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, ...


1

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 ...


1

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 = ...


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 = ...



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