Confirmed that I now have this working with Gmail and the current build. I ended up using SMTP auth type 'Login' for Gmail. I also needed to make some changes to the security settings at Gmail else the whole thing would just not work.

--- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I ended up using SMTP auth type 'Login' for Gmail. I also needed to make some changes to the security settings at Gmail else the whole thing
would just not work.

What were the settings you needed to change for Gmail?

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pb.darktech.org:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Mystic Prison Board BBS*Mesquite Tx (21:1/134)

Confirmed that I now have this working with Gmail and the current build.
I ended up using SMTP auth type 'Login' for Gmail. I also needed to make some changes to the security settings at Gmail else the whole thing
would just not work.

Great to hear!

The issue was specific to password reset, which is why I was struggling with it. I was testing with e-mail validation using Gmail and the issue was that when doing password reset, it wasn't using the configuration value for SSL.
So every time I would test it, it'd work fine for me!

What did you have to change at Gmail? I am guessing it freaks out about an unknown login if you are just using a standard e-mail account. It might be something worth noting in the Wiki at some point.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

On 12/23/18, Zazz pondered and said...

What were the settings you needed to change for Gmail?

Will post a follow-up ;)

--- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 12/23/18, g00r00 pondered and said...

What did you have to change at Gmail? I am guessing it freaks out about an unknown login if you are just using a standard e-mail account. It might be something worth noting in the Wiki at some point.

Righto I set up my config as follows

First I installed the complied cl32.dll and also dropped in cl64.dll from CryptLib. I suggest you really should ship Mystic with these if at all possible.

Servers > Server Options

Ûßßßßßßßßßßßßßßßß Server Options ßßßßßßßßßßßßßßßßßÜ
Û Û
Û Domain Name ³ agency.bbs.nz Û
Û Max BBS Nodes ³ 8 Û
Û Start Hidden ³ No Û
Û Enable SMTP Send ³ Yes Û
Û SMTP Host ³ smtp.gmail.com:587 Û
Û SMTP IP Type ³ IPV4 Only Û
Û SMTP Login ³ agencybbs@gmail.com Û
Û SMTP Password ³ ************* Û
Û SMTP Auth Type ³ Login Û
Û SMTP Use SSL/TLS ³ Yes Û ßÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÛ


At this stage Configuration > User Password Policy is set like this

Ûßßßßßßßßßßßßßßß User Password Policy ßßßßßßßßßßßßßßßÜ
Û Û
Û Minimum Length ³ 7 Û
Û Minimum Capital Letters ³ 1 Û
Û Minimum Numbers ³ 1 Û
Û Minimum Symbols ³ 0 Û
Û Maximum Password Attempts ³ 3 Û
Û Force Password Change ³ 0 Û
Û Allow Password Inquiry ³ Yes Û
Û Allow Reset By E-mail ³ Yes Û
Û Password Storage Method ³ PBKDF2 SHA512 Hash Û
Û PBKDF2 512-bit Iterations ³ 1000 Û
Û Û ßÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÛ


Then I ran a test with a test user and assigned an email address that would come to me

The node logs showed an error when SMTP was trying to connect to Gmail and I then got an email from Gmail.

[snip]

Sign-in attempt was blocked for your linked Google Account

Someone just used your password to try to sign in to your account from a non-Google app. Google blocked them, but you should check what happened.
Review your account activity to make sure no one else has access.
Check activity.

[snip]

I then had to go to Google Account > Security > Less secure app access
and then set that to 'on'

So according to Google it's making my Gmail account more vulnerable but at least it now works :)

Perhaps there's something you can do to keep Google happy so we don't have to set this setting to on?

Lastly I did a password reset test and the node logging looked good.

[snip]


------------------- Node 1 (Mystic v1.12 A40 2018/12/22)
2018.12.23 20:59:10 Connect from 103.25.58.8 (Unknown)
2018.12.23 20:59:10 Connection by Telnet
2018.12.23 20:59:10 Set time left 10 TE=1269
2018.12.23 20:59:18 Bad PW: 11
2018.12.23 20:59:18 Bad PW: 11
2018.12.23 20:59:19 Bad PW: 11
2018.12.23 20:59:21 SMTP R:220 smtp.gmail.com ESMTP y5sm36069076pge.49 - gsmtp 2018.12.23 20:59:21 SMTP S:EHLO agency.bbs.nz
2018.12.23 20:59:22 SMTP R:250-smtp.gmail.com at your service, [219.89.83.33] 2018.12.23 20:59:22 SMTP R:250-SIZE 35882577
2018.12.23 20:59:22 SMTP R:250-8BITMIME
2018.12.23 20:59:22 SMTP R:250-STARTTLS
2018.12.23 20:59:22 SMTP R:250-ENHANCEDSTATUSCODES
2018.12.23 20:59:22 SMTP R:250-PIPELINING
2018.12.23 20:59:22 SMTP R:250-CHUNKING
2018.12.23 20:59:22 SMTP R:250 SMTPUTF8
2018.12.23 20:59:22 SMTP S:STARTTLS
2018.12.23 20:59:22 SMTP R:220 2.0.0 Ready to start TLS
2018.12.23 20:59:23 SMTP S:AUTH LOGIN
2018.12.23 20:59:23 SMTP R:334 VXNlcm5hbWU6
2018.12.23 20:59:23 SMTP S:YWdlbmN5YmJzQGdtYWlsLmNvbQ==
2018.12.23 20:59:23 SMTP R:334 UGFzc3dvcmQ6
2018.12.23 20:59:23 SMTP S:bXlzdGljMjAxOA==
2018.12.23 20:59:24 SMTP R:235 2.7.0 Accepted
2018.12.23 20:59:24 SMTP S:MAIL FROM:<sysop@agency.bbs.nz>
2018.12.23 20:59:24 SMTP R:250 2.1.0 OK y5sm36069076pge.49 - gsmtp
2018.12.23 20:59:24 SMTP S:RCPT TO:<ph@paulhayton.nz>
2018.12.23 20:59:25 SMTP R:250 2.1.5 OK y5sm36069076pge.49 - gsmtp
2018.12.23 20:59:25 SMTP S:DATA
2018.12.23 20:59:25 SMTP R:354 Go ahead y5sm36069076pge.49 - gsmtp
2018.12.23 20:59:26 SMTP R:250 2.0.0 OK 1545551967 y5sm36069076pge.49 - gsmtp

