Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] best method for before-add-message.rb
Date: Thu, 10 Feb 2011 09:44:18 -0500	[thread overview]
Message-ID: <1297346751-sup-70@plc.intranet.plecavalier.com> (raw)

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


             reply	other threads:[~2011-02-10 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 14:44 Philippe LeCavalier [this message]
2011-02-10 16:40 ` Mark Alexander
     [not found]   ` <1297356327-sup-9107@plc.intranet.plecavalier.com>
     [not found]     ` <1297357197-sup-5893@bloovis.org>
2011-02-10 19:19       ` Philippe LeCavalier
2011-02-10 22:09         ` Philippe LeCavalier
2011-02-13  1:34           ` Moritz Wilhelmy
2011-02-13  9:51             ` Tero Tilus
2011-02-13 13:00               ` [sup-talk] How to treat List-Id headers (Was: best method for before-add-message.rb) Moritz Wilhelmy
2011-02-13 17:45               ` [sup-talk] best method for before-add-message.rb Rich Lane
2011-02-13 17:12             ` Hamish D
2011-02-13 18:08               ` Philippe LeCavalier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1297346751-sup-70@plc.intranet.plecavalier.com \
    --to=support@plecavalier.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox