-
-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smtp_forward: tighten up queue.wants routing #3199
Conversation
#### Fixed - feat(q_forward): add LMTP routing handling #3199 - chore(q_forward): tighten up queue.wants handling #3199 - doc(q_forward): improve markdown formatting #3199 - helo.checks: several fixes, #3191 - q/smtp_forward: correct path to next_hop #3186 - don't leak addr parsing errors into SMTP conversation #3185 - connection: handle dns.reverse invalid throws on node v20 #3184 - rename redis command setex to setEx #3181 #### Changed - test(helo.checks): add regression tests for #3191 #3195 - connection: handle dns.reverse invalid throws on node v20 - build(deps): bump ipaddr.js from 2.0.1 to 2.1.0 #3194 - chore: bump a few dependency versions #3184 - dns_list_base: avoid test failure when public DNS used #3184 - doc(outbound.ini) update link #3159 - doc(clamd.md) fixed spelling error #3155
@msimerson this change causes a regression in our tests. the 61126ab#diff-358fdbf915639f898db16fb2bab56c2284331a4e8bfe65e25fe3b0f1f13bdcfeR33 |
To add some more info, the way we configure the forwad plugin is:
With the above config, emails from |
Well yes. Sorry. The That's what I was thinking. But I missed something important: that disables the ability to have [outbound] forward MX routing disabled in the main config and enabled per-domain. And vise versa. #3204 does the needful, but it needs to have a test added so prevent future regressions. smtp_forward is used in quite a few ways (I also [ab]use it to deliver via LMTP using outbound). |
Yes, indeed, this is exactly how we were using it. I see you already reverted that part of the code, thanks! I will test and get back. |
Can confirm your revert fixed the issue (for us). |
Changes proposed in this pull request:
Checklist: