SMTP Gmail issue

[Elcid]

Having issues with gmail. This was working 3 days ago. I updated to nodejs14 and for some reason had to reinstall MSR I did not have backup of notification.yaml, so re-entered the settings. The log is showing the smtp call is timing out. Any Ideas. I turn logging to 6 but no aditional info.

[CatmanV2]

Have you tried connecting to the configured server direct from a command line? What options are you passing in the yaml file?

C

[Elcid]

notification:
  # Alert is the system-default notification method that displays an alert
  # in the Status tab of the UI. It has no options.
  Alert: {}

  # SMTP (Simple Mail Transfer Protocol, for sending email)
  SMTP:
    profiles:
      default:
        # description - A friendly description of this profile (for menus)
        description: main email
        #
        # host - Hostname or IP address of SMTP server. Default: localhost
        host: "smtp.gmail.com"
        #
        # port - Port on which to make connection. The typical values are 25,
        #        465, and 587. Port 25 is usually only usable for local (LAN)
        #        servers, as some ISPs block it for SPAM control. Port 465 is
        #        usually for SSL/TLS-originated connections to the MTA, and
        #        port 587 is for STARTTLS to the MTA. If you're not sure, it's
        #        usually best to start with 587. Default is 25.
        port: 465
        #
        # allow_invalid_cert - if true, self-signed certificates are accepted
        #                      on secure connections; otherwise, they are not
        #                      verified.
        #allow_invalid_cert: true
        #
        # sender - email address to be used in "from" field of messages. The
        #          default is "username+reactor@hostname" where username is
        #          the user under which the Reactor service is running.
        sender: "********@gmail.com"
        #
        # default_recipient - email address to use when no recipients are spec-
        #                     ified in the Notify action. This can be a list of
        #                     comma-separated values. Default: sender address.
        default_recipient: "*******@gmail.com"
        #
        # default_subject - default subject if the notification does not provide
        #                   one.
        default_subject: "Notification from Reactor"
        #
        # username and password - for authentication with the MTA. If not given,
        #                         no login/auth is attempted (often acceptable
        #                         for connections to local/LAN servers).
        username: "*****@gmail.com"
        password: "dddjdyyyddkfuyydysb"
        #
        # auth_method - Future. Don't uncomment or modify the line below.
        #auth_method: "PLAIN"
        #
        # secure: if true, an SSL/TLS connection is established to the specified
        #         port. If false, STARTTLS is attempted after connecting. It is
        #         usually NOT necessary to uncomment and use this value; please
        #         not uncomment it unless advised to do so.
        #secure: false
        #
        # ignore_tls - if true, STARTTLS is not used even if the server
        #              advertises its support. This is sometimes useful for MTA
        #              connections to servers on trusted/local/LAN networks.
        #ignore_tls: false

[Elcid]

I get no response from
openssl s_client -connect smtp.gmail.com:465

if i leave it a minute i get

4024960164:error:0200206E:system library:connect:Connection timed out:crypto/bio/b_sock2.c:110:
4024960164:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
connect:errno=110

I have googled error and it suggests the wrong port or server is refusing secure connections on that port.
465 is the standard gmail smtp port that i use in reactor.

[toggledbits]

I can connect to smtp.gmail.com on 465 fine from where I am (using openssl as you gave it), so it suggests either a temporary routing failure of your upstream or maybe incorrect network configuration on your network (incorrect netmask, firewall/filtering, etc.).

[Elcid]

Ok, that got me thinking, turns out app password is being blocked when vpn is on, this hasbeen working for over a year. They really are making vpn's more difficult

seems google is blocking ipvanish maidenhead servers, I have moved back to london as they are still working.

[CatmanV2]

That would do it. Glad you're sorted, although why do you want to use a VPN to connect to them?

C

[Elcid]

So my ISP does not get a record of my internet interactions, also it stops them throttling my connection my upload speed goes from 1.3 to 5 when connected to a VPN all for $39 a year unlimited with 500gb cloud storage

[parkerc]

Hi @Elcid do you recommend IPVanish?

[Elcid]

Yes the connection is very stable my 35 mb /10mb connection gets 30/1.2 normally from my ISP
when connected to VPN I get 20-28 /5mb. and connection is stable very rarely do I get VPN connection issues.
There help desk response time is pretty good to. The VPN is unlimited downloads and devices.
I have also got 80mb when downloading multiple files simultaneously
They also have split tunneling so you can bypass VPN for certain apps, and you can allow local lan access without VPN

[gwp1]

I've been using IPVanish for a couple three years now. I have had success with it. Little pricey but seemingly more stable than others.

[Elcid]

How is $39 a year pricey?

[gwp1]

@elcid You should review their pricing. $39 for the first year... future years it's ~$80. I've been with them a couple three years now.

[Elcid]

@gwp1 I have been with them for 3 -4 years and never paid more than $4 a month. I have haggle every year and I get an offer every year, but this year I just used a different email address.