From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Still pounding nnimap and odd gmail behavior
Date: Thu, 23 May 2013 17:11:49 -0400 [thread overview]
Message-ID: <8761y9v1t6.fsf@newsguy.com> (raw)
In-Reply-To: <877giqxhhf.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> And this in .authinfo
>>
>> machine imap.gmail.com login acc1@gmail.com password xxxxxxxx port imap
>> machine imap.gmail.com login acc2@gmail.com password xxxxxxxx port imap
>
> I used to have two gmail accounts. The trick, for me, was to give
> machines different names:
>
> machine acc1 login acc1@gmail.com ...
> machine acc2 login acc2@gmail.com ...
>
> given the nnimap entries you have defined in your .gnus.el file. The
> actual IMAP server has already been specified using nnimap-address.
>
> Not sure if this would make any difference in your case but it may be
> worth trying?
Haven't tried your suggestion yet. But want to get clarity on something.
Enrico Schumann <es@enricoschumann.net> writes:
[...]
> You could try to change .authinfo like this:
>
> machine acc1 login acc1@gmail.com password xxxxxxxx port imap force yes
> machine acc2 login acc2@gmail.com password xxxxxxxx port imap force yes
>
>
> (That worked for me with several IMAP accounts with the same
> nnimap-address, but that was not gmail.)
Same thing to clarify here.
Do you mean like so:
('password xxxxxxxx' has been elided to shorten)
machine loginname1 login loginname1@gmail.com [...] port imap force yes
machine loginname2 login loginname2@gmail.com [...] port imap force yes
That is, NOT giving a fully qualified hostname as argument to `machine'?
or do you mean this:
machine loginname1@gmail.com login loginname1@gmail.com [...]
machine loginname2@gmail.com login loginname2@gmail.com [...]
That is, using the full email address in two places. Again NOT a
qualified IP address.
Sorry if this seems weak...
I think I better post the actual lines leaving out the password and
final arguments and you guys show me exactly what you are suggesting.
machine imap.gmail.com login hputnam3@gmail.com
machine imap.gmail.com login harrygp3@gmail.com
Those are the actual lines... How would you edit them?
next prev parent reply other threads:[~2013-05-23 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 22:46 Harry Putnam
2013-05-23 7:08 ` Alberto Luaces
2013-05-23 20:56 ` Harry Putnam
2013-05-23 21:33 ` Joseph Mingrone
2013-05-24 5:26 ` Steinar Bang
2013-05-24 7:28 ` Alberto Luaces
2013-05-25 21:54 ` Harry Putnam
2013-05-23 7:50 ` Eric S Fraga
2013-05-23 21:11 ` Harry Putnam [this message]
2013-05-24 5:48 ` Steinar Bang
2013-05-24 6:10 ` Enrico Schumann
2013-05-25 21:59 ` Harry Putnam
2013-05-27 7:22 ` Enrico Schumann
2013-06-06 14:39 ` Ted Zlatanov
2013-05-24 10:16 ` Eric S Fraga
2013-05-25 22:04 ` Harry Putnam
2013-05-23 9:29 ` Enrico Schumann
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=8761y9v1t6.fsf@newsguy.com \
--to=reader@newsguy.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).