Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: rhomunuq+ml_sup@gmail.com (Iain)
Subject: [sup-talk] Arg, gmail
Date: Wed, 27 May 2009 17:36:45 +0100	[thread overview]
Message-ID: <1243442046-sup-3254@leda> (raw)
In-Reply-To: <1e5fdab70905270924t798c4e5er3978e717b2215d48@mail.gmail.com>

(Replying to the list in case of future person with the same problem.)

> I'm having a *little* problem with gmail: I can't send mail with
> neither msmtp nor ssmtp, I get "no route to host" with the first one
> and "can't auth" with the latter, even though last year it worked

Gmail uses non-standard port 587.

Partial example .msmtprc:

account whateveryouwant
auth on
host smtp.gmail.com
port 587
user yourusername at gmail.com
password yourpassword
tls on
tls_starttls on
tls_certcheck off  # Insecure; better would be to add the Gmail cert to
tls_trust_file
auto_from on


  reply	other threads:[~2009-05-27 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 16:24 Guillaume Quintard
2009-05-27 16:36 ` Iain [this message]
2009-05-27 16:38 ` William Morgan
2009-05-27 17:29   ` Guillaume Quintard
2009-05-27 17:36     ` Iain
2009-05-27 17:53       ` Guillaume Quintard
2009-05-27 17:41     ` Nicolas Pouillard
2009-05-27 17:42     ` Mark Alexander

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=1243442046-sup-3254@leda \
    --to=rhomunuq+ml_sup@gmail.com \
    /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