The relay link service judges relayed inbound mail with the settings that were in force when the link to the relay connected, not the current ones.
run_link (crates/services/src/inbuxa_relay_link.rs) builds a Server once per connection attempt, and Server holds a snapshot of the core (core: inner.shared_core.load_full()). session() hands that same Server to the Taker, and every relayed message goes through Job.server into ingest_relayed. A link stays up for hours or days, so a full reload after a registry write swaps the shared core while relayed mail keeps going through the old one.
Effect: anything a reload applies is ignored for mail arriving through a relay until the link reconnects (restart, relay turned off/on, a move, a new link CA): a domain's directory and its mailbox filter, RCPT/DATA stage rules, spam filter settings, sender authentication, and so on. Mail arriving directly on port 25 uses the new settings at once, so the two paths disagree.
Reported on the forum (t/259): an LDAP mailbox filter was fixed, direct mail followed it, relayed mail kept getting 550 until the server was restarted.
Not affected: the relay's recipient set (rebuilt from the store every sync), outbound sending (Sending::up keeps inner).
Fix: build a fresh Server from inner for each relayed message (and refresh the session's Server on each loop pass, so sync/events/follow also see current settings).
Acceptance: with a link up, a setting changed through the registry applies to the next relayed message without the link reconnecting; covered by a relay integration test.
The relay link service judges relayed inbound mail with the settings that were in force when the link to the relay connected, not the current ones.
`run_link` (crates/services/src/inbuxa_relay_link.rs) builds a `Server` once per connection attempt, and `Server` holds a snapshot of the core (`core: inner.shared_core.load_full()`). `session()` hands that same `Server` to the `Taker`, and every relayed message goes through `Job.server` into `ingest_relayed`. A link stays up for hours or days, so a full reload after a registry write swaps the shared core while relayed mail keeps going through the old one.
**Effect:** anything a reload applies is ignored for mail arriving through a relay until the link reconnects (restart, relay turned off/on, a move, a new link CA): a domain's directory and its mailbox filter, RCPT/DATA stage rules, spam filter settings, sender authentication, and so on. Mail arriving directly on port 25 uses the new settings at once, so the two paths disagree.
Reported on the forum (t/259): an LDAP mailbox filter was fixed, direct mail followed it, relayed mail kept getting 550 until the server was restarted.
**Not affected:** the relay's recipient set (rebuilt from the store every sync), outbound sending (`Sending::up` keeps `inner`).
**Fix:** build a fresh `Server` from `inner` for each relayed message (and refresh the session's `Server` on each loop pass, so sync/events/follow also see current settings).
**Acceptance:** with a link up, a setting changed through the registry applies to the next relayed message without the link reconnecting; covered by a relay integration test.
Fixed by #367 (merged, 983f3783), ships in the next 27.1 RC. Each relayed message is now judged with a Server built from the shared core when it is taken, and the link loop refreshes its Server every pass, so a reload reaches relayed mail without the link reconnecting. relay_link_tests covers it (maxReceivedHeaders changed with the link up: 450 4.4.6, then delivered once set back). Until the release: restart after changing settings that affect inbound mail.
Fixed by #367 (merged, 983f3783), ships in the next 27.1 RC. Each relayed message is now judged with a Server built from the shared core when it is taken, and the link loop refreshes its Server every pass, so a reload reaches relayed mail without the link reconnecting. relay_link_tests covers it (maxReceivedHeaders changed with the link up: 450 4.4.6, then delivered once set back). Until the release: restart after changing settings that affect inbound mail.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The relay link service judges relayed inbound mail with the settings that were in force when the link to the relay connected, not the current ones.
run_link(crates/services/src/inbuxa_relay_link.rs) builds aServeronce per connection attempt, andServerholds a snapshot of the core (core: inner.shared_core.load_full()).session()hands that sameServerto theTaker, and every relayed message goes throughJob.serverintoingest_relayed. A link stays up for hours or days, so a full reload after a registry write swaps the shared core while relayed mail keeps going through the old one.Effect: anything a reload applies is ignored for mail arriving through a relay until the link reconnects (restart, relay turned off/on, a move, a new link CA): a domain's directory and its mailbox filter, RCPT/DATA stage rules, spam filter settings, sender authentication, and so on. Mail arriving directly on port 25 uses the new settings at once, so the two paths disagree.
Reported on the forum (t/259): an LDAP mailbox filter was fixed, direct mail followed it, relayed mail kept getting 550 until the server was restarted.
Not affected: the relay's recipient set (rebuilt from the store every sync), outbound sending (
Sending::upkeepsinner).Fix: build a fresh
Serverfrominnerfor each relayed message (and refresh the session'sServeron each loop pass, so sync/events/follow also see current settings).Acceptance: with a link up, a setting changed through the registry applies to the next relayed message without the link reconnecting; covered by a relay integration test.
Fixed by #367 (merged,
983f3783), ships in the next 27.1 RC. Each relayed message is now judged with a Server built from the shared core when it is taken, and the link loop refreshes its Server every pass, so a reload reaches relayed mail without the link reconnecting. relay_link_tests covers it (maxReceivedHeaders changed with the link up: 450 4.4.6, then delivered once set back). Until the release: restart after changing settings that affect inbound mail.