Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Gnus SPAM support, and email based reporting.
Date: 24 May 2004 14:50:19 -0400	[thread overview]
Message-ID: <4nwu314q38.fsf@lifelogs.com> (raw)
In-Reply-To: <87vfilitqw.fsf@enki.rimspace.net> (Daniel Pittman's message of "Tue, 25 May 2004 04:07:35 +1000")

Daniel Pittman wrote:
> Well, I don't believe that we *can* find a valid default value.
> I certainly know of nothing that would work for ever a small proportion
> of people, let alone a majority.

> This isn't unprecedented within Emacs either; PSGML already does this
> for `user-email-address'.

OK, that's fine then.  Comitted.

> I don't think that this should be the recommended way of setting the
> value, either, just that it is the nicest option when we don't have a
> value already - and it isn't likely to trigger in any automated setup
> that I can see...

> >> No handling of the group stuff yet, because I am not sure where that
> >> is best hooked in.
> >
> > I looked at gnus.el, and the attached patch adds the parameter.  Let
> > me know if the *parameter* looks OK and I can add the rest of the glue
> > to make spam.el do a lexical let on spam-report-resend-to.

> At the moment the code only deals with a string `spam-report-resend-to';
> I wonder if it is best to support more than one address there...

No, I don't think that's necessary.  It would add extra complexity and
I really doubt it's all that useful to have multiple resend-to
addresses.

Try out the code I just comitted and let me know how it works for you.

Ted



  reply	other threads:[~2004-05-24 18:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 12:40 Daniel Pittman
2004-04-17 15:20 ` Derrell.Lipman
2004-04-21 15:44   ` Ted Zlatanov
2004-04-22  9:10     ` Steinar Bang
     [not found]       ` <87fzawgyxq.fsf-1rLz5CwDoL8@public.gmane.org>
2004-04-22 16:23         ` Jochen Küpper
2004-04-22 20:11           ` Ted Zlatanov
     [not found]             ` <4n1xmfept2.fsf-mIZUurteI1BWk0Htik3J/w@public.gmane.org>
2004-04-22 21:32               ` Jochen Küpper
2004-04-23 16:15                 ` Ted Zlatanov
2004-04-22 18:35       ` Ted Zlatanov
2004-04-23  5:34         ` Steinar Bang
2004-04-23  7:45           ` Daniel Pittman
2004-04-23 16:17           ` Ted Zlatanov
2004-05-15 13:27     ` Daniel Pittman
2004-05-18 20:08       ` Ted Zlatanov
2004-05-24 11:09         ` Daniel Pittman
2004-05-24 11:39           ` Kai Grossjohann
2004-05-24 14:07             ` Daniel Pittman
2004-05-24 14:12               ` Kai Grossjohann
2004-05-26 19:00                 ` Michael Schierl
2004-05-24 13:44           ` Ted Zlatanov
2004-05-24 14:18             ` Daniel Pittman
2004-05-24 17:40               ` Ted Zlatanov
2004-05-24 18:07                 ` Daniel Pittman
2004-05-24 18:50                   ` Ted Zlatanov [this message]
2004-05-24 18:52             ` spam.el processor code refactored (was: Gnus SPAM support, and email based reporting.) Ted Zlatanov
     [not found] ` <87isfy7p6a.fsf-kiwxAyAbAnkGAYDEi5AF0l6hYfS7NtTn@public.gmane.org>
2004-04-18 22:05   ` Gnus SPAM support, and email based reporting Jochen Küpper

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=4nwu314q38.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).