Paul Schmehl via Postfix-users: > I'm 77. I've been retired for 10 years. Now I'm struggling trying > to get postfix working with Dovecot and Spamasassin on a CentOS 7 > server. I manage a small hobby domain for some friends (for free), > and the changes in systems are so dramatic that I feel I'm losing > touch.
Welcome back. I'm also updating some different infrastructure from a similar vintage, and translating configurations from the past to the present can be challenging. > I read this doc to help me understand the new setup: > https://samhobbs.co.uk/2014/03/raspberry-pi-email-server-part-4-spam-detection-spamassassin > > I used to use filter.sh and didn't run the spamd daemon, but I > thought that using the daemon would be the best way to go now. > > I uninstalled postfix 2.10 and installed postfix 3.9. I installed > spamassassin 3.4. I copied my old 2.1 master.cf and main.cf to the > new configs (after backing those up) and started up both daemons. > (I don't know if that's a mistake. > > I can send and receive email, including remotely using saslauth. > But, I'm not gettting headers altered by spamassassin and I'm > seeing some warnings in the logs that bother me. > > Here's the spamassassin bits in master.cf: > > smtp inet n - n - - smtpd > -o content_filter=spamassassin > > spamassassin unix - n n - - pipe > user=spamd argv=/usr/local/bin/spamc -f -e > /usr/sbin/sendmail -oi -f ${sender} ${recipient} So that one seems to be failing. > Jun 13 13:10:34 ded602 postfix/master[31118]: warning: > /usr/libexec/postfix/pipe: bad command startup -- throttling > Jun 13 13:10:34 ded602 postfix/master[31118]: warning: process > /usr/libexec/postfix/pipe pid 2404 exit status 1 This is the exist status when the pipe daemon detects a bad configuration. I suspect that the pipe daemon is logging some details along the linesof: unknown flag: unknown username unknown group > Jun 13 13:10:34 ded602 postfix/qmgr[31120]: warning: private/spamassassin > socket: malformed response That is to be expected when the pipe daemon detects a configuyration problem. > [root@ded602 etc]# postconf -n Skipping that for now. > I'm not sure if all these parameters are still in use or if I even need them. > I'm seeing a lot of these, but I assume this is just a nefarious actor: > Jun 13 13:16:18 ded602 postfix/smtpd[2438]: warning: non-SMTP command from > unknown[80.244.11.148]: > \026\003\001\000\342\001\000\000\336\003\003iRf+\246d\261&]\303\034&jn/;\315\213\372\t4\005L\253\250 That's a TLS handshake. If this is on port 25 or 587 that is the client's mistake. With modern master.cf files, Postfix will log the service name for user mail user agents as postfix/submission/smtpd, postfix/smtps/smtpd, or postfix/submissions/smtpd. > Please be gentle. I'm far from a pro, and I've been out of the game for a > decade. No problem. Could you be so kind not to include a 80 kilobyte HTML attachment? Wietse _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
