From: Sharon Kimble <boudiccas@skimble.plus.com>
To: ding@gnus.org
Subject: Re: problems in sending out emails
Date: Thu, 22 Jan 2015 18:45:02 +0000 [thread overview]
Message-ID: <87egqmac41.fsf@skimble.plus.com> (raw)
In-Reply-To: <87ppa9qqgr.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
Since I sent the original email the problem has not recurred. I've
restarted emacs/gnus many times since then, and also rebooted, and
everything is now working okay. Thanks folks, I've made a note of
what to do if the problem recurs.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.6, emacs 24.4.1.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2015-01-22 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 13:12 Sharon Kimble
2015-01-20 17:21 ` Steinar Bang
2015-01-20 18:03 ` e.fraga
2015-01-22 18:45 ` Sharon Kimble [this message]
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=87egqmac41.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--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).