Re: [9fans] Setting up Mail in Acme on the Raspberry Pi.

[Mats Olsson <plan9.meo@gmail.com>]

Hi Steve!

Thanks for your reply! I'll check it out ASAP. When it comes to the
(*) sign I put it there as a substitution for a character that looked
like a really jagged and pixelized backwards euro sign that I just
dont know what it means. Thanks again!

Kind Regards,
Mats

2014-10-31 20:35 GMT+01:00, Quintile <steve@quintile.net>:
> 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.
>
> worth a try, it looks ok to me on the plan9 side. I used to use gmail but
> haven't for several years, but my old setup looked like yours.
>
> -Steve
>
>
>
>
>
>> On 30 Oct 2014, at 11:13, Mats Olsson <plan9.meo@gmail.com> wrote:
>>
>> Hi Steve!
>>
>> 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
>>
>> Then I get this error message:
>>
>> 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 – gsmtp (*)
>> EHLO plan9.168.0.118 (*)
>> 250 - mx.google.com at your service,[109.225.120.180] (*)
>> 250 – SIZE 35882577 (*)
>> 250 – 8BITMIME (*)
>> 250 – STARTTLS (*)
>> 250 – ENHANCEDSTATUSCODES (*)
>> 250 – PIPELINING (*)
>> 250 – CHUNKING (*)
>> 250 – SMTPUTF8 (*)
>> STARTTLS (*)
>> 220 2.0.0 Ready to start TLS (*)
>> EHLO plan9.168.0.118 (*)
>> 250 – mx.google.com at your service, [109.225.120.180] (*)
>> 250 – SIZE 35882577 (*)
>> 250 – 8BITMIME (*)
>> 250 – AUTH LOGIN PLAIN XOAUTH XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER (*)
>> 250 – ENHANCEDSTATUSCODES (*)
>> 250 – PIPELINING (*)
>> 250 – CHUNKING (*)
>> 250 – SMTPUTF8 (*)
>> AUTH LOGIN
>> 334 VXNlcm5hbWU6 (*)
>> ZHJ5NjmbHK= (*)
>> 535 – 5.7.8 Username and Password bot accepted. Learn more at (*)
>> 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257
>> k7sm2974971lak22 – gsmtp (*)
>> 535 – 5.7.8 Username and Password bot accepted. Learn more at (*)
>> 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257
>> k7sm2974971lak22 – gsmtp QUIT(*)
>> 221 2.0.0  closing connection  k7sm2974971lak22 – gsmtp (*)
>> rc 280: smtp 281: Retry, Temporary Failure
>>
>> NOTE BY ME: (*) stands for a sign looking like a messy backwards
>> eurosign maybe covering a final character.
>>
>> I would be inmensly appreciative if you or anyone else could shed some
>> light on what's missing.
>>
>> Yours Sincerely,
>> Mats
>>
>> 2014-10-29 22:58 GMT+01:00, Steve Simon <steve@quintile.net>:
>>> Can you send the complete log when sending the email.
>>>
>>> You can prevent the window that appears when sending mail
>>> by teaching factotum the passwords for your mail provider.
>>>
>>> Just so we can see the complete conversation with gmail
>>> and get a better understanding of what went wrong.
>>>
>>> I assume you have worked you way through this:
>>>
>>>
>>> http://www.plan9.bell-labs.com/wiki/plan9/mail_configuration/index.html
>>>
>>> particularly with reference to the section on SMTP TLS auth
>>>
>>> -Steve
>>>
>>>
>
>