Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: IMAP copies of usenet posts in exactly the same format
Date: Thu, 06 Nov 2014 00:57:23 +0100	[thread overview]
Message-ID: <87egthfbfg.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.12886.1415197636.1147.info-gnus-english@gnu.org>

"Andrzej A. Filip" <andrzej.filip@gmail.com> writes:

> How to make gnus store copies of usent posts in IMAP
> folder in exactly the same format as they are sent
> to usenet?

There are several ways to do that, though I don't know
exactly what you mean by "exactly the same format".

The best and most "automatic" way I've found is to set
`gnus-message-archive-group'. In my case, as I use
nnml for mail, it looks like this:

    (setq gnus-message-archive-group "nnml:mail.sent")

This will insert a Gcc header to your outgoing
messages:

    Gcc: nnml:mail.sent

In effect, you are archiving your outgoings by sending
them to yourself.

As for the "same format", in nnml you get a file on
your filesystem for each message. With the 'file'
command, it tells me the files are "news or mail,
ASCII text" - all files (mails and news), so that's
pretty much the same format, I'd say. (Of course, most
often I access them from Gnus, but sometimes as
filesystem files, yes.)

If you get tired of seeing the Gcc header all the
time, use

    (setq message-hidden-headers '( ... "Gcc:") )

If you don't like this method, there are hooks to the
message-mode:

    message-send-hook
    message-send-mail-hook
    message-send-news-hook
    message-sent-hook

You can setup those to save your messages in any way
you like.

-- 
underground experts united

       reply	other threads:[~2014-11-05 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.12886.1415197636.1147.info-gnus-english@gnu.org>
2014-11-05 23:57 ` Emanuel Berg [this message]
2014-11-05 14:26 Andrzej A. Filip

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=87egthfbfg.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).