From: Emcc <emcc@riseup.net>
To: info-gnus-english@gnu.org
Subject: Re: make sent emails synced in imap sent folder
Date: Wed, 09 Mar 2016 10:06:19 +0800 [thread overview]
Message-ID: <874mcgh0bo.fsf@zhtux.jiantu.boxes> (raw)
In-Reply-To: <871t7l2f8i.fsf@hillenius.net>
Gijs Hillenius <gijs@hillenius.net> writes:
>>> ;; Archive Sent Mail On Imap Server
>>> (setq gnus-message-archive-method
>>> '(nnimap "name-of-your-server-here"))
>
> name-of-your-server-here should correspond to the name you defined for
> the imap server in the server buffer
1. Must this imap server be consistent with my current smtp server?
2. What if: imap.gmail.com for sent archive while smtp.outlook.com for sending?
>
>>> ;; E-mail archive, per month
>>> (setq gnus-message-archive-group
>>> '((if (message-news-p)
>>> "INBOX.misc-news"
>>> (concat "INBOX.sent." (format-time-string "%Y-%m")))))
>> 1. Will this create new 'sent' folders per month under 'Inbox'
>> folder?
>
> nnimap+thuis:INBOX.sent.2015-01
> nnimap+thuis:INBOX.sent.2015-02
> nnimap+thuis:INBOX.sent.2015-03
> nnimap+thuis:INBOX.sent.2015-04
> nnimap+thuis:INBOX.sent.2015-05
>
3. Traditionally, when using email through browser, we can see
folders (letter case sensitive) like 'Inbox', 'Sent', 'Trash'
etc. 'Inbox' is for receving emails while 'Sent' folder is for our
written emails. Why use 'INBOX.sent.' prefix? Why not
'Sent.2015-01'? Is there any difference between 'INBOX' and
'Inbox'?
>
--
Whatever you are, be a good one
next prev parent reply other threads:[~2016-03-09 2:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 14:35 fkqqrr
2016-03-07 15:13 ` Eric Abrahamsen
2016-03-08 7:16 ` Gijs Hillenius
2016-03-08 12:07 ` Fkqqrr
2016-03-08 12:41 ` Fkqqrr
2016-03-08 14:53 ` Gijs Hillenius
2016-03-09 2:06 ` Emcc [this message]
[not found] ` <mailman.6969.1457363607.843.info-gnus-english@gnu.org>
2016-03-08 11:12 ` Fkqqrr
2016-03-08 11:33 ` Fkqqrr
2016-03-10 1:30 ` Eric Abrahamsen
[not found] ` <mailman.7195.1457573482.843.info-gnus-english@gnu.org>
2016-03-10 3:21 ` fkqqrr
2016-03-10 3:40 ` Eric Abrahamsen
[not found] ` <mailman.7199.1457581246.843.info-gnus-english@gnu.org>
2016-03-10 3:55 ` fkqqrr
2016-03-10 7:38 ` fkqqrr
2016-03-10 7:47 ` Eric Abrahamsen
[not found] ` <mailman.7214.1457596037.843.info-gnus-english@gnu.org>
2016-03-10 8:33 ` fkqqrr
2016-05-04 7:21 ` Alice Bob
2016-06-08 2:13 ` Eric Abrahamsen
[not found] ` <mailman.1102.1465352106.1216.info-gnus-english@gnu.org>
2016-06-08 13:58 ` Alice Bob
2016-06-09 1:11 ` Eric Abrahamsen
2016-03-09 2:11 ` Emcc
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=874mcgh0bo.fsf@zhtux.jiantu.boxes \
--to=emcc@riseup.net \
--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).