Re: some mail annoyances

[Ken McGlothlen <mcglk@serv.net>]

reader@newsguy.com (Harry Putnam) writes (in response to a missive by me):

| > (For example, mail from userA to me should go in the userA folder, but mail
| > from userA to me *and* userB, userC, userD and userE should go in the
| > groupZ folder.)
| 
| A small point here, about splitting:  I believe gnus "fancy splitting" can
| handle that setup, but if you are already familiar with procmail, then why
| not use procmail to do the more complicated splitting.  Procamil can easily
| handle the problem you present because you can list as many conditions as you
| like in a single rule.

Hm.  True.  That wasn't the case when I first started using procmail, and I
rarely have use for that feature, so I'd forgotten.  But yes, okay.

| The deletion expiration stuff is a bit confusing but becomes less so if you
| kind of forget deletion as an option, like you would on an nntp group.  Think
| of deletion as something taken care of by a "higher power" and you just guide
| its hand as to when with your expiry.

Actually, I've noticed that one of the things that confuses people the most is
that messages "disappear" once they've been read.  Which is why I say that some
article needs to be written that addresses it for people new to Gnus.

| Taking a word of advice from Karl K. I've switched the bindings of "E"
| (gnus-summary-mark-as-expirabl) and "e" (gnus-summary-edit-article) Since
| expiring is much more common function for me.  That makes it easier to mark
| as `expirable', since no <SHIFT> is needed

That's an excellent idea; I wonder why that isn't the default.