From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] upas/smtp and gmail
Date: Thu, 23 Jan 2014 11:59:10 -0500 [thread overview]
Message-ID: <7d8f71bcff82ccf35fe155badfaf4480@bellsouth.net> (raw)
In-Reply-To: <20140123055720.GA4132@Grants-MacBook.local>
> The farthest I have gotten is getting smtp to issue 220 Ready to Start
> TLS, and then it exits, that's running smtp with the -d flag.
> /sys/log/smtp reveals a bunch of bad thumbprint x509 lines. I have tried
> adding the sha1 hash to /sys/lib/tls/mail, but this has had no effect.
For outgoing, you'll need to add a thumbprint to /sys/lib/tls/smtp.
Your factotum will need a key with:
proto=pass service=smtp server=your-smtp-server user=your-user-name !password=your-password
This message was sent with exactly that setup, though through ATT,
rather than gmail.
BLS
next prev parent reply other threads:[~2014-01-23 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 5:57 Grant Mather
2014-01-23 10:10 ` erik quanstrom
2014-01-23 16:59 ` blstuart [this message]
2014-01-23 19:54 ` Grant R. Mather
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=7d8f71bcff82ccf35fe155badfaf4480@bellsouth.net \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/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).