what is 'originating' flag ?

Hi,

The term  'originating' flag comes up quite often when I am
searching
to exclude some mails (from particular ip, SMTP AUTH and
localhost)
from scanning.  But I could not find any docs specifying
what it is.
Any pointers to docs will be helpful here. Also links to any
docs on
policy maps.

Thanks,

raj

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

On 1/16/08, Rajkrishna S wrote:
> Hi,
>
> The term  'originating' flag comes up quite often when
I am searching
> to exclude some mails (from particular ip, SMTP AUTH
and localhost)
> from scanning.  But I could not find any docs
specifying what it is.
> Any pointers to docs will be helpful here.
>

search:

http://www.ijs.si/software/amavisd/release-notes.txt
for:
policy banks now contain a new key 'originating'

Appears to me (could be wrong) some routines need to know
whether
a message originates from us (client is in our network,
client is
authenticated, etc.) and once this state is known (or once
it is set),
it's more efficient to store this info in a single boolean
variable than
it is to calulate this state each time it's needed. Plus,
having the
state in a single variable makes it easy to manipulate.

> Also links to any docs on policy maps.

http://www.ijs.si/software/amavisd/amavisd-new-do
cs.html#pbanks

htt
p://www200.pair.com/mecham/spam/bypassing.html

> Thanks,
>
> raj
>

Gary V

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Gary V write,

> On 1/16/08, Rajkrishna S wrote:
> > The term  'originating' flag comes up quite often
when I am searching
> > to exclude some mails (from particular ip, SMTP
AUTH and localhost)
> > from scanning.  But I could not find any docs
specifying what it is.
> > Any pointers to docs will be helpful here.
>
> search:
> 
http://www.ijs.si/software/amavisd/release-notes.txt
> for: policy banks now contain a new key 'originating'

Right.

> Appears to me (could be wrong) some routines need to
know whether
> a message originates from us (client is in our network,
client is
> authenticated, etc.) and once this state is known (or
once it is set),
> it's more efficient to store this info in a single
boolean variable than
> it is to calulate this state each time it's needed.
Plus, having the
> state in a single variable makes it easy to
manipulate.

Yes, sort of. It is not a matter of efficiency, but setting
the
state of the originating flag is the only way that amavisd
can be
told whether a message was submitted from our users (from
internal
networks or by authenticated roaming users), as opposed to
all other mail.

  Mark

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

On 1/17/08, Mark Martinec wrote:
>
> > Appears to me (could be wrong) some routines need
to know whether
> > a message originates from us (client is in our
network, client is
> > authenticated, etc.) and once this state is known
(or once it is set),
> > it's more efficient to store this info in a single
boolean variable than
> > it is to calulate this state each time it's
needed. Plus, having the
> > state in a single variable makes it easy to
manipulate.
>
> Yes, sort of. It is not a matter of efficiency, but
setting the
> state of the originating flag is the only way that
amavisd can be
> told whether a message was submitted from our users
(from internal
> networks or by authenticated roaming users), as opposed
to all other mail.
>
>  Mark
>

Ah, Ok. Currently no reliable way for amavisd-new to know
when a
client has authenticated via the MTA, so in this case (for
example)
originating must be explicitly set (via a policy bank).

The default for mynetworks lists private address space, so
can I
assume that if this is not changed, and only the default
policy bank
is loaded, that $originating is true for private addresses?
Or is it
required to create a MYNETS policy bank (even an empty one)
so
$originating is true for addresses in mynetworks?

-- 
Gary V

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Gary,

> Ah, Ok. Currently no reliable way for amavisd-new to
know when a
> client has authenticated via the MTA, so in this case
(for example)
> originating must be explicitly set (via a policy
bank).

Exactly.

> The default for mynetworks lists private address space, so
can I
> assume that if this is not changed, and only the
default policy bank
> is loaded, that $originating is true for private
addresses?

Yes.

(yes for mail coming from these IP addresses; this
information
is passed from Postfix to amavisd with a XFORWARD smtp
command,
or from an AM.PDP milter through attribute
'client_address')

> Or is it required to create a MYNETS policy bank (even
an empty one) so
> $originating is true for addresses in mynetworks?

No, it is not required (but doesn't hurt).
For the purpose of backwards compatibility, it suffices
that
IP address is found in mynetworks_maps - as documented in
the RELEASE_NOTES:

  It is a boolean variable,
  turned on automatically in the currently loaded policy
bank when a
  smtp client's IP address matches mynetworks_maps, to retain
full
  compatibility with existing setups.


Mark

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

On Jan 17, 2008 9:05 PM, Gary V <mr88talentgmail.com> wrote:
> search:
> 
http://www.ijs.si/software/amavisd/release-notes.txt
> for:
> policy banks now contain a new key 'originating'

Thanks a lot!

raj

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/