Tag Info

Hot answers tagged

8

It is not really necessary to use one IP address per domain, both Postfix and Dovecot (and the DNS system) are perfectly capable of handling a practical unlimited amount of domains with only one IP. Even if you do use only one domain per IP, you would usually still run only one instance of Postfix/Dovecot and configure them accordingly to handle mails for ...


4

You have doubled imap_acl in the config, dovecot try to link that library twice protocol imap { mail_max_userip_connections = 20 mail_plugins = acl imap_acl imap_acl }


3

Both Postfix and Dovecot use Certificate-Key pair that has same format with Apache Certificate-Key pair. Because of that, you can steal use solution from this thread: Converting a Java Keystore into PEM Format. Convert it pkcs12 format keytool -importkeystore -srckeystore foo.jks \ -destkeystore foo.p12 \ -srcstoretype jks \ ...


3

The first thing to point out is that the solution is not to disable SELinux but to work with it. There are tools that you can use to determine wat you need to do and the good news is that they are much improved in CentOS 7.1 compared to their earlier versions. First run audit2why on the AVC messages you have gathered audit2why <FileContainingMessages ...


3

You probably want to set sender_canonical_maps for outgoing mails. This way you get both header and envolope addresses rewritten. But for incoming mails recipient_canonical_maps doesn't work since you can only map to one E-Mail address. Anyways it's probably cleaner to have recipient_bcc_maps (delivers to info, bob1 and bob2) or virtual_alias_maps (delivers ...


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


2

Thanks masegaloeh! Perhaps you have mismatch in userdb { args }' and user_attrs ` in dovecot-ldap.conf – masegaloeh 22 hours ago old one: userdb { args = uid=106 gid=114 home=/var/mail/%u allow_all_users=yes driver = static } new: userdb { args = uid=106 gid=114 home=/var/mail/%n allow_all_users=yes driver = ...


2

The dovecot wiki would seem to suggest that Pluggable Authentication Modules(PAM) is a pretty common authentication solution. PAM also works well with LDAP and there is a lot of information about integrating existing LDAP servers into PAM authentication schemes. PAM also offers a lot of different customization of the authorization process for various ...


1

Do you have an auth_mechanisms line in your dovecot configuration? If so, post it, if not that's probably the issue. default for reference: auth_mechanisms = plain login But you're probably going to want something else because of your postfix sasl security options, both plaintext and login are considered plaintext. More: ...


1

I worked around the issue by defining the namespace in the configuration twice (inbox and inbox_alt, with the latter with disabled = yes), and put this in the userdb: userdb_namespace/inbox/disabled=yes userdb_namespace/inbox_alt/disabled=no This way, I could successfully set prefix in inbox_alt to the empty string.


1

From the information you provided, I'm assuming that you are most probably running RHEL 6 or CentOS 6. Perhaps you should try starting the dovecot service manually first and post the log again. --Update Ok. These steps should fix the problem. Edit the file using the command vi /etc/dovecot.conf Find the line which has login_process_size Uncomment it and ...


1

Nevermind, I found dsync tool from Dovecot wiki. As alternative, you can also use imapsync.


1

Solved. I uncommented the following line: smtp inet n - - - - smtpd I can now send and receive emails over TLS with the following configuration: IMAPS Server: imap.mydomain.org Port: 993 User: mail@mydomain.org Security: SSL/TLS Authentification: Password SMTP Server: imap.mydomain.org Port: 465 User: ...


1

Should have looked better into the documentation. According to the exim documentation, exim does not support ssha512(yet?). I took the easy way out and just told exim to use dovecot for authentication purposes, like the dovecot documentation tells you to. I'm sorry to have wasted your time and I hope, someone will benefit from my experience.



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