The scan list rule seems to be executing.  It's just not finding equality in the list.  I deleted everything and started over.  Made a new list. added emails to it from the messages in the new mail folder.  It works the same as it did before. 

 I know it is doing something because when I use the rule:

List scan  NOT  @LIST3970.PML   Set color to red   

it sets the message color to red for all unread messages in the new mail folder.  That means it is not finding the addresses in the Dlist, but they are definitely in there (no aliases).  It also means the rule is getting fired.

I give up.  Thanks for your help.

 David

I have several filter rules set up to distribute new mail into various folders. I also have multiple POP3 accounts that feed this PM, but the rules are applied in an "all_mail" identity which handles all incoming mail. The rules are set up in order so there are many "if FROM abc@mailaddress.com, move to folder ...". They are followed by multiple "if TO abc@mailaddress.com, move to folder ...". One of the "from" rules is defined as a "member of list" search but it doesn't seem to work. I received several e-mails from members of that list but the e-mails end up in a folder I set up as a catch-all "inbox" if the TO address contains my primary e-mail address. In other words, the filtering seems to ignore the "member of list" filter and successfully applies the catch-all "TO" filter. Is there a specific order in which the filter rules are applied that would cause it to ignore the member search? I'm a relative newbie to PM, but I understand the filtering concept. I know this is a very generic example, but does anyone have any suggestions on what I might be doing wrong?   

Add'l info:

I've tried setting up distribution list filtering for both open and close of the new mail folder.I moved a mail from the inbox to new mail and unread it. Mail was definitely from a member of the scan list. After the new mail folder was opened,the mail got moved to Inbox folder. If scan list had been invoked, mail would have been moved to a different folder.

System message says:

Mon, 18:51:40    Newmail rule processing: No messages triggered any rules.
Mon, 18:52:23    Newmail rule processing:
    1 message moved to 'Inbox'

Can someone help?

[quote user="bhenry004"]

I have several filter rules set up to distribute new mail into various folders. I also have multiple POP3 accounts that feed this PM, but the rules are applied in an "all_mail" identity which handles all incoming mail. The rules are set up in order so there are many "if FROM abc@mailaddress.com, move to folder ...". They are followed by multiple "if TO abc@mailaddress.com, move to folder ...". One of the "from" rules is defined as a "member of list" search but it doesn't seem to work. I received several e-mails from members of that list but the e-mails end up in a folder I set up as a catch-all "inbox" if the TO address contains my primary e-mail address. In other words, the filtering seems to ignore the "member of list" filter and successfully applies the catch-all "TO" filter. Is there a specific order in which the filter rules are applied that would cause it to ignore the member search? I'm a relative newbie to PM, but I understand the filtering concept. I know this is a very generic example, but does anyone have any suggestions on what I might be doing wrong?   

Add'l info:

I've tried setting up distribution list filtering for both open and close of the new mail folder.I moved a mail from the inbox to new mail and unread it. Mail was definitely from a member of the scan list. After the new mail folder was opened,the mail got moved to Inbox folder. If scan list had been invoked, mail would have been moved to a different folder.

System message says:

Mon, 18:51:40    Newmail rule processing: No messages triggered any rules.
Mon, 18:52:23    Newmail rule processing:
    1 message moved to 'Inbox'

Can someone help?[/quote]

Can you check the raw detail of the "From:" header on a mail that should be caught by the scan list filter - does it contain "?" symbols signifying an encoded name?

The raw detail in any of the FROM: headers do not contain any "?" symbols.

Here's more information. I hope it makes sense. (Email addresses shown below have been changed to protect owners but are correct in my PM address book/lists.)

Snipit of entries in my filtering rules, in the order they appear (rules are applied when new mail folder is opened):

...

Headers      F R contains Victoria Dillon     Move to 'SVE Tennis'

...

List scan    @SVE_Friends.PML                Move to 'SVE Friends'

...

Headers       CT contains bhenrynnn@rochester.rr.com     Move to 'Inbox'

