On Fri, Mar 14, 2025 at 08:18:42AM +0100, Sławomir Dworaczek via Exim-users wrote: > bogo_router checks if the header already has bogosity, if not, the message > goes to the transport, there the message status X-Bogosity Spam Han or > Unsure is assigned > if Spam, it stops processing, if Ham or unsure, it continues processing, the > problem is that if the transport tags the message as Spam, it has to return > to the maildir_spam_bosity router, which has an acl list that allows it to > deliver this message to the user's mailbox, this works if, for example, I > send a message from another account, outside my domain but already tagged
Transport can't "stop processing". It could either deliver or fail. And transport can't "return to router": if it fails, mail is returned to queue for next delivery attempt. You should reconsider the logic of your workflow, using those properties of programmatic objects (routers and transports), which are available. Say, on step N1 do a classification, marking mail as ham/spam/unsure via X-Bogosity header (or something else). On steps N2, N3 and N4 check for spam/ham/unsure marks and route mail to appropriate transports. -- Eugene Berdnikov -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
