[sup-talk] best method for before-add-message.rb

[Philippe LeCavalier <support@plecavalier.com>]

Hi All.

I'm still working on my initial labeling/hooks and best choices thereof.

I'm torn between a few options.

i)external file reference (would be my preferred method)
-can't list anything other than full email addresses in the file
@domain.com, wildcards...etc. would be nice
-can't comment in the file. It would be nice to weed out comments
-is it possible that when an address has a subdomain the example in the wiki breaks? ie list@list.domain.com
none of my hooks for these types of addresses seem to work
-is Sup caching the referenced file? if not, I presume this option significantly slows things down

ii)not using an external file makes the hook file lengthy. However it seems to be the only safe way of adding multiple labels - which I feel crucial to making a strong searchable system. Perhaps a label(s)-markread-archive would be nice :)
-using this method I find myself writing a ton of rules for the same thread.
a)label the thread from a particular community/client/area
b)label the thread from a particular person within said community/clientel/area
c)label it something useful ie (not)important/archive/redirect/bounce(hehe)...etc.


I'm assuming my difficulties spring from a few basic assumptions;
I can't write any code let alone Ruby, if my life depended on it.
The wiki has solid working examples for those who can work with Ruby. Again I don't speak Ruby.
And mostly, I come form a world where things get filtered to folders :-( I'm really trying to keep an open mind and I know I'll get there but my inbox now has thousands of mails in it and I'm the type that kept a strict 0 count. In order for me to move to Sup I had to get *real* disorganized before getting *real* organized ;-) All that to say that for types like me, it's all about copying other, less ruby-challenged, peoples work. So for the past three weeks I've been living in the wiki....It's a pretty lonely place out there!

In keeping an open mind about all this, I'm open to hearing examples of how others handle there workflow that are achieving the same goal I have in mind. ie label everything with individual labels and archive it all using the least/simplest/most efficient code possible. This way I can search for clients,client A,reports,after:tue-jan-18(I think the latter is prob. wrong but feel like looking up chronic's standards at the moment:-) )

My mail is really important to me so if the only response I get from this is "learn Ruby you lazy-ass-bastard!" I'll get the message(lousy pun eh?) ;-)
-- 
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk