Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: How to know a mail is sent with gnus ?
Date: Mon, 14 Feb 2011 08:28:06 +0100	[thread overview]
Message-ID: <87k4h3jcs9.fsf@member.fsf.org> (raw)
In-Reply-To: <m2zkpzliy5.fsf@gmail.com> (Francis Moreau's message of "Sun, 13 Feb 2011 22:32:02 +0100")

Francis Moreau <francis.moro@gmail.com> writes:

Hi Francis,

>>> Could anybody tell me what I can test ?
>>
>> At least `org-gnus.el' checks for Message-Id and Gcc headers to store
>> links to Gnus messages that haven't been sent at the time of linking
>> yet.  I might be wrong, but I think Gcc headers are a Gnus invention.
>>
>
> The thing is that I don't always use Gcc header. For mailing lists for
> example, I don't use it since I'm going to receive a copy of the mail
> anyways.

Hm, I always set a Gcc.  For normal groups it's the group itself, and
for mailing list groups, I set a Gcc to my "Sent Messages" group.

Instead of looking at the Gcc, you could set
`message-generate-headers-first' to t and make User-Agent non-optional
in `message-required-mail-headers'.  That should insert a User-Agent
header with Gnus + version as contents as soon as you write a mail from
inside Gnus.

HTH,
Tassilo



  reply	other threads:[~2011-02-14  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13 20:07 Francis Moreau
2011-02-13 20:20 ` Tassilo Horn
2011-02-13 21:32   ` Francis Moreau
2011-02-14  7:28     ` Tassilo Horn [this message]
2011-02-14  7:55       ` Francis Moreau
2011-02-13 23:51 ` Andreas Schwab
2011-02-14  8:05   ` Francis Moreau
2011-02-15  1:03     ` Dave Goldberg
2011-02-15  7:59       ` Francis Moreau
2011-02-15 22:36         ` Dave Goldberg
2011-02-19 11:15           ` Francis Moreau

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=87k4h3jcs9.fsf@member.fsf.org \
    --to=tassilo@member.fsf.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).