senderscore allowlist
Hi, i'm using an up-to-date OpenBSD 6.9. OpenSMTPD seems to be up-to-date too : antispam# ls -alF /usr/local/libexec/smtpd/filter-senderscore -rwxr-xr-x 1 root bin 3014449 Apr 19 21:29 /usr/local/libexec/smtpd/filter-senderscore* antispam# sha256 /usr/local/libexec/smtpd/filter-senderscore SHA256 (/usr/local/libexec/smtpd/filter-senderscore) = 88494be1ffdabdae70c623b4049375d4aefffbba696ef255eb691606d8692734 However, the whitelist option seems to be unrecognized. Jul 30 10:18:54 antispam smtpd[7840]: info: OpenSMTPD 6.9.0 starting Jul 30 10:18:54 antispam smtpd[24374]: prepend: 2021/07/30 10:18:54 filter-prepend registered with [*EXT*] Jul 30 10:18:54 antispam smtpd[24374]: senderscore: flag provided but not defined: -whitelist Jul 30 10:18:54 antispam smtpd[24374]: senderscore: Usage of /usr/local/libexec/smtpd/filter-senderscore: Jul 30 10:18:54 antispam smtpd[24374]: senderscore: -blockBelow int Jul 30 10:18:54 antispam smtpd[24374]: senderscore: score below which session is blocked (default -1) Jul 30 10:18:54 antispam smtpd[24374]: senderscore: -blockPhase string Jul 30 10:18:54 antispam smtpd[24374]: senderscore: phase at which blockBelow triggers (default "connect") Jul 30 10:18:54 antispam smtpd[24374]: senderscore: -junkBelow int Jul 30 10:18:54 antispam smtpd[24374]: senderscore: score below which session is junked (default -1) Jul 30 10:18:54 antispam smtpd[24374]: senderscore: -scoreHeader Jul 30 10:18:54 antispam smtpd[24374]: senderscore: add X-SenderScore header Jul 30 10:18:54 antispam smtpd[24374]: senderscore: -slowFactor int Jul 30 10:18:54 antispam smtpd[24374]: senderscore: delay factor to apply to sessions (default -1) Jul 30 10:18:54 antispam smtpd[7]: warn: lost processor: senderscore exited abnormally Jul 30 10:18:54 antispam smtpd[7]: Exiting sysupdate and pkg_add -Uu are OK. Is there something I should do to enable this option ? Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
Re: [*EXT*] smtpd failure
Hi, Did you update the packages after the sysupgrade ? $ pkg_add -Uu Regards, -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
filter data-line session and opaque id order
Hi, According to the most recent smtp-filters(7) man page, the session id (field 6) and opaque id (field 7) are sent in the same order in the response filter-dateline as field 2 and 3 respectively. However, in OpenSMTPD 6.6, respecting the fields order make the filtering flow hanging. Session and opaque needs to be swapped in the response. Is this expected for this version and corrected in 6.7, thus the doc is up-to-date ? Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
Subject prefixing
Hi list, I'm looking for an easy way to add a static prefix "[*EXT*]" to all incoming emails, as long as the subject does not already contains this string. OpenSMTPD is running as a filtering MX running senderscore filter. default action is relay to another host. Can OpenSMTPD modify the header conditionally ? If so, should I add a filter to the existing "listen" line or should I add a new "listen" line with a dedicated filter and chaining listen->action relay to local listen->action relay to external ? Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