(End of Rules)

Snipit of "SVE_Friends" distribution list (all entries in my address book contain the correct email address for these names):

...

Dave & Carol Lawson                            (address book entry contains weezer-nnnn@mchsi.com)

...

Fred Gross                                           (address book entry contains fredjnnn@gmail.com)

...

...

(End of list)

Raw FROM: addresses from the Emails I have received that have not been sent to the correct folder: (again, addresses have been changed for protection)

From: weezer-nnnn@mchsi.com                     (this email was sent to 'Inbox but should have been sent to 'SVE Friends' according to list scan filter rule)

From: Fred Gross <fredjnnn@gmail.com>        (this email was sent to 'Inbox' but should have been sent to 'SVE Friends' according to list scan filter rule)

From: Victoria Dillon <vikdillonx@yahoo.com>  (this email was correctly sent to 'SVE Tennis' because a "from" rule was detected before the scan filter rule)

(End)

As best I can tell, all the individual rules in my filter list are working correctly. Just the Scan list rule is being ignored.

Any help is appreciated.

[quote user="bhenry004"]

The raw detail in any of the FROM: headers do not contain any "?" symbols.

Here's more information. I hope it makes sense. (Email addresses shown below have been changed to protect owners but are correct in my PM address book/lists.)

Snipit of entries in my filtering rules, in the order they appear (rules are applied when new mail folder is opened):

...

Headers      F R contains Victoria Dillon     Move to 'SVE Tennis'

...

List scan    @SVE_Friends.PML                Move to 'SVE Friends'

...

Headers       CT contains bhenrynnn@rochester.rr.com     Move to 'Inbox'

(End of Rules)[/quote]

Do you send messages out to this Distribution list?  Check that it isn't corrupted in any way or have strange characters as that can cause problems.

[quote]Snipit of "SVE_Friends" distribution list (all entries in my address book contain the correct email address for these names):
...

Dave & Carol Lawson                            (address book entry contains weezer-nnnn@mchsi.com)

...

Fred Gross                                           (address book entry contains fredjnnn@gmail.com)

...

...

(End of list)[/quote]

OK, I've never done it this way - please test if including just the actual address in the Distribution list results in the filter working.

[quote]Raw FROM: addresses from the Emails I have received that have not been sent to the correct folder: (again, addresses have been changed for protection)

From: weezer-nnnn@mchsi.com                     (this email was sent to 'Inbox but should have been sent to 'SVE Friends' according to list scan filter rule)

From: Fred Gross <fredjnnn@gmail.com>        (this email was sent to 'Inbox' but should have been sent to 'SVE Friends' according to list scan filter rule)

From: Victoria Dillon <vikdillonx@yahoo.com>  (this email was correctly sent to 'SVE Tennis' because a "from" rule was detected before the scan filter rule)

(End)

As best I can tell, all the individual rules in my filter list are working correctly. Just the Scan list rule is being ignored.

Any help is appreciated. [/quote]

I did send mail out to this list. There were a couple rejections due to "Syntax Errors". I double checked the list and found some misspelled entries and corrected them.

As for special characters, there are several "&" in the alias names (e.g. Dick & Jane Smith). I wouldn't think that should cause a problem, but who knows. 

I did some further testing with a folder of 4 emails, all of which should trigger a rule to change the messages a different color. 

Dist List1 - combination of real addresses and alias names. Results: The emails matching the real addresses in the list were changed, the alias emails were not changed.

Dist List2 - only real address entries in the list. Results: All emails were matched and colors were changed.

Dist List3 - only alias entries in the list. Results: No emails were matched and colors were not changed.

Final conclusion: If the distribution list contains real addresses, a "scan list" rule will work on matched emails. It will NOT work with alias names.

The real problem: The PMAIL help documentation says a "scan list" will work with either an alias name or an address. That is not true. Even more confusing, when building a distribution list by selecting the entries from an address book, the alias name is what is stored. That would lead a user to believe that the alias name can be used in a scan list rule. I find no place in the help doc that says a "scan list" must use a distribution list with real addresses. Can this anomaly be fixed?

[quote user="bhenry004"]

I did send mail out to this list. There were a couple rejections due to "Syntax Errors". I double checked the list and found some misspelled entries and corrected them.

As for special characters, there are several "&" in the alias names (e.g. Dick & Jane Smith). I wouldn't think that should cause a problem, but who knows. 

I did some further testing with a folder of 4 emails, all of which should trigger a rule to change the messages a different color. 

Dist List1 - combination of real addresses and alias names. Results: The emails matching the real addresses in the list were changed, the alias emails were not changed.

Dist List2 - only real address entries in the list. Results: All emails were matched and colors were changed.

Dist List3 - only alias entries in the list. Results: No emails were matched and colors were not changed.

Final conclusion: If the distribution list contains real addresses, a "scan list" rule will work on matched emails. It will NOT work with alias names.

The real problem: The PMAIL help documentation says a "scan list" will work with either an alias name or an address. That is not true. Even more confusing, when building a distribution list by selecting the entries from an address book, the alias name is what is stored. That would lead a user to believe that the alias name can be used in a scan list rule. I find no place in the help doc that says a "scan list" must use a distribution list with real addresses. Can this anomaly be fixed?[/quote]

OK, I've now seen the parallel query you had ongoing in another thread - http://community.pmail.com/forums/thread/5116.aspx

It seems it was stated quite clearly back in 2007 that aliases don't work in filter scan lists - did you read that?

[quote user="bhenry004"]The real problem: The PMAIL help documentation says a "scan list" will work with either an alias name or an address. That is not true. Even more confusing, when building a distribution list by selecting the entries from an address book, the alias name is what is stored. That would lead a user to believe that the alias name can be used in a scan list rule. I find no place in the help doc that says a "scan list" must use a distribution list with real addresses. Can this anomaly be fixed? [/quote]

This will help:  Addressbook properties > Apply the e-mail address instead of the alias

Brian,

Thank you. That will be helpful in recreating my alias name dist lists with real addresses and ultimately use them in scan list rules. I don't know the maintenance policies for PM. Are updates done to the software periodically?

A version 5 is in the works.  The latest news from the developer can be found here.  http://www.pmail.com/devnews.htm

[quote user="bfluet"]

[quote user="bhenry004"]The real problem: The PMAIL help documentation says a "scan list" will work with either an alias name or an address. That is not true. Even more confusing, when building a distribution list by selecting the entries from an address book, the alias name is what is stored. That would lead a user to believe that the alias name can be used in a scan list rule. I find no place in the help doc that says a "scan list" must use a distribution list with real addresses. Can this anomaly be fixed? [/quote]

This will help:  Addressbook properties > Apply the e-mail address instead of the alias[/quote]

Will it?  This is from the Help:

Apply the e-mail address instead of the alias If you check this control, then Pegasus Mail will insert the e-mail address from the selected addressbook entries when you use them to create a new mail message. In the default state, with the control unchecked, Pegasus Mail will insert the "Name" field of the entry as an alias.

I'm surprised you don't think the setting change will be helpful.  In your related post you expressed frustration in this statement: "Even more confusing, when building a distribution list by selecting the

entries from an address book, the alias name is what is stored.".  The alias is what is stored because you have it configured that way.   Change the setting and this little frustration is gone.  It doesn't fix existing entries but should help in future use.

[quote user="bfluet"]

I'm surprised you don't think the setting change will be helpful.  In your related post you expressed frustration in this statement: "Even more confusing, when building a distribution list by selecting the entries from an address book, the alias name is what is stored.".  The alias is what is stored because you have it configured that way.   Change the setting and this little frustration is gone.  It doesn't fix existing entries but should help in future use.[/quote]

That quote wasn't me, that was the OP (bhenry).  I don't think that setting affects the building of distribution lists from an addressbook as the docs say it only affects creating new messages.

There are a couple of things I'm missing here:

1. I've tried building a distribution list from an addressbook using the standard addressing centre and every time it puts in the email address and not an alias.  How can you get it to behave otherwise?

2. Where does it say in the Help documentation that 'a "scan list" will work with either an alias name or an address' ?  I couldn't find that.

Sorry Paul.  I lost track of who posted what. 

To answer your question, you can control whether the alias or the email address gets added from an addressbook.  It's the "Apply the e-mail address instead of the alias" setting located in addressbook properties.

I have not seen anything in the help files or the manual that states that aliases will work in a scan list.  I can understand the OPs confusion though.  Aliases work in distribution lists but it is not stated anywhere that aliases will fail when that same dlist is used as a scan list.

[quote user="bfluet"]To answer your question, you can control whether the alias or the email address gets added from an addressbook.  It's the "Apply the e-mail address instead of the alias" setting located in addressbook properties.[/quote]

Strange, but that checkbox makes no difference for me when adding entries into a distribution list - I always get the address.  Do you get aliases added?

[quote user="PaulW"][quote user="bfluet"]To answer your question, you can control whether the alias or the email address gets added from an addressbook.  It's the "Apply the e-mail address instead of the alias" setting located in addressbook properties.[/quote]

Strange, but that checkbox makes no difference for me when adding entries into a distribution list - I always get the address.  Do you get aliases added?[/quote]

Yes.  With the 'Addressbook and distribution lists' window open I can enable that setting and then add an addressbook contact to a dlist and it will be the email address.  I can then disable it and add the same contact and it adds the alias.  I have tested on two Pegasus Mail installs. 

That setting is available as either addressbook specific or global so be sure you are paying attention to that.

Paul,

I see that you and Brian have been discussing the "distribution list" issue and agree that it is a bit confusing. I would just like to justify my statement about the Help documentation. Before I originally posted this, I read a lot of the help documentation about distribution lists, filtering, etc. I just went back and tried to find a direct quote that would support my statement. I couldn't find any phrase that did. What I found was this in the discussion of "Creating a distribution list":

"To add addresses to your distribution list click in the address list area and either type in the addresses or select them from address books or the local user list. Make sure that you have only one address per line in the list. Any valid address  can be entered in the list, including addressbook aliases."

Using that in conjunction with this statement in the discussion of "Filtering messages based on list membership": "With this type of filtering rule, the rule will trigger if the sender's e-mail address can be located in a Pegasus Mail distribution list. When you create the rule, simply select the distribution list Pegasus Mail should search, and it will do the rest.".

Looking at the statements again, I may have over estimated the ability of Pegasus. The filtering help text specifically states "e-mail address" so if one goes by the letter of the law, an alias would not be included in the scope of that search even though the "distribution list" text states that an alias is a valid entry in a distribution list.

Again, I may have incorrectly interpreted the help text to include my own needs, but I think the confusion is worthy of clarification in future documentation.

Thanks for all your support. I still think Pegasus is a good product and I'm continuing to learn more about it each day.

I have exactly the same problem. "Scan DList" does not seem to work.  It doesn't matter if the alias is included with the email address or not. I have edited the DList and either way it doesn't work.

Testing has demonstrated that it does not work with aliases included in dlist entries.  It should work with only email addresses, as least based on my tests.  Please confirm that what you are saying is that yours failed when using only email addresses in the dlist ( all entries formatted as user@domain.com, no aliases or wildcards).

I have a "New Mail Filtering Rules" set with several rules. The first few are specialized rules to filter certain msgs into specific folders. Those rules work fine.

The purpose of this filter is to set up a white list to leave all white list msgs in the new mail folder and delete everything else.

The last two rules are:
"Scan List   @white.pml   Skip Next Rule"
"Always ... Delete message"

The last rule (the Delete message) gets executed on every message.  It behaves as though the Scan List rule is not there.  The addresses in the white.pml are naked email addresses only. No aliases.