Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: message-send-mail-function, agent, and a day of work
Date: Thu, 15 Apr 2004 18:50:15 -0500	[thread overview]
Message-ID: <ubrlsrebs.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <sdsmf53ro2.fsf@wes.hardakers.net>

Wes Hardaker <wes@hardakers.net> writes:

>>>>>> On Thu, 15 Apr 2004 15:28:28 -0500, Kevin Greiner <kgreiner@xpediantsolutions.com> said:
>
> Kevin> If you are truely changing your code to set
> Kevin> gnus-agent-send-mail-function then you going down the wrong
> Kevin> path.  Your code will now break for those users who have turned
> Kevin> the agent off as gnus-agent-send-mail-function will never be
> Kevin> called.
>
> Sorry, I miss-led you.  Thats only in my .gnus file.  I haven't
> touched real gnus code yet at this point.
>
> Kevin> I'm going to assume that the mail in queue should be dispatched to
> Kevin> multiple smtp servers so that being offline is transparent to the
> Kevin> actual delivery.  If that is the case, I believe that you'll need to
> Kevin> have the first message-send-hook put the selected smtp server into the
> Kevin> message as a header.  The second message-send-hook could then decode,
> Kevin> and remove, the custom header.
>
> I actually was using a custom header at one point, but just reverted
> to checking the From: header which is really all I care about matching
> on.

I just checked in a patch to gnus-agent that will, if it works is
intended, let you change message-send-mail-function.

I'll also take a look at updating the manual.

Kevin



  reply	other threads:[~2004-04-15 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 16:05 Wes Hardaker
2004-04-15 17:20 ` Kevin Greiner
2004-04-15 18:26   ` Wes Hardaker
2004-04-15 20:28     ` Kevin Greiner
2004-04-15 20:35       ` Wes Hardaker
2004-04-15 23:50         ` Kevin Greiner [this message]
2004-04-16  4:09           ` Wes Hardaker

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=ubrlsrebs.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).