Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: .netrc parsing stopped working when not giving port numbers
Date: Mon, 17 Jun 2013 06:49:11 -0400	[thread overview]
Message-ID: <m2fvwhqafs.fsf@lifelogs.com> (raw)
In-Reply-To: <m3ehc16qu9.fsf@stories.gnus.org>

On Mon, 17 Jun 2013 11:15:10 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> I have entries like
LMI> machine foo login bar password zot

LMI> When searching for the smtp or imap passwords on host foo, I'm not
LMI> getting anything.  .netrc should return this as a match, even though
LMI> there's no port number there.

That's very likely my fault and I will look at it later today.

Ted




  reply	other threads:[~2013-06-17 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  9:15 Lars Magne Ingebrigtsen
2013-06-17 10:49 ` Ted Zlatanov [this message]
2013-06-17 23:34   ` Ted Zlatanov
2013-08-01 14:40     ` Lars Magne Ingebrigtsen
2013-08-01 16:45       ` Ted Zlatanov

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=m2fvwhqafs.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).