Gnus development mailing list
 help / color / mirror / Atom feed
From: Nils Ackermann <nils@ackermath.info>
To: ding@gnus.org
Subject: Re: Mail messages not queued properly when unplugged.
Date: Thu, 05 Jun 2008 11:07:57 -0500	[thread overview]
Message-ID: <87wsl3yiea.fsf@pascal.matem.unam.mx> (raw)
In-Reply-To: <b4m1w3cf64c.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu\, 05 Jun 2008 20\:55\:47 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> Katsumi Yamaoka wrote:
>
>> 2008-03-18  Nils Ackermann  <nils@ackermath.info>  (tiny change)
>> [...]
>> 	* message.el (message-disassociate-draft): Specify drafts group name
>> 	fully.
>
>> See the article <b4mhcf4jir6.fsf@jpl.org> in this list.  I hasten
>> to have made it revert in the trunk and the v5-10 branch.
>
>> The problem that happens to Nils should be solved in another way.
>
> The problems that Nils Ackermann reported can be found in:
> http://article.gmane.org/gmane.emacs.gnus.general/66523
>
> Nils, even if `message-disassociate-draft' reverted, you can
> achieve making groups' expiry target the nnml:archive group
> except that that of the nndraft:drafts group is `delete'.
> To do that, use
>
> (setq gnus-parameters '(("\\`drafts\\'" (expiry-target . delete))))
>
> instead of:
>
> (setq gnus-parameters '(("nndraft:drafts" (expiry-target . delete))))
>
> Normally a group name that is passed to a back end isn't
> prefixed with the server name.  So, this and the patch to
> `nnmh-request-expire-articles' you made are probably wrong
> approaches.  Maybe the right way is that
> `gnus-request-expire-article' reads the `expiry-target' group
> parameter and passes it to a back end.  However, the nndraft
> back end is special and it is expected to be not so easy.
> I have no plan for the present.

Probably the other part of my change wasn't correct, either.  Maybe
`nnmh-request-expire-articles' should not be called directly by
`nndraft-request-expire-articles' but instead through
`gnus-group-expire-articles-1', because that function takes care of
checking the group parameters.  OTOH, maybe articles should be deleted
unconditionally in the drafts group when sent, instead of being
expired.

I'll look into it again in a couple of weeks, currently I am short of
time.

Nils

-- 
Info: http://www.ackermath.info/



  reply	other threads:[~2008-06-05 16:07 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
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 [this message]
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=87wsl3yiea.fsf@pascal.matem.unam.mx \
    --to=nils@ackermath.info \
    --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).