From: telephil9@gmail.com
To: 9front@9front.org
Subject: fqa8: sending email with gmail
Date: Wed, 18 Dec 2019 18:03:49 +0100 [thread overview]
Message-ID: <A8D7867948D78FB7EEE2E4767308C03A@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 155 bytes --]
Hi,
Attached is a patch to fqa8 that documents sending mail with gmail.
Thanks to Ori_B and kvik for helping me with the issues I had.
Regards,
Philippe
[-- Attachment #2.1: Type: text/plain, Size: 337 bytes --]
from postmaster@hades:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Disposition: attachment; filename=fqa8-send-gmail.patch
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
[-- Attachment #2.2: fqa8-send-gmail.patch.suspect --]
[-- Type: application/octet-stream, Size: 1611 bytes --]
diff -r c259787f7f92 fqa8.ms
--- a/fqa8.ms Wed Dec 04 21:18:36 2019 -0500
+++ b/fqa8.ms Wed Dec 18 12:47:41 2019 +0100
@@ -891,6 +891,67 @@
.B Note:
Opening large mailboxes over a slow 9p link will be very slow.
+.html - <a name="8.4.1.1.2" />
+.ihtml h5 <h5>
+.SH
+8.4.1.1.2 - Sending mail with gmail
+.R
+.ihtml h5
+
+Add your gmail password to the factotum:
+.P1
+echo 'key proto=pass server=smtp.gmail.com service=smtp \e
+ user=your.username@gmail.com !password=yourpassword' >/mnt/factotum/ctl
+.P2
+
+Configure upas to use gmail as a gateway for outgoing email:
+.P1
+cat /mail/lib/rewrite.gateway >> /mail/lib/rewrite
+.P2
+
+Modify /mail/lib/remotemail to use your gmail account:
+.P1
+#!/bin/rc
+shift
+sender=your.username@gmail.com
+shift
+addr=tcp!smtp.gmail.com!587
+shift
+fd=`{/bin/upas/aliasmail -f $sender}
+switch($fd){
+case *.*
+ ;
+case *
+ fd=gmail.com
+}
+exec /bin/upas/smtp -u your.username@gmail.com -a -h $fd $addr $sender $*
+.P2
+
+Now you can try sending an email:
+.P1
+echo hello | mail -s test your.username@gmail.com
+.P2
+
+This will not work the first time as we also need to add a certificate.
+Look into /sys/log/smtp for the following error:
+.P1
+cert for smtp.gmail.com not recognized:
+ sha256=wnu7Uuzq4MlyJHP90+8f2smoh6x3cj0dG5z02jJlX42
+.P2
+
+Add the certificate to your system:
+.P1
+echo 'x509 sha256=wnu7Uuzq4MlyJHP90+8f2smoh6x3cj0dG5z02jJlX42' \e
+ >> /sys/lib/tls/smtp
+.P2
+
+You should now be able to send emails from 9front!
+
+.B Note:
+This configuration does not work for local email delivery.
+
+
+
.html - <a name="8.4.1.2" />
.ihtml h4 <h4>
.SH
next reply other threads:[~2019-12-18 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:03 telephil9 [this message]
2019-12-18 17:29 ` [9front] " Ori Bernstein
2019-12-18 19:28 ` telephil9
2019-12-19 3:17 ` sl
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=A8D7867948D78FB7EEE2E4767308C03A@gmail.com \
--to=telephil9@gmail.com \
--cc=9front@9front.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).