Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Pierfrancesco Caci <pf@tippete.net>
To: info-gnus-english@gnu.org
Subject: Re: nnimap woes after debian upgrade
Date: Sat, 20 Feb 2016 08:33:56 +0100	[thread overview]
Message-ID: <87r3g7ygwr.fsf@snoopy.tippete.net> (raw)
In-Reply-To: <mailman.5169.1455942076.843.info-gnus-english@gnu.org>


Hi Eric

>>>>> "Eric" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:


    Eric> The error message says it all: change my\.imapserver\.it
    Eric> to the string
    Eric> "my.imapserver.it" and you should be fine.
    >> 
    >> I've tried this by changing the variable from inside emacs
    >> configuration. I still get the escapes back when I save. 

    Eric> Did you put quotes in explicitly when entering the server name? You
    Eric> should see the double quotes in the customization interface.

    >> Interestingly, I can access the server fine if I "browse remote server"
    >> and enter the required info manually

    Eric> When you enter the server name at the prompt, it's
    Eric> automatically treated 
    Eric> as a string and quoted.


oh... quotes! yes that worked, I can read mail from my remote server
now, thanks! Interesting that this is now a requirement. 


    Eric> If the upgrade is taking you through several new versions of
    Eric> Gnus, it's 
    Eric> probably worth going back to the Gnus manual and reading the
    Eric> section on 
    Eric> IMAP again, just to make sure you've got everything right.
    >> 
    >> This is "the" manual, right? http://www.gnus.org/manual/big-gnus.html

    Eric> You'll be best off using the in-Emacs info browser: "C-h i", and then
    Eric> "m" and "Gnus". That way you'll know that the manual you're reading
    Eric> corresponds to the Gnus you're using.

Well, that's odd. I remember having the manual inside emacs and browsing
it as you suggest, apparently is no longer there. I'm probably missing a
.deb, but Chtulu knows which one :-)

Anyway, thanks for the help, I've got my main mail working again so I'm
happy. I can live with the local mail broken until I figure out what's
wrong with dovecot.

Pf


    Eric> HTH,
    Eric> Eric



-- 
Pierfrancesco Caci, ik5pvx

  parent reply	other threads:[~2016-02-20  7:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 18:26 Pierfrancesco Caci
2016-02-19  6:33 ` Eric Abrahamsen
     [not found] ` <mailman.5092.1455863619.843.info-gnus-english@gnu.org>
2016-02-19 13:19   ` Pierfrancesco Caci
2016-02-20  4:20     ` Eric Abrahamsen
     [not found]     ` <mailman.5169.1455942076.843.info-gnus-english@gnu.org>
2016-02-20  7:33       ` Pierfrancesco Caci [this message]
2016-02-20  7:39         ` Pierfrancesco Caci
2016-02-21  2:01           ` Eric Abrahamsen

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=87r3g7ygwr.fsf@snoopy.tippete.net \
    --to=pf@tippete.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).