![]() |
|
Problems with dkim and amavis - Printable Version +- Sentora Support Forums (https://senforums.mach-hosting.com) +-- Forum: Sentora Forum Archives (https://senforums.mach-hosting.com/forumdisplay.php?fid=5) +--- Forum: Sentora Public Support Forums v1.0.x (https://senforums.mach-hosting.com/forumdisplay.php?fid=32) +---- Forum: Email Support v1.0.x (https://senforums.mach-hosting.com/forumdisplay.php?fid=35) +---- Thread: Problems with dkim and amavis (/showthread.php?tid=2631) |
Problems with dkim and amavis - HogensHero - 02-25-2016 Hey guys, I have a question first then I will explain the issue I am having. First I have noticed that there are two postfix folders with main.cf in both folders and master.cf in the /sentora/configs/postfix folder and a symbolic link of master.cf in /etc/postfix. The question is, which main.cf does postfix actually use and if it is either is there a way to permanently link it to the /sentora/configs/... folder? Now the issue. I have been trying to set our email server to authticate using spf, dkim and dmarc records. I have a working email server that I added all of these records to and was working good until I looked into the log and noticed that the email were being deffered due to not passing thru amavis-new. So I set up amavis-new, spamassasin and clamv to check mails for viruses and spam. I now have those working good but now the email system will not validate the dkim signature from the server. Looking in the logs I have found this error: "Feb 24 13:03:37 myhostname postfix/smtpd[pid#]: warning: milter inet:127.0.0.1:8891: bad protocol information: content_filter". This is the settings in the main.cf file in /etc/postfix: # DKIM smtpd_milters = inet:127.0.0.1:8891 non_smtpd_milters = $smtpd_milters milter_default_action = accept milter_protocol = content_filter = amavis:[127.0.0.1]:10024 receive_override_options = no_address_mappings I have searched for 2 days straight for a solution and any help with this would be appreciated. EDIT: I made a change in the dkim settings listed above to test and I got it working. I changed: content_filter = amavis:[127.0.0.1]:10024 with milter_protocol = 2 The original question still stands though. RE: Problems with dkim and amavis - Me.B - 02-25-2016 The reply over the .cf file is obvious the symbolic link point to sentora config folder. That's the main postfix config used here. If you edit the symbolic link file and save it you will break the symbolic link! I didn't test the setting to offer an answer. There is guides in How to section over there. M B RE: Problems with dkim and amavis - HogensHero - 02-25-2016 Well I attempted to edit the main.cf in the sentora folder and created a new symbolic link in the Postfix folder that pointed to the sentora folder. When I restarted the server it removed the link and rewrote a new main.cf that I think came from the sentora folder. That is why I am asking which one is used. |