From: Catalin Marinas <catalin.marinas@gmail.com>
To: Aubin LaBrosse <aubin@stormboxes.com>
Cc: git@vger.kernel.org
Subject: Re: StGIT mail configuration
Date: Mon, 13 Feb 2006 21:45:56 +0000 [thread overview]
Message-ID: <b0943d9e0602131345r43b02496g@mail.gmail.com> (raw)
In-Reply-To: <43F0F072.90609@stormboxes.com>
On 13/02/06, Aubin LaBrosse <aubin@stormboxes.com> wrote:
> I'm using StGIT 0.8.1 on top of the latest release of Cogito - in
> .git/stgitrc of a local git repo, I have the following part related to
> my mail configuration:
>
> smtpserver: mail.stormboxes.com:25
> smtpuser: username@stormboxes.com
> smtppassword: myPassword
>
> (actual username and password redacted, of course) - the point is, the
> username actually is that entire string 'username@stormboxes.com' (no
> quotes) because the box it's on is a virtual server for many domains and
> the usernames must contain the domain to which they belong. anyway, i
> was getting authentication failures, so i hacked up mail.py and set the
> debug level on the smtp object - i found out that it's trying to auth
> using CRAM-MD5. And I'm not sure whether the server doesn't support
> that or not, but i didn't see anything in the python doc that would
> indicate that i could make the login() method use auth login or auth
> plain or something else
At least with Python 2.4, the authentication type is detected
automatically based on server's response to the ehlo command. It
supports cram-md5, plain and login (and I think it tries them in this
order). If the server responds with something different, the login()
command would raise an exception like "No suitable authentication
method found.". You could print s.esmtp_features["auth"] in mail.py in
StGIT after ehlo.
I haven't read the RFC2554 but you could also try to replace the '@' with '%40'.
> thunderbird works fine but i can't figure out which auth type
> it's using. (suppose i could tcpdump it and see) I have, of course,
> triple checked my auth credentials at this point.
Probably using tcpdump or ethereal would be the easiest.
--
Catalin
prev parent reply other threads:[~2006-02-13 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 20:47 StGIT mail configuration Aubin LaBrosse
2006-02-13 21:45 ` Catalin Marinas [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=b0943d9e0602131345r43b02496g@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=aubin@stormboxes.com \
--cc=git@vger.kernel.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).