Rails - Oct 2004 - Rubyonrails email list: From

Hi

Is is possible to configure this list so that the rubyonrails
emails are seen as being sent From
rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org?

Currently rubyonrails.org is in the reply-to category, but my
procmail filters don''t catch this, so all the rails emails
get captured as junk.

-- 
Jim Freeze

On Sat, Oct 16, 2004 at 12:51:09PM +0000,
jim-c4f1mTqwXZkdnm+yROfE0A@public.gmane.org wrote:
> Hi
> 
> Is is possible to configure this list so that the rubyonrails
> emails are seen as being sent From
rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org?
> 
> Currently rubyonrails.org is in the reply-to category, but my
> procmail filters don''t catch this, so all the rails emails
> get captured as junk.
> 
> -- 
> Jim Freeze
No, mucking with the From is not a good idea.  The mails are sent To the
rails list and you should set your procmail rules to filter on the TO
stuff to catch rails mail.  E.g.:

:0:
* ^TOrails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
.rails/

Or something (depending on what mailbox format you use).

-Scott

On Sat, Oct 16, 2004 at 07:25:40PM -0400, Scott Barron
wrote:
> On Sat, Oct 16, 2004 at 12:51:09PM +0000,
jim-c4f1mTqwXZkdnm+yROfE0A@public.gmane.org wrote:
> > Hi
> > 
> > Is is possible to configure this list so that the rubyonrails
> > emails are seen as being sent From
rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org?
> > 
> > Currently rubyonrails.org is in the reply-to category, but my
> > procmail filters don''t catch this, so all the rails emails
> > get captured as junk.
> > 
> > -- 
> > Jim Freeze
> 
> No, mucking with the From is not a good idea.  The mails are sent To the
> rails list and you should set your procmail rules to filter on the TO
> stuff to catch rails mail.  E.g.:
> 
> :0:
> * ^TOrails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> .rails/
As Marcel pointed out to me, you''d probably want ^TO_ there as,
according to the man page, ^TO_ is for specific _addresses_ and ^TO is
for specific _words_.  Though I seem to use TO on everything and manage
to filter my mail OK.  It must be magic :)

-Scott

> No, mucking with the From is not a good idea.  The mails are sent To 
> the
> rails list and you should set your procmail rules to filter on the TO
> stuff to catch rails mail.  E.g.:
Even better to use the header field designed for this.

List-Id: 	rails.lists.rubyonrails.org

Guaranteed not to change, someone can use cc or bcc to send to a list 
and break the other method. Any list using Mailman has this.

jim-c4f1mTqwXZkdnm+yROfE0A@public.gmane.org writes:
> Currently rubyonrails.org is in the reply-to category, but my
> procmail filters don''t catch this, so all the rails emails
> get captured as junk.
Filter on List-Id.

I use the following:

:0:
* ^List-Id:.*rails.lists.rubyonrails.org
rails/.

-mc

-- 
Mike Coleman <mc-z+dVY2EdHMFWk0Htik3J/w@public.gmane.org>
Five Bats Incorporated, Portland Oregon

On Sat, Oct 16, 2004 at 07:00:59PM -0500, Michael Sheets
wrote:
> >No, mucking with the From is not a good idea.  The mails are sent To 
> >the
> >rails list and you should set your procmail rules to filter on the TO
> >stuff to catch rails mail.  E.g.:
> 
> Even better to use the header field designed for this.
> 
> List-Id: 	rails.lists.rubyonrails.org
> 
> Guaranteed not to change, someone can use cc or bcc to send to a list 
> and break the other method. Any list using Mailman has this.
Indeed it would, since this list provides that.  Cc would not break it,
though, as ^TO_ looks at that.  Bcc, it may not catch, though I don''t
know why you''d Bcc a mailing list.  Regardless, List-Id is a more
optimal solution, I was merely expressing that changing the From is not
at all a good idea.

-Scott