Yes, router based is what I was looking at.  Here is a rundown of what I am
trying to do.  Let me say that there are NO local users on the machine at
all.  It is just for processing mail in, scan for spam, process some SPF
stuff etc. and then back out for delivery.

When a message comes in, I am using acl_smtp_data to check messages for
spam.  The spam checker has no idea who the user is, just gives its opinion
of the spam content.

We do not reject spam in the ACL, we accept all of it.

We store the spam score and recipients to a variable in the ACL so the info
can be referenced later.

Then we drop down into the routers, where we do stuff with SPF, user
aliases, domain aliases etc.  One of the routers deals with catch-all, if
the domain uses catch-all direct all unknown recipients to the catch-all
address.

Then the next router is deciding if the spam should be placed in
quarantine.  What was the spam score, what is the user preference etc.  One
of the conditions is if the message is a catch-all message or not, if it is
a catch-all message there is no spam quarantine.

So the decision of the catch-all router is what we are trying to gain
access to.  What action is the catch-all  router doing and can we act on it
in our quarantine router.

May have to keep digging on this, move the quarantine function to transport
or something... if anyone has a bright idea please let me know.


Rob

On Fri, Aug 11, 2017 at 3:58 PM, Heiko Schlittermann via Exim-users <
exim-users@exim.org> wrote:

> Rob Gunther via Exim-users <exim-users@exim.org> (Fr 11 Aug 2017 08:49:30
> CEST):
> > My assumption was correct, I found this blurb in the documentation
> > <http://www.exim.org/exim-html-current/doc/html/spec_
> html/ch-generic_options_for_routers.html>
> > on
> > routers.
> >
> > *New header lines are not actually added until the message is in the
> > process of being transported. This means that references to header lines
> in
> > string expansions in the transport’s configuration do not “see” the added
> > header lines. *
>
> That talks about header lines added in transports. What is mentioned
> about header lines added in routers? (I'm not sure..)
> >
> > So back to my original question...  What can I do in a router that I can
> > then read as a condition of another router?
>
> You can try setting address_data.
>
> (And I revoke my question about the subsequent routers, as the first one
> was a redirect router…)
>
>     Best regards from Dresden/Germany
>     Viele Grüße aus Dresden
>     Heiko Schlittermann
> --
>  SCHLITTERMANN.de ---------------------------- internet & unix support -
>  Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
>  gnupg encrypted messages are welcome --------------- key ID: F69376CE -
>  ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to