From: Tassilo Horn <tsdh@gnu.org>
To: Alberto Luaces <aluaces@udc.es>
Cc: ding@gnus.org
Subject: Re: gcc to remote groups
Date: Thu, 31 Jul 2014 11:05:00 +0200 [thread overview]
Message-ID: <877g2t7vb7.fsf@gnu.org> (raw)
In-Reply-To: <87r412ngfa.fsf_-_@eps142.cdf.udc.es>
Alberto Luaces <aluaces@udc.es> writes:
Hi Alberto,
>> (,(rx "nnimap+Uni:ml/")
>> (gcc-self . "nnimap+Uni:Sent"))
>> (,(rx "nnimap+Fastmail:INBOX.mailinglists.")
>> (gcc-self . "nnimap+Fastmail:INBOX.Sent Items"))))
>
> On a side note, I wanted to do this as well, but I was worrying about
> losing the copy of an email if there are network problems during the
> sending process. Any issue with that?
Indeed, I think that can happen if the mail could successfully be
transfered to your SMTP server, but the server hosting the IMAP account
you're gcc-ing to is offline.
I think it would be nice if the gcc-self value could also be a list, so
(gcc-self "nnml+Archive:mail-backups" t)
would mean to put outgoing mail into both the local archive group and
into the current group as well. I've tried that out, but it doesn't
seem to be implemented so far.
I'll hack that right now. Shouldn't be too hard to implement, but give
me some time so that I can also update the docs accordingly.
Bye,
Tassilo
next prev parent reply other threads:[~2014-07-31 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 13:09 Using gnus with gmail: almost there Carlos
2014-07-31 5:56 ` Tassilo Horn
2014-07-31 7:19 ` gcc to remote groups (was: Using gnus with gmail: almost there) Alberto Luaces
2014-07-31 9:05 ` Tassilo Horn [this message]
2014-07-31 9:27 ` gcc to remote groups Tassilo Horn
2014-07-31 9:35 ` Alberto Luaces
2014-07-31 19:18 ` Using gnus with gmail: almost there Carlos Pita
2014-07-31 19:44 ` Carlos Pita
2014-07-31 20:27 ` Carlos Pita
2014-07-31 20:36 ` Adam Sjøgren
2014-08-01 9:01 ` Tassilo Horn
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=877g2t7vb7.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=aluaces@udc.es \
--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).