On Friday 28 March 2008 03:30:14 John Andersen wrote:

On Thu, Mar 27, 2008 at 2:12 PM, Stan Goodman

wrote:

...

Is there somewhere a description of the requirements for writing a custom filter for Kwrite incoming mail?

For example, how to call such a filter, how it should access the components of an incoming message (body, all headers, perhaps specific headers), how to return a filter action?

With Kmail available, probably one of the better mail agents available, why on earth would you want to use Kwrite for mail?

Is this a case of the only tool you know being a hammer making you look at every problem as if it were a nail?

I wouldn't. I mistyped. I am speaking about Kmail. I have no idea how one would go about using an editor for email. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 29 March 2008 01:38:13 Will Stephenson wrote:

On Friday 28 March 2008 08:36:24 Stan Goodman wrote:

...

On Friday 28 March 2008 03:30:14 John Andersen wrote:

...

On Thu, Mar 27, 2008 at 2:12 PM, Stan Goodman

wrote:

...

Is there somewhere a description of the requirements for writing a custom filter for Kwrite incoming mail?

For example, how to call such a filter, how it should access the components of an incoming message (body, all headers, perhaps specific headers), how to return a filter action?

With Kmail available, probably one of the better mail agents available, why on earth would you want to use Kwrite for mail?

Is this a case of the only tool you know being a hammer making you look at every problem as if it were a nail?

I wouldn't. I mistyped. I am speaking about Kmail. I have no idea how one would go about using an editor for email.

I thought you did, but I'm afraid I don't understand some of the rest of the original request either.

"how to call such a filter" - do you mean "how to trigger a filter manually"? (filters normally act on incoming mail).

"how to return a filter action"?

Could you describe what you want to do?

Will

I need a filter criterion that I do not think is possible to implement using the filter available scheme. If want to write a script to examine specific headers of incoming messages, and either deposit the message in the inbox or dump it. To anticipate the next question ("What sort of bizarre criterion might that be?"), I will describe an example. If I have overlooked a possibility within the capability of the default scheme, I would be very happy to be corrected. A LOT of the the junk mail I get is addressed, in either To or Cc header, with more than one address, each one consisting of the same domain, and one or more of them with a legitimate username, while the others have fictitious usernames. If there is a way to filter like this within Kmail (have I got it right this time?), I do not see it, because it would have to parse email addresses into: <address> --> <username>@<domain> and make sure that the combination belongs to a set of legitimate addresses. Since a legitimate address is always present, it is not possible to rely on "contains", "doesn't contain" or anything of the sort. If that is still unclear, or if you see something I don't, please tell me. But if my conclusion is correct, please tell me how to use a custom filter in the way I asked. The filter itself will be very easy to code. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 30 March 2008 11:54:25 G T Smith wrote:

Stan Goodman wrote:

<snip>

...

I need a filter criterion that I do not think is possible to implement using the filter available scheme. If want to write a script to examine specific headers of incoming messages, and either deposit the message in the inbox or dump it.

To do more sophisticated mail filtering procmail is probably a better tool than those embedded in most mail clients, unfortunately it is not the easiest thing in the world to configure and use...

For further info look at ..

man procmail man procmailrc man procmailex

combined with spamassassin it is very effective....

I will read those man pages. Thank you. An alternative is to go back to Polarbar Mailer, in which custom filters are a lead-pipe cinch. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 30 March 2008 19:49:28 John Andersen wrote:

On Sun, Mar 30, 2008 at 2:30 AM, Stan Goodman

wrote:

...

On Sunday 30 March 2008 11:54:25 G T Smith wrote:

...

Stan Goodman wrote:

<snip>

...

I need a filter criterion that I do not think is possible to implement using the filter available scheme. If want to write a script to examine specific headers of incoming messages, and either deposit the message in the inbox or dump it.

To do more sophisticated mail filtering procmail is probably a better tool than those embedded in most mail clients, unfortunately it is not the easiest thing in the world to configure and use...

For further info look at ..

man procmail man procmailrc man procmailex

combined with spamassassin it is very effective....

I will read those man pages. Thank you. An alternative is to go back to Polarbar Mailer, in which custom filters are a lead-pipe cinch.

The alternative might be just to write a regular expression working against <recipients> (which includes both TO and CC). The inclusion of ANY user@domain combination that is NOT known to you should be sufficient.

This is totally impractical if your good list is long, but with only a few entries and the full power of regular expressions available I'm sure it can be done.

You could count the list of good addresses on the fingers of one hand, and even get change; they are the one that I have been writing from, plus a very few others using the same domain name. The unacceptable ones consist of the same domain name with any other usernames. So you would have to observe that that other addresses are present, and that some of them contain the same domain but variant usernames. That's a lot to put into a regular expression. Someone has pointed out that there is in the list of Filter Actions provided in the Kmail filter system a choice called "Execute Command", and suggested that the Command could be a filter script. But the fact that it appears as a Filter Action (after Filter Critera are satisfied) would suggest that it isn't for that purpose at all, but for e.g. sounding an audible alarm for a message that satisfies the criteria. Also there is nothing whatever in the "documentation" of Kmail about how to access an incoming message, or anything else. This, of course, is not a big surprise. So I am inclined to believe that there is not a way to devise a filter criterion that the developer hasn't already thought of. Which is very limiting. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Stan,

Will...

Probably you are the best one to know an answer to my "Vanishing Panel" problem. Why has it become invisible, except for a fraction of a second at boot time? And how can I stop it from doing that? In the absence of the multiple virtual desktops, I am having a terrible time operating.

my ~/.kde/share/config/kickerrc file contains the following line: "AutoHidePanel=false" May be yours is set to true? HTH hjb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 29 March 2008, Stan Goodman said:

And in the absence of virtual desktops, my workarounds have revealed to me a serious design error, which I can explain to you very easily.

Please explain. Will -- Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org