From mboxrd@z Thu Jan 1 00:00:00 1970 References: <64562eef8a41a3bf4522cd750ac9d1a5@quintile.net> From: Quintile Content-Type: text/plain; charset=utf-8 In-Reply-To: Message-Id: Date: Fri, 31 Oct 2014 19:35:27 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] Setting up Mail in Acme on the Raspberry Pi. Topicbox-Message-UUID: 22657184-ead9-11e9-9d60-3106f5b1d025 sorry for the delay, it's 1/2 term and I have kids to entertain. the (*) would print as a carriage return if your font had the character. I am on my phone here so no manuals , but I wonder if gmail objects to plain= passwords over an unencrypted link? I think SMTP has a flag to force tls on= , and to use macrame or digest auth.=20 worth a try, it looks ok to me on the plan9 side. I used to use gmail but ha= ven't for several years, but my old setup looked like yours. -Steve > On 30 Oct 2014, at 11:13, Mats Olsson wrote: >=20 > Hi Steve! >=20 > First I want to mention that I've added the login information to > factotum prior to trying to send an e-mail from Acme. I open a new > window in Acme and type in the body of the mail. Afterward I type in > the tag line: ;upas/smtp -d -a -h localhost.localdomain > net!smtp.gmail.com mye-mail recipiente-mail >=20 > Then I get this error message: >=20 > Sending /net/dns 'smtp.gmail.com mx' > dns: dns: resource does not exist; negrcode 0 > mxdial trying /net/net!smtp.gmail.com!smtp > 220 mx.google.com ESMTP k72974791lak.22 =E2=80=93 gsmtp (*) > EHLO plan9.168.0.118 (*) > 250 - mx.google.com at your service,[109.225.120.180] (*) > 250 =E2=80=93 SIZE 35882577 (*) > 250 =E2=80=93 8BITMIME (*) > 250 =E2=80=93 STARTTLS (*) > 250 =E2=80=93 ENHANCEDSTATUSCODES (*) > 250 =E2=80=93 PIPELINING (*) > 250 =E2=80=93 CHUNKING (*) > 250 =E2=80=93 SMTPUTF8 (*) > STARTTLS (*) > 220 2.0.0 Ready to start TLS (*) > EHLO plan9.168.0.118 (*) > 250 =E2=80=93 mx.google.com at your service, [109.225.120.180] (*) > 250 =E2=80=93 SIZE 35882577 (*) > 250 =E2=80=93 8BITMIME (*) > 250 =E2=80=93 AUTH LOGIN PLAIN XOAUTH XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARE= R (*) > 250 =E2=80=93 ENHANCEDSTATUSCODES (*) > 250 =E2=80=93 PIPELINING (*) > 250 =E2=80=93 CHUNKING (*) > 250 =E2=80=93 SMTPUTF8 (*) > AUTH LOGIN > 334 VXNlcm5hbWU6 (*) > ZHJ5NjmbHK=3D (*) > 535 =E2=80=93 5.7.8 Username and Password bot accepted. Learn more at (*) > 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=3D14257 > k7sm2974971lak22 =E2=80=93 gsmtp (*) > 535 =E2=80=93 5.7.8 Username and Password bot accepted. Learn more at (*) > 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=3D14257 > k7sm2974971lak22 =E2=80=93 gsmtp QUIT(*) > 221 2.0.0 closing connection k7sm2974971lak22 =E2=80=93 gsmtp (*) > rc 280: smtp 281: Retry, Temporary Failure >=20 > NOTE BY ME: (*) stands for a sign looking like a messy backwards > eurosign maybe covering a final character. >=20 > I would be inmensly appreciative if you or anyone else could shed some > light on what's missing. >=20 > Yours Sincerely, > Mats >=20 > 2014-10-29 22:58 GMT+01:00, Steve Simon : >> Can you send the complete log when sending the email. >>=20 >> You can prevent the window that appears when sending mail >> by teaching factotum the passwords for your mail provider. >>=20 >> Just so we can see the complete conversation with gmail >> and get a better understanding of what went wrong. >>=20 >> I assume you have worked you way through this: >>=20 >> http://www.plan9.bell-labs.com/wiki/plan9/mail_configuration/index.htm= l >>=20 >> particularly with reference to the section on SMTP TLS auth >>=20 >> -Steve >>=20 >>=20