> On Jun 9, 2016, at 1:53 PM, Eric <[email protected]> wrote: > > Domain users usually use port 587 (submission) to authenticate for relay > purposes. How many users do you have? And, which ones are using the > submission port to authenticate in order to send email?
So far, it’s just me. I do have accounts in a half-dozen or so domains, all lightly used. I’ll be adding a half-dozen heavier users soon, once things stabilize. What’s odd is: 1. The segfaults I’m finding are not occurring around the sending of mail; some of them are in the middle of the night, which makes me wonder if they’re fake auth attempts from someone / somewhere else, brute-force crack attempts, or maybe attempts to use invalid characters or somehow trigger other bugs in the auth process; 2. With these segfaults, I’m not actually noticing any consequences so far - I find them in the logs, but that’s all. At an earlier point in the build process, I started segfaulting on every attempt to send mail when I changed from the self-signed cert created automatically to the LetsEncrypt cert I got for the domain, and until I raised the softlimit, they didn’t stop. (I think I was rebooting the server between changes at that point, which did the hard stop necessary for the submission/run change to take effect, since the build was brand new and I was the only one using it, and VM reboots are fast… just me being lazy.) Anyway, though, as far as I can tell, mail is working fine for me… but the segfaults are still popping up in the logs at weird times and intervals. I’ve sent a few messages (to the list) since I made the last change, and I’m tailing -f /var/log/messages in a term window, and no segfaults so far since I bumped the submission/run softlimit to 200 megs coming up on an hour ago now, but some of the windows between segfaults have been longer than that, so I’m still holding my breath. - Steve -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle.
