@BahnhofAB Hur kan ni slå er på bröstet, när ni inte har er support öppen under tiden, kunderna normalt nyttjar er "tjänster"? 🤔💩
(kom inte att påstå någon AI hanterar det tillfredsställande)
@PoolpOrg
Trace (rules) with #OpenSMTPD only working on one of six servers (#OpenBSD 7.5)!?
smtpctl log verbose
smtpctl trace rules
But if I run in foreground like below, it works (on all)!?
smtpd -dv -T rules
And smtpctl not allowing any shorts for any subsystem for trace
Failed to upgrade my #OpenBSD home fw this night!
They missed to document dhcp syntax change in the upgrade guide! 7.0 needs "inet autoconf" instead of "dhcp" in your hostname.if. Lucky that the machine was local...
#OpenBSD@PoolpOrg
If #OpenSMTPD had more tag-functionality like pf.conf, it would be nirvana!
action A forward-only alias <z> tag T # "z-alias" a: [email protected]
match for domain "sub.dom.xx" action A
match tagged T for domain "dom.xx" action B
Without needing expose dom.xx
@PoolpOrg Ok thanks!
So 6.6 maybe get some new match parameters?
Following worked: match from local for domain [...]
But I think you should consider more functionality with tags anyways ...
@PoolpOrg If you don't want to accept incoming mails to a domain you want to forward to through aliases, how do you do then?
If it was possible to "tag" in actions and/or matches, then it would be solveable.
@PoolpOrg And I use specific machines for the alternative subdomain (with less filters then the ordinary servers does for main domain/addresses).
Have to do this to allow example some amazan crap for specific users...
@PoolpOrg I promise, you need an extra match if you first match an action forward-only alias <z>for destination.
Where the filie/table z has something like a: [email protected] and first match is a sub-domain of other.dom.
This is an "alternative" subdomain with less filters for special cases.
#OpenSMTPD#OpenBSD@PoolpOrg
Doc hard to find, is this true?
<= 6.3
limit mta inet4
limit session max-rcpt nn
limit session max-mails nn
>= 6.4
mta limit inet4
smtp limit max-rcpt nn
smtp limit max-mails nn
@proofpoint did you release an "upgrade" yesterday or so?
Your "sw" doesn't follow MX-pointers and not doing retries as they should (again, as in march).
Maybe your devs should have some night reading (with SMTP RFC's)!
You are not @Google or @Microsoft, try to follow standards!
@VolvoCarSverige Be er "IT" att titta hur ni skickar ut e-post för "Volvo-ID"! Testa mot den vanligaste antispammotorn #SpamAssassin själva och trimma bort: LONG_HEX_URI, MIME_HTML_MOSTLY, MPART_ALT_DIFF och URIBL_GREY m.m. Använd egna SMTP-servrar (iaf inte Sendgrids).
@Forcepointsec One more "hint", check specially your SMTP servers in cluster-[abe].mailcontrol.com which not respecting MX-pointers and get trapped due to misbehavior (not retrying with greylisting servers and/or accept order to connect).
Doesn't @Forcepointsec 's product #mailcontrol respect others MX-pointer and #greylisting. They get trapped when they try to contact servers they shouldn't talk to (if they followed SMTP RFC's)! #fail
@Forcepointsec No, try to find that contact information on your site (if you are not a customer)! Maybe your "devs" could test your product against #OpenBSD's #spamd (#spam deferral daemon) with a #greytrap host (see -M option and greytrapping in https://t.co/4cw7v4I7R7).