14
What you need is a chain certificate. You can create one like this:
cat /etc/ssl/server.pem /etc/ssl/cacert.pem > /etc/ssl/chain.pem
and then use the chain as the server certificate
ssl_cert = </etc/ssl/chain.pem
ssl_key = </etc/ssl/server.key
Now when you connect with openssl s_client, you should get no errors (provided everything else is set ...
12
According to this thread titled: IMAP Dovecot Error - Corrupted index cache 10.6.4 it sounds like you just need to do the following:
Scribit
Re: IMAP Dovecot Error - Corrupted index cache 10.6.4
Nov 30, 2010 11:10 AM (in response to Scribit)
I am not sure if this is the best procedure and there may be unintended consequences, but this is ...
12
I had similar problems with Thunderbird on Mac OSX and a new StartSSL cert.
Thunderbird uses OCSP to validate the certificates and fails silently in this special case. Additionally the StartSSL OCSP server need some time to update the catalogue of known certificates (compare with https://forum.startcom.org/viewtopic.php?t=2654).
To check if OCSP is the ...
12
Yes, you may delete files from that folder manually. Dovecot is designed to assume that other software besides itself might manipulate the Maildir folder, including adding, removing, and renaming (the portion of the filename after the colon). It will update the indices accordingly as soon as it notices.
In order to avoid deleting those mails outright, you ...
8
Dovecot wiki
# Use "host= ... pass=foo#bar" if your password has '#' character
so your /etc/dovecot/dovecot-sql.conf.ext should be
driver = mysql
connect = "host=127.0.0.1 dbname=froxlor user=froxlor password=test#test"
default_pass_scheme = CRYPT
8
The correct procedure to execute a script (I use a shell script) upon receipt of a mail message is the following. It involves modifying postfix's configuration file, master.cf (which, in my Debian, is located in /etc/postfix) by adding the following line:
my_shell_script unix - n n - - pipe flags=F user=MY_USERNAME argv=/path/to/my/shell/script ${sender} ${...
6
It seems that your problem is because cron scripts run with a different PATH value by default. For example, on Ubuntu as root you have /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in your PATH by default. But your cron script running as root has a more limited PATH value: /usr/bin:/bin.
I recommend you to to set the PATH environment variable ...
6
netstat is your friend when you're trying to troubleshoot a lot of network-related problems. To find a listening port, I would use netstat -tulpn | grep :<port number>
For example, to find what pids are listening on port 22, I would run:
netstat -tulpn | grep :22
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3062/sshd
That tells me that sshd with ...
4
Dovecot isn't a mail server
You're looking at the wrong thing when you say "Dovecot to ignore....". Dovecot is a POP/IMAP client and doesn't really have anything to do with the attempt of Redmine to send emails to different users.
This functionality rests with Redmine itself and whatever mail server/frontend you're using (Sendmail, Postfix, etc.).
There's ...
4
I can see two obvious solutions.
If you are using procmail as the MDA on your server, or are willing to convert to using it, then you can run any arbitrary script on any arbitrary email through procmail's | (pipe) recipe action. It hopefully won't be started as root, but it should be easy to make a script that performs the required magic and which can be ...
4
You can use dovecot's own tools for that, e.g. doveadm move. You can use search queries to select mails.
This selects all mails in a date range and moves them to the Archive
doveadm move -u jane Archive/2011/09 mailbox INBOX BEFORE 2011-10-01 SINCE 01-Sep-2011
To just search without action use the search command:
doveadm search -u jane mailbox INBOX ...
4
TL;DR: See Summing up!
I regularly also get emails with UTF-8 chars in the Subject: line. Never so far any within other headers.
While a 'soft-fail'-mode in postfix is unknown to me, you may setup another smtp transport and filtering bounces through it as a kind of failsafe-mode. However, I would have yet to complete this setup myself. As of now, the ...
4
You're using user database prefetch, which can be used to reduce the number of queries to the password database by already reading information on the user during authentication, but this only works when the user actually authenticated.
For mail delivery, the LDA will obviously not authenticate, so you need a second user database configuration that reads ...
4
As I further explored the subject, felt something was out of place definitively.
My suspicions also grew even more, as when ungzipping some messages, the name was actually updated to reflected the new bigger size when dovecot saw them.
So upon further investigation, found dovecot can have compression on place.
From Enable compression on Dovecot storage
...
3
Your /etc/postfix/main.cf file doesn't mention procmail anywhere. This is the problem, AFAIK.
In my case, I have:
mailbox_command = procmail -a "$EXTENSION"
and my procmail config file is in ~user/.procmailrc. However this is a real user on the machine. It seems that you're using virtual transport, in which case I suppose that you should use something ...
3
I find the easiest way to restore the index files is this.
Stop Dovecot
sudo systemctl stop dovecot
Rename, or delete, the entire .imap folder for any affected users (I prefer delete, but the cautious may feel otherwise)
sudo rm -R /home/bernhard/Mail/.indexes/.imap/
Start Dovecot
sudo systemctl start dovecot
When the mailbox is checked, Dovecot will ...
3
By default Dovecot uses Maildir++ directory layout for organizing mailbox directories. This means that all the folders are directly inside ~/Maildir directory, and:
~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain
the messages for INBOX.
You can read more about the layout here
Thus what you complain about is standard behavior. You can ...
3
In general the server offers to the requesting client the server certificate plus all intermediary certification authorities certificates so that the client can match the top certificate of the chain to one of his trusted (root) certificates. That is true for apache, dovecot and postfix. Dovecot doesn't seem to have a setting for the trust chain, so in this ...
3
After some back-and-forth through comments and chat the OP's problem is now resolved. The IMAP server needed to be specified as imap.mydomain.com instead of mydomain.com although for some reason this only worked when set using the advanced account settings, not using the account creation dialog box.
In addition to mentioning this situation-specific solution,...
3
thanks @ Celada, based on your comment it did seem to be a corrupt installation of dovecot.
I installed it using sudo apt-get install dovecot-imapd dovecot-pop3d and the service is starting fine. Am also able to telnet successfully.
Before I configured this for LDAP via SASL it was working, so I assumed I messed some configuration. For some reason the root ...
3
Finally, i found a problem! There was a short parameter in master.cf file.
I had:
-o smtpd_recipient_restrictions=permit_sasl_authenticated, reject
Must be:
-o smtpd_recipient_restrictions=permit_sasl_authenticated, reject_unauth_destination
Parameter reject needs to be changed to reject_unauth_destination because of smtpd rejects all incoming ...
3
You have to uncomment the smtps block in your main.cf, then restart Postfix. STARTTLS works because it uses the standard smtp port (25).
3
You would use a virtual_map to map virtual users in your second domain to either real users on the server or to other addresses (similar to an alias).
e.g. in /etc/postfix/main.cf you would have:
virtual_maps = hash:/etc/postfix/virtual
and in /etc/postfix/virtual:
example.com VIRTUAL
john@example.com john@myrealdomain.example.com
joe@...
3
You might also like a solution using ss that is more systematic and more precise than grepping port numbers.
# ss -t -l 'sport = 22'
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::ssh :::*
3
You experience the very purpose of certificates: preventing to accidentally connect with a server that isn't the one you expect (mail.example.com instead of beta.example.com). You must configure a certificate issued for the domain you connect to, ie. if the mail client connects to beta.example.com, you need a certificate for beta.example.com.
Either get ...
3
According to Dovecot manual, the var_name = </path/to/file syntax reads the file contents into the variable.
3
The error message at the top of the question tells you exactly what the problem is, and where to look for it:
Oct 28 15:29:52 (server name) dovecot[14267]: imap-login: Fatal: Couldn't parse private ssl_key
error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY
The problem you have listed is nothing to do with Postfix; it's ...
3
It is probably generated by the PAM pam_mail.so module.
Edit /etc/pam.d/login en comment out the line that looks like:
session optional pam_mail.so standard
Alternatively, keep the line but remove standard if it's there, and add nopen to the end.
It may be necessary to do the same in the /etc/pam.d/sshd file.
See man pam_mail for more information.
3
You have to use the --expand option of certbot
--expand tells Certbot to update an existing certificate with a new certificate that contains all of the old domains and one or more additional new domains. With the --expand option, use the -d option to specify all existing domains and one or more new domains.
Example :
certbot --expand -d mysite.com,imap....
2
iptables -A INPUT -p tcp --dport 25 -m set --set blocking src -j DROP
iptables -A INPUT -p tcp --dport 143 -m set --set blocking src -j DROP
... or whatever ports you're using.
Only top voted, non community-wiki answers of a minimum length are eligible
