Re: First steps in packaging
On Fri, Apr 18, 2003 at 01:54:59PM +1000, Matthew Palmer wrote:
> On Thu, 17 Apr 2003, Pete Ryland wrote:
> > On Thu, Apr 17, 2003 at 11:46:21AM +1000, Matthew Palmer wrote:
> > > On Wed, 16 Apr 2003, David Z Maze wrote:
> > > > Your mailer doesn't have a "reply to all" button? Get a better one,
> > > > Debian has lots.
> > >
> > > The problem we're discussing, though, is that "reply to all" means
> > > exactly that - to *all*.
> >
> > Hmm.. I recall "reply to list" being mentioned, not "reply to all" which
> > is different. I've already deleted David's mail, but is that really
> > what he said?
>
> http://lists.debian.org/debian-mentors/2003/debian-mentors-200304/msg00265.html
Ok, fair enough. I must have just misread the first time.
> Or would you like to accuse me of tampering with the list archives while
> you're at it?
Oh, ok. If you'd like. ;-)
> Out of interest, are there any MUAs which have a separate "reply to list"
> function?
Most do AFAIK. Not sure about pine, but then it's not in Debian anyway.
> > Duplicate removal is easy, yes, but if you were to reply to me *and* the
> > list, the mail sent directly to me will usually get to me first and so
> > the one sent to the list will be removed. This means that it will end
> > up in my normal inbox rather than my mailbox for said list, which is
> > slightly annoying.
>
> It depends on how you're filtering your lists. I get a personal copy in
> my inbox and one to the list (which is what you're talking about) because
> I filter based on the headers added by the list software. It could be
> PITA I suppose, although I don't think it would bother me because I'm
> pretty careful these days about who an e-mail is going to (after some
> oopses in the eldar days). If you filter based on procmail's _TO (is that
> the macro for it?) or something like that, then both copies should (I
> imagine) end up in the folder for the mailing list.
I use a catch all lists in my procmail, so I don't have to do anything when
I join a new list:
# Most lists
:0
* ^((List-Id|X-(Mailing-)?List):(.*[<]\/[^>]*))
{
LISTID=$MATCH
:0:
* LISTID ?? ^\/[^@\.]*
IN.$MATCH
}
# Majordomo
:0
* ^Sender: owner-[^@]+@[^@\+]+
* ^Sender: owner-\/[^@\+]+
{
:0:
IN.$MATCH
}
:0
* ^Sender: [^-@]+-(list-)?owner@[^@\+]+
* ^Sender: \/[^-@]+(-list)?
{
:0:
IN.$MATCH
}
And then some ^TO rules for some other lists that don't work with the above.
This works pretty well, apart from the dup removal problem. I have some
mates that insist on using nothing but "reply to all" so it's kind of
necessary.
> Duplicates, though, don't bother me - I figure it's not an excessive
> hassle, and I normally go through all my mailboxes at once, so I should be
> able to remember which messages I've already replied to.
Fair enough.
Pete
--
Pete Ryland
http://pdr.cx/
Reply to: