Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Mail messages not queued properly when unplugged.
Date: Fri, 30 May 2008 16:33:59 +0900	[thread overview]
Message-ID: <b4mskw0mejc.fsf@jpl.org> (raw)
In-Reply-To: <m2ve2k3ogc.fsf@xemacs.org>

>>>>> Malcolm Purvis wrote:
> Today I upgraded to the latest version of No Gnus in CVS from a version
> about amonth old.  I'm now getting mail messages being deleted when
> being sent unplugged rather than being queued.

Does it still happen even now?  I tried No Gnus and XEmacs 21.5,
both are the latest, and had no problem.

> The minibuffer messages are:

> Reading active file via nnnil...
> Deleting article /Users/malcolmp/News/drafts/queue/1 in nndraft:drafts...
> Sending...done
> Wrote /Users/malcolmp/News/drafts/queue/1
> Sending via mail...
> Sending...

Wasn't the file name "drafts/drafts/1", not "drafts/queue/1" ?

If so, it looks as if a mail was really sent (probably it failed
in fact because the mail server was unreachable, though).  If it
really happened, I have only one idea of the cause of it.  That
is that the variable `gnus-agent-send-mail-function' has been
set to a non-nil value before Gnus was agentized.  If you have
something like the following snippet in the ~/.gnus.el file,

(setq gnus-agent-send-mail-function message-send-mail-function)
...[1]

the `message-send-mail-real-function' variable will not be set to
`gnus-agent-send-mail':

(defun gnus-agentize ()
[...]
  (unless gnus-agent-send-mail-function
    (setq gnus-agent-send-mail-function
	  (or message-send-mail-real-function
	      (function (lambda () (funcall message-send-mail-function))))
	  message-send-mail-real-function 'gnus-agent-send-mail))

So what's the value of `message-send-mail-real-function' in your
XEmacs?  It should be `gnus-agent-send-mail' if Gnus is agentized.
If it is left nil that is the default, Message will always use
the value of `message-send-mail-function':

(defun message-send-mail (&optional arg)
[...]
		(funcall (or message-send-mail-real-function
			     message-send-mail-function)))


[1] I actually have it in my ~/.gnus.el file, though I don't
    recall why I did so.  My pc is always connected to the net,
    so I can send mails regardless of the plugged state of Gnus.



  parent reply	other threads:[~2008-05-30  7:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  7:06 Malcolm Purvis
2008-04-15 13:33 ` Michael Piotrowski
2008-04-16  6:21   ` Malcolm Purvis
2008-04-16  9:21     ` Michael Piotrowski
2008-05-07 12:42       ` Norman Walsh
2008-05-09  9:21         ` Michael Piotrowski
2008-05-09 19:36           ` Norman Walsh
2008-05-12 11:02             ` Michael Piotrowski
2008-05-30  7:33 ` Katsumi Yamaoka [this message]
2008-06-03 17:00   ` Michael Piotrowski
2008-06-04  9:00     ` Katsumi Yamaoka
2008-06-04 12:01       ` Michael Piotrowski
2008-06-04 18:20         ` Reiner Steib
2008-06-05  0:46           ` Katsumi Yamaoka
2008-06-05 11:55             ` Katsumi Yamaoka
2008-06-05 16:07               ` Nils Ackermann
2008-06-05 18:12                 ` Nils Ackermann
2008-06-05 14:55             ` Michael Piotrowski

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=b4mskw0mejc.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).