Gnus development mailing list
 help / color / mirror / Atom feed
From: Lynbech Christian <christian.lynbech@tieto.com>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>
Cc: <ding@gnus.org>
Subject: Re: two server which I did not add
Date: Fri, 7 Oct 2016 14:35:41 +0200	[thread overview]
Message-ID: <ytqpponcfiaq.fsf@tieto.com> (raw)
In-Reply-To: <87twcqix0u.fsf@yale.edu> (Jorge A. Alfaro-Murillo's message of "Wed, 5 Oct 2016 12:24:49 -0400")

Saving messages locally can seem a bit unnecessary but so many things
can go wrong when sending emails so I like to know that I always have
the original email at hand.

An alternative to saving sent messages (whether within gnus or on an
imap server) is to use the BCC field, for instance by setting:

    (setq message-default-mail-headers (format "Bcc: %s\n" user-mail-address))

On top of getting a copy of the sent email (and having it appear inside
the message thread), you get it through the email system which slightly
increases ones confidence in the email having gone out.

                              -- Christian


-----------------------
On Wed, Oct 05 2016, Jorge A. Alfaro-Murillo wrote:

Rainer M Krug writes:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> On Tue, 04 Oct 2016 11:50:50 +0200, Rainer M Krug wrote:
>>> I have the following two server in gnus, in addition to a local
>>> imap and gmane, which I have no idea where they come from and if I
>>> need them.
>>> ,----
>>>|      {nnfolder:archive} (opened)
>>>|      {nndraft:} (opened)
>>> `----
>>> My questions are:
>>> 1) how did they get here, are they part of the default setup of
>>> gnus?
>>> 2) what are they used for?
>>> 3) how can I get rid of them if they are not needed (I assume that
>>> nndraft might be useful?)?
>>
>> The nnfolder:archive method will be created when a user uses Gnus
>> for the first time (w/o ~/.newsrc.eld, ~/.gnus.el) for archiving
>> sent messages.  See: (info "(gnus)Archived Messages") 
>>
>> To remove it, quit Gnus, edit the ~/.newsrc.eld file and delete the
>> ("archive" ...) portion in the (setq gnus-server-alist...) section.
>> Be extremely careful!  To turn on the show-paren-mode is
>> recommended.

The archive keeps the messages you have sent. Because my imap keeps a
copy of the sent messages, I do not need a local copy. I think I
removed it just by setting gnus-message-archive-method to nil.

>> The draft: method is used for handling draft messages to send. I
>> don't know alternative way of it, so never remove it.  See: (info
>> "(gnus)Drafts")
>
> Thanks for the info - as they are more or less part of gnus, I'll
> just leave them where they are.

Yes, the draft has messages that you are editing but haven't sent yet.

Best,
-- 
Jorge.



  reply	other threads:[~2016-10-07 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04  9:50 Rainer M Krug
2016-10-05  0:20 ` Katsumi Yamaoka
2016-10-05  7:32   ` Rainer M Krug
2016-10-05 16:24     ` Jorge A. Alfaro-Murillo
2016-10-07 12:35       ` Lynbech Christian [this message]
2016-10-11  4:47 ` Snippet formatting (was: two server which I did not add) Arkady Grudzinsky
2016-10-11  5:52   ` Snippet formatting Arkady Grudzinsky

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=ytqpponcfiaq.fsf@tieto.com \
    --to=christian.lynbech@tieto.com \
    --cc=ding@gnus.org \
    --cc=jorge.alfaro-murillo@yale.edu \
    /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).