[snip]

and the email came in

[snip]

From: Agency BBS <agencybbs@gmail.com>
Subject: Password Reset Code for Agency BBS
To: TestUser

Enter the following code when prompted by the BBS to reset your password: RDOPVMPN

[snip]

A nice idea might be to create a text file in mystic\data that sysops can customise the email body copy a bit more.

Best, Paul

--- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

|10On 12/24/18, Avon said the following...|10

On 12/23/18, Zazz pondered and said...

What were the settings you needed to change for Gmail?

Will post a follow-up ;)

Ok

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pb.darktech.org:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Mystic Prison Board BBS*Mesquite Tx (21:1/134)

First I installed the complied cl32.dll and also dropped in cl64.dll from CryptLib. I suggest you really should ship Mystic with these if at all possible.

I'm using linux. I followed the Mystic Wiki guide, but Mystic will throw a runtime erorr when the libcl.so file is placed in /usr/lib.

Any advice?

--- Mystic BBS v1.12 A40 2018/12/24 (Linux/32)
* Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)

I'm using linux. I followed the Mystic Wiki guide, but Mystic will throw
a runtime erorr when the libcl.so file is placed in /usr/lib.

Are you certain you are using the proper bit level? The cryptlib you have
must match the bit level of Mystic (32-bit Mystic = 32-bit Cryptlib)

The only time I have seen runtime errors is when Mystic does not match the bit level of SDL2, Cryptlib, or Python. That will make it crash every time.

--- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Are you certain you are using the proper bit level? The cryptlib you
have must match the bit level of Mystic (32-bit Mystic = 32-bit Cryptlib)

The only time I have seen runtime errors is when Mystic does not match
the bit level of SDL2, Cryptlib, or Python. That will make it crash
every time.

I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib
and placing it into the directory as the instructions say.

Everything on this OS should be 32bit.

--- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
* Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)

I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib and placing it into the directory as the instructions say.

Everything on this OS should be 32bit.

Okay thanks.

I didn't have a Linux 32-bit installation, so I spent all day today getting one downloaded and setup so I can compile and test Mystic on it.

I can confirm I am seeing the same problem, but I don't have any more time at the moment to research the issue. I'll try to get a fix or a solution out soon. One thing I haven't tried was using an older version of Cryptlib but I have no idea if that would even work.

I'll try to spend some time on it tonight or tomorrow. Looks like I am going to need to get an A42 our soon.

--- Mystic BBS v1.12 A42 2018/12/28 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib and placing it into the directory as the instructions say.

Everything on this OS should be 32bit.

So before I jump into working on the latest Cryptlib, I compiled an older version (3.4.3) and that seems to work just fine with Mystic no crashing.

I am wondering if the problem is with the newer Cryptlib itself on the 32-bit systems. Many Linux distributions are no longer shipping 32-bit versions so it could be they aren't actively testing with it.

I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

Windows seems to not have this same problem, and I have not tested Pi or
macOS yet to see how those systems fare

--- Mystic BBS v1.12 A42 2018/12/28 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/28/18, g00r00 said the following...

I am wondering if the problem is with the newer Cryptlib itself on the 32-bit systems. Many Linux distributions are no longer shipping 32-bit versions so it could be they aren't actively testing with it.

I dont recall what the original issue is. But on a Pi, running Raspbian it is 32-bit - and I have used 3.4.3.1(? sorry whatever was originally on the wiki) and 3.4.4.1. I need to double check which one I'm using now when I get back from holidays.

Not sure if this helps you above?

BTW: For Debian Systems, I've made a deb out of both of them for x86_64 and armv7l.

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

Windows seems to not have this same problem, and I have not tested Pi or macOS yet to see how those systems fare

i will give this a shot as soon as i have a few mins

--- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
* Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)

I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

So Mystic appears to be working with this version. However, even though it
says it was a success emailing the code out, I don't actually get the email.

--- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
* Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)

So Mystic appears to be working with this version. However, even though
it says it was a success emailing the code out, I don't actually get the email.

You might want to review the node log first as the SMTP connection is logged there. But if its reporting success that should mean the server accepted the message and said it was successful... At that point its not up to Mystic anymore what happens.

It could be that your SMTP server is refusing to relay the message for some reason or other? Or maybe it failed and Mystic is reporting a false positive but I would think it'd be more on the former issue as SMTP servers are
probably pretty strict with sending e-mail in order to combat spam senders.

--- Mystic BBS v1.12 A42 2018/12/31 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)