[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Sun, 19 Nov 2006, Rob Arends wrote:

 
 Davide, let me first quote your documentation:
  
 quote
  !flags[TAB]command[TAB]arg-or-macro[TAB]...[NEWLINE]
 
 Each file may contain multiple commands, that will be executed in strictly
 sequential order. The first command that will trigger a rejection code will
 make the filtering process to end. The 'flags' parameter is a
 comma-separated list of flags that drives the filter execution. The syntax
 of each flag is either FLAG or FLAG=VAL. Currently supported flags are:
 
   aex 
   exclude filter execution in case of authenticated sender
 
   wlex 
   exclude filter execution in case the client IP is white-listed
 inside the SMTP.IPPROP.TAB file.
 /quote
  
 I have recently attempted to use a post-data filter.
 I have need to execute one program if the user *was* authenticated, and
 another when the user was *not*.
 
 I tried this in filters.post-data.tab, based on the FLAG=VAL detailed
 above.
 
 !aex=1[tab]program1.exe
 !aex=0[tab]program2.exe
 
 Hoping to achieve my goal, but I get both excluded.

aex and wlex have no VAL. There is no point in adding them as aex=0



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Sun, 19 Nov 2006, Davide Libenzi wrote:

 On Sun, 19 Nov 2006, Rob Arends wrote:
 
  
  Davide, let me first quote your documentation:
   
  quote
   !flags[TAB]command[TAB]arg-or-macro[TAB]...[NEWLINE]
  
  Each file may contain multiple commands, that will be executed in strictly
  sequential order. The first command that will trigger a rejection code will
  make the filtering process to end. The 'flags' parameter is a
  comma-separated list of flags that drives the filter execution. The syntax
  of each flag is either FLAG or FLAG=VAL. Currently supported flags are:
  
  aex 
  exclude filter execution in case of authenticated sender
  
  wlex 
  exclude filter execution in case the client IP is white-listed
  inside the SMTP.IPPROP.TAB file.
  /quote
   
  I have recently attempted to use a post-data filter.
  I have need to execute one program if the user *was* authenticated, and
  another when the user was *not*.
  
  I tried this in filters.post-data.tab, based on the FLAG=VAL detailed
  above.
  
  !aex=1[tab]program1.exe
  !aex=0[tab]program2.exe
  
  Hoping to achieve my goal, but I get both excluded.
 
 aex and wlex have no VAL. There is no point in adding them as aex=0

Ok, for consistency with the doc, now you can do the aex=0 smart thing.



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

Ok, so what does this mean:???

 The syntax of each flag is either FLAG or FLAG=VAL.

The description indicates a feature that would be more flexible.
The ability to run a filter for those that *are* auth or wlst and/or for
those that *are not* auth or wlst.

!aex[tab]program1.exe
This only allows me to run for those *not Auth* (equivalent to !aex=1  ? )


Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Monday, 20 November 2006 7:49 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


On Sun, 19 Nov 2006, Rob Arends wrote:

 
 Davide, let me first quote your documentation:
  
 quote
  !flags[TAB]command[TAB]arg-or-macro[TAB]...[NEWLINE]
 
 Each file may contain multiple commands, that will be executed in 
 strictly sequential order. The first command that will trigger a 
 rejection code will make the filtering process to end. The 'flags' 
 parameter is a comma-separated list of flags that drives the filter 
 execution. The syntax of each flag is either FLAG or FLAG=VAL. Currently
supported flags are:
 
   aex 
   exclude filter execution in case of authenticated sender
 
   wlex 
   exclude filter execution in case the client IP is white-listed
inside 
 the SMTP.IPPROP.TAB file.
 /quote
  
 I have recently attempted to use a post-data filter.
 I have need to execute one program if the user *was* authenticated, 
 and another when the user was *not*.
 
 I tried this in filters.post-data.tab, based on the FLAG=VAL 
 detailed above.
 
 !aex=1[tab]program1.exe
 !aex=0[tab]program2.exe
 
 Hoping to achieve my goal, but I get both excluded.

aex and wlex have no VAL. There is no point in adding them as aex=0



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

 Ok, for consistency with the doc, now you can do the aex=0 smart thing.

Ok, ignore crossed email

BTW, is that !aex=0  or aex=0
Does the ! indicate Flags here, or does it mean not


Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Monday, 20 November 2006 8:46 AM
To: XMail mailing list
Subject: [xmail] Re: filter aex  wlex


On Sun, 19 Nov 2006, Davide Libenzi wrote:

 On Sun, 19 Nov 2006, Rob Arends wrote:
 
  
  Davide, let me first quote your documentation:
   
  quote
   !flags[TAB]command[TAB]arg-or-macro[TAB]...[NEWLINE]
  
  Each file may contain multiple commands, that will be executed in 
  strictly sequential order. The first command that will trigger a 
  rejection code will make the filtering process to end. The 'flags' 
  parameter is a comma-separated list of flags that drives the filter 
  execution. The syntax of each flag is either FLAG or FLAG=VAL. Currently
supported flags are:
  
  aex 
  exclude filter execution in case of authenticated sender
  
  wlex 
  exclude filter execution in case the client IP is white-listed 
  inside the SMTP.IPPROP.TAB file.
  /quote
   
  I have recently attempted to use a post-data filter.
  I have need to execute one program if the user *was* authenticated, 
  and another when the user was *not*.
  
  I tried this in filters.post-data.tab, based on the FLAG=VAL 
  detailed above.
  
  !aex=1[tab]program1.exe
  !aex=0[tab]program2.exe
  
  Hoping to achieve my goal, but I get both excluded.
 
 aex and wlex have no VAL. There is no point in adding them as aex=0

Ok, for consistency with the doc, now you can do the aex=0 smart thing.



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Mon, 20 Nov 2006, Rob Arends wrote:

 
  Ok, for consistency with the doc, now you can do the aex=0 smart thing.
 
 Ok, ignore crossed email
 
 BTW, is that !aex=0  or aex=0
 Does the ! indicate Flags here, or does it mean not

It means this is not the executable path, but a flags declaration



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

Ok, thanks, so I'll test with 

!aex=1[tab]prog  - user is auth'd
!aex=0[tab]prog  - user is not auth'd


Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Monday, 20 November 2006 8:59 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


On Mon, 20 Nov 2006, Rob Arends wrote:

 
  Ok, for consistency with the doc, now you can do the aex=0 smart thing.
 
 Ok, ignore crossed email
 
 BTW, is that !aex=0  or aex=0
 Does the ! indicate Flags here, or does it mean not

It means this is not the executable path, but a flags declaration



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

Davide, The testing shows that an Auth'd user will run the first of the two
examples below,
But a non Auth'd user will run both.

Can you confirm?

Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Rob Arends
Sent: Monday, 20 November 2006 9:04 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


Ok, thanks, so I'll test with 

!aex=1[tab]prog  - user is auth'd
!aex=0[tab]prog  - user is not auth'd


Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Monday, 20 November 2006 8:59 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


On Mon, 20 Nov 2006, Rob Arends wrote:

 
  Ok, for consistency with the doc, now you can do the aex=0 smart thing.
 
 Ok, ignore crossed email
 
 BTW, is that !aex=0  or aex=0
 Does the ! indicate Flags here, or does it mean not

It means this is not the executable path, but a flags declaration



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Mon, 20 Nov 2006, Rob Arends wrote:

 
 Davide, The testing shows that an Auth'd user will run the first of the two
 examples below,
 But a non Auth'd user will run both.
 
 Can you confirm?

Yes I can.


- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Mike Harrington

In the example:

!aex=1[tab]prog  - user is auth'd
!aex=0[tab]prog  - user is not auth'd

I thought it stated that an auth'd user will NOT run the first of the two, 
and a non-authed user would run both?  Am I missing something?

- Original Message - 
From: Davide Libenzi davidel@xmailserver.org
To: xmail@xmailserver.org
Sent: Sunday, November 19, 2006 3:29 PM
Subject: [xmail] Re: filter aex  wlex



 On Mon, 20 Nov 2006, Rob Arends wrote:


 Davide, The testing shows that an Auth'd user will run the first of the 
 two
 examples below,
 But a non Auth'd user will run both.

 Can you confirm?

 Yes I can.


 - Davide


 -
 To unsubscribe from this list: send the line unsubscribe xmail in
 the body of a message to [EMAIL PROTECTED]
 For general help: send the line help in the body of a message to
 [EMAIL PROTECTED]

 

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Sun, 19 Nov 2006, Mike Harrington wrote:

 In the example:
 
 !aex=1[tab]prog  - user is auth'd
 !aex=0[tab]prog  - user is not auth'd
 
 I thought it stated that an auth'd user will NOT run the first of the two, 
 and a non-authed user would run both?  Am I missing something?

Correct. The second format is brain-demaged and parsed only to comply to 
the VAR=VAL filter flag generic rule.



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Mike Harrington

Then what was this about:


 Davide, The testing shows that an Auth'd user will run the first of the 
 two
 examples below,
 But a non Auth'd user will run both.

 Can you confirm?

 Yes I can.

isn't that opposite?

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

Davide, It's nice that you can confirm. !!??

I'm confused with the meaning of your response.
Let me reword:

In a post-data filter I have the following:

!aex=0[tab]D:\prog_for_non_auth_user.exe
!aex=1[tab]D:\prog_for_auth_user.exe

In the above filter configuration, only ONE of the two programs would run
for any given email, because aex has only two states [0|1].

The whole reason for !aex=0 was that a filter would run *only* if the user
was *not* auth'd.

My Filter logs are showing:
Message1:
[EMAIL PROTECTED] [EMAIL PROTECTED] 10.90.10.152 211.29.132.195 
2006-11-20
10:57:01 post-data  0 0 D:\prog_for_non_auth_user.exe;
[EMAIL PROTECTED] [EMAIL PROTECTED] 10.90.10.152 211.29.132.195 
2006-11-20
10:57:02 post-data  0 0 D:\prog_for_auth_user.exe;

Message2:
[EMAIL PROTECTED] [EMAIL PROTECTED] 10.90.10.152 10.90.10.100 
2006-11-20
10:40:10 post-data  0 0 D:\prog_for_non_auth_user.exe;
[EMAIL PROTECTED] [EMAIL PROTECTED] 10.90.10.152 10.90.10.100 
2006-11-20
10:40:10 post-data EXCL -1 -1 D:\prog_for_auth_user.exe;

I expected to see Message1 with the first log entry with an EXCL.

Thanks,
Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Monday, 20 November 2006 10:29 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


On Mon, 20 Nov 2006, Rob Arends wrote:

 
 Davide, The testing shows that an Auth'd user will run the first of 
 the two examples below, But a non Auth'd user will run both.
 
 Can you confirm?

Yes I can.


- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in the body
of a message to [EMAIL PROTECTED] For general help: send the line
help in the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Sun, 19 Nov 2006, Mike Harrington wrote:

 
 Then what was this about:
 
 
  Davide, The testing shows that an Auth'd user will run the first of the 
  two
  examples below,
  But a non Auth'd user will run both.
 
  Can you confirm?
 
  Yes I can.
 
 isn't that opposite?

G ...

!aex=0  - Filter is always run - brain-demaged format
!aex- Filter is NOT run if the user authenticated
!aex=1  - Filter is NOT run if the user authenticated




- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Davide Libenzi

On Mon, 20 Nov 2006, Rob Arends wrote:

 
 Davide, It's nice that you can confirm. !!??
 
 I'm confused with the meaning of your response.
 Let me reword:
 
 In a post-data filter I have the following:
 
 !aex=0[tab]D:\prog_for_non_auth_user.exe
 !aex=1[tab]D:\prog_for_auth_user.exe
 
 In the above filter configuration, only ONE of the two programs would run
 for any given email, because aex has only two states [0|1].
 
 The whole reason for !aex=0 was that a filter would run *only* if the user
 was *not* auth'd.

No, such concept does not exist. Stop.



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Mike Harrington

Yes you can, you just can't use the logic to run a program only on 
AUTHETNICATED mail.

- Original Message - 
From: Rob Arends [EMAIL PROTECTED]
To: xmail@xmailserver.org
Sent: Sunday, November 19, 2006 4:46 PM
Subject: [xmail] Re: filter aex  wlex



 Hmm,  In that case, it would have been easier to remove the FLAG=VAL part 
 of
 the Doco, as so far not additional functionality was produced.

 I suppose that the meaning of aex is Auth user EXcluded. (true or 
 false)
 == if true then don't run this filter.
 Perhaps what I'm looking for is auth, where it has state (or value) of
 [0|1].

 Then it might mean more, when you say == if true then run this filter.

 It just means that currently I cannot use the logic to run a program only 
 on
 un-auth'd mail.

 Rob :-)

 _
 Note To Self: Remember to put something witty here later...


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 On
 Behalf Of Davide Libenzi
 Sent: Monday, 20 November 2006 11:35 AM
 To: xmail@xmailserver.org
 Subject: [xmail] Re: filter aex  wlex


 On Sun, 19 Nov 2006, Mike Harrington wrote:

 In the example:

 !aex=1[tab]prog  - user is auth'd
 !aex=0[tab]prog  - user is not auth'd

 I thought it stated that an auth'd user will NOT run the first of the
 two, and a non-authed user would run both?  Am I missing something?

 Correct. The second format is brain-demaged and parsed only to comply to 
 the
 VAR=VAL filter flag generic rule.



 - Davide


 -
 To unsubscribe from this list: send the line unsubscribe xmail in
 the body of a message to [EMAIL PROTECTED]
 For general help: send the line help in the body of a message to
 [EMAIL PROTECTED]


 -
 To unsubscribe from this list: send the line unsubscribe xmail in
 the body of a message to [EMAIL PROTECTED]
 For general help: send the line help in the body of a message to
 [EMAIL PROTECTED]

 

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: filter aex wlex

2006-11-19 Thread Rob Arends

Yes I had come to that conclusion - I am now testing @@USERAUTH=- in a
wrapper.


Rob :-)
 
_
Note To Self: Remember to put something witty here later...
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Harrington
Sent: Monday, 20 November 2006 11:51 AM
To: xmail@xmailserver.org
Subject: [xmail] Re: filter aex  wlex


Yes you can, you just can't use the logic to run a program only on
AUTHETNICATED mail.


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]