Am I the only one with mail issues? [resolved...kind of]

[camerabob]

As of this weekend, I can no longer send any email from Cacti. I haven't changed a thing. SMTP from Cacti fails altogether. I have VZ FIoS service. Wondering if they have disabled SMTP form residential accounts.

[camerabob]

OK, so it seems the IP address I have acquired is on a blacklist. Some other clown must have spammed from it before it got handed to me.

[netniV]

So I'm guessing the answer is yes?

Not sure why you are sending from your residential address unless this is a small test farm. If so, you may want to consider creating a GMAIL account and then using authenticated sending through them (you may have to lower their internal security for it to work).

[camerabob]

VZ FIoS new terms of service state that only their SMTP servers can be used for sending email. I was using Gmail happily before they changed their terms. (probably around March 2 of this year...) Also they will not permit you to use any other name but the account holder's name on those outgoing emails. I'm OK using my name on them, but I simply couldn't get the VZ mail server to send anything from cacti which is why I used Gmail. Cacti said success, but I never received anything at all. My guess is that something in the server system wasn't liking something cacti said and it was silently dropped. Now nothing at all is working... This is a private installation for myself only, so I'm not concerned so much with the mail issue, but it's nice to know when my power fails long before the UPSs take a dive, or I run out of hard drive space on a server without having to sit and watch them.

[netniV]

You should be able to send mail through them as long as you use authentication. If you can do it from a PC, you can do it from Linux.

[camerabob]

I have to add this as a follow up. After your last post, I checked my home email which I haven't been into in quite a while. (darn iPhone...) My mail client was quite old and would not allow me to even download email via POPS. (Thunderbird is up to 52. I was on 13. There was an extension that I liked that wouldn't work with any version newer...) So I upgraded and pulled down all the waiting email and I then sent one back up to make sure all was working. I then tested Cacti again and the test email failed. I rebooted a device to clear an error on it and voila! I get a notification from Monitor that a device was rebooted. WTF??? I then changed an IP on a working device to force it to fail. I get another notification that it dropped and again when I changed it back that it returned. Test emails still fail. I am clueless, but at least I know the system works even though the test mechanism is wonky. So there is no root cause of the failed email for the past weeks. Aside from me changing the SMTP information from Gmail back to Verizon's SMTP server nothing else was done.

[netniV]

It sounds like Verizon are using their own firewalls to actively filter out any SMTP traffic that is not their own, thus forcing you to use theirs. I've seen ISPs do that in a bid to combat email spam since unless you have an active account on their smtp server, infected home machines wouldn't be able to sent mails out.

There was a bug fix in 1.1.37 related to disabling TLS from starting in a certain circumstance. Do you have a link to Verizon's mail settings (they would have a support page for it) ?

[camerabob]

I'm still on 1.1.36. I know their email settings by heart at this point in time:

inbound: POPS on port 995 @pop.verizon.net (or @incoming.verizon.net)
outbound: SMTPS on port 465 @ smtp.verizon.net, SSL enabled and password authentication
For VZ customers that migrated to AOL email, the user name is the full 'username@verizon.net' name

[netniV]

What settings do you have in the Mail/Reporting/DNS tab? I presume you are using SMTP and setting the SSL/TLS option, plus changing the port accordingly? It sounds like you know the settings quite well but I'm just want to be sure. If so, I can throw a test program together for you to see what's going on with PHPMailer.

[camerabob]

Here they are

mailer.png (148.34 KiB) Viewed 5533 times

error-smtp.png (15.47 KiB) Viewed 5533 times

error-sendmail.png (11.31 KiB) Viewed 5533 times

error-php.png (10.62 KiB) Viewed 5533 times

[netniV]

Try changing the option from SSL to TLS, then it may work.

[camerabob]

TLS gave same results...

[netniV]

Try using this PHP file. Copy it to the cli folder and then run from there using php test_mail.php

There will be a lot of output given, but hopefully it may give you some more insight in to why it's failing.

If there are any CLIENT -> SERVER: AUTH LOGIN lines, hide any output that follows (since these are encoded - not encrypt) lines containing username/password) until the SERVER -> CLIENT: 235 Authenticated

However, I am suspecting you are not even getting that far.
(Remember to rename the .txt to .php)

[camerabob]

That worked without a hitch. I received the test email (or text, rather) without issue. Output below:

Code: Select all

[root@CB-cacti cli]# php test_mail.php
Checking Configuration...Method: SMTP
Ping Results: Bypassed
Sending Message...2018-04-01 13:00:05   Connection: opening to ssl://smtp.verizon.net:465, timeout=10, options=array (
                                          )
2018-04-01 13:00:05     Connection: opened
2018-04-01 13:00:05     SERVER -> CLIENT: 220 vz-proxy-l005.mx.aol.com ESMTP ready
2018-04-01 13:00:05     CLIENT -> SERVER: EHLO CB-cacti.xxxxxxxxx.lan
2018-04-01 13:00:05     SERVER -> CLIENT: 250-vz-proxy-l005.mx.aol.com
                                          250-SIZE 36700160
                                          250-ENHANCEDSTATUSCODES
                                          250-8BITMIME
                                          250-DSN
                                          250 AUTH PLAIN LOGIN XOAUTH2
2018-04-01 13:00:05     CLIENT -> SERVER: AUTH LOGIN
2018-04-01 13:00:05     SERVER -> CLIENT: 334 xxxxxxxxxxxx
2018-04-01 13:00:05     CLIENT -> SERVER: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2018-04-01 13:00:06     SERVER -> CLIENT: 334 xxxxxxxxxxxx
2018-04-01 13:00:06     CLIENT -> SERVER: xxxxxxxxxxxxxxxx
2018-04-01 13:00:06     SERVER -> CLIENT: 235 2.0.0 OK
2018-04-01 13:00:06     CLIENT -> SERVER: MAIL FROM:<xxxsxxxxxxxxxxxx@verizon.net>
2018-04-01 13:00:06     SERVER -> CLIENT: 250 2.1.0 Ok
2018-04-01 13:00:06     CLIENT -> SERVER: RCPT TO:<xxxxxxxxxx@vtext.com>
2018-04-01 13:00:06     SERVER -> CLIENT: 250 2.1.5 Ok
2018-04-01 13:00:06     CLIENT -> SERVER: DATA
2018-04-01 13:00:06     SERVER -> CLIENT: 354 End data with <CR><LF>.<CR><LF>
2018-04-01 13:00:06     CLIENT -> SERVER: Date: Sun, 1 Apr 2018 09:00:05 -0400
2018-04-01 13:00:06     CLIENT -> SERVER: To: xxxxxxxxxx@vtext.com
2018-04-01 13:00:06     CLIENT -> SERVER: From: Robert Patterson <xxxsxxxxxxxxxxxx@verizon.net>
2018-04-01 13:00:06     CLIENT -> SERVER: Subject:
2018-04-01 13:00:06     CLIENT -> SERVER: Message-ID: <74a9007f30e0115f156841729ec7f67b@CB-cacti.xxxxxxxxx.lan>
2018-04-01 13:00:06     CLIENT -> SERVER: X-Mailer: PHPMailer 5.2.26 (https://github.com/PHPMailer/PHPMailer)
2018-04-01 13:00:06     CLIENT -> SERVER: MIME-Version: 1.0
2018-04-01 13:00:06     CLIENT -> SERVER: Content-Type: multipart/alternative;
2018-04-01 13:00:06     CLIENT -> SERVER:       boundary="b1_74a9007f30e0115f156841729ec7f67b"
2018-04-01 13:00:06     CLIENT -> SERVER: Content-Transfer-Encoding: 8bit
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: This is a multi-part message in MIME format.
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: --b1_74a9007f30e0115f156841729ec7f67b
2018-04-01 13:00:06     CLIENT -> SERVER: Content-Type: text/plain; charset=us-ascii
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: This is a test message generated from Cacti.  This message was sent to test the configuration of your Mail Settings
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: Your email settings are currently set as follows
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: Method: SMTP
2018-04-01 13:00:06     CLIENT -> SERVER: Device: smtp.verizon.net
2018-04-01 13:00:06     CLIENT -> SERVER: Port: 465
2018-04-01 13:00:06     CLIENT -> SERVER: Authentication: true
2018-04-01 13:00:06     CLIENT -> SERVER: Username: xxxxxxxxxxxxxxxx@verizon.net
2018-04-01 13:00:06     CLIENT -> SERVER: Password: (Not Shown for Security Reasons)
2018-04-01 13:00:06     CLIENT -> SERVER: Security: ssl
2018-04-01 13:00:06     CLIENT -> SERVER: Ping Results: Bypassed
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: --b1_74a9007f30e0115f156841729ec7f67b
2018-04-01 13:00:06     CLIENT -> SERVER: Content-Type: text/html; charset=us-ascii
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: This is a test message generated from Cacti.  This message was sent to test the configuration of your Mail Settings<br><br>Your email settings are currently set as follows<br><br><b>Method</b>: SMTP<br><b>Device</b>: smtp.verizon.net<br><b>Port</b>: 465<br><b>Authentication</b>: true<br><b>Username</b>: xxxxxxxxxxxxxxxx@verizon.net<br><b>Password</b>: (Not Shown for Security Reasons)<br><b>Security</b>: ssl<br><b>Ping Results</b>: Bypassed<br><br><br>
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: --b1_74a9007f30e0115f156841729ec7f67b--
2018-04-01 13:00:06     CLIENT -> SERVER:
2018-04-01 13:00:06     CLIENT -> SERVER: .
2018-04-01 13:00:07     SERVER -> CLIENT: 250 2.0.0 Ok: queued as 27B9338000088
2018-04-01 13:00:07     CLIENT -> SERVER: QUIT
2018-04-01 13:00:07     SERVER -> CLIENT: 221 2.0.0 Bye
2018-04-01 13:00:07     Connection: closed

Result: Success!
[root@CB-cacti cli]#

Could it be that I have something corrupt in my Linux install?

[camerabob]

OK. The problem is on my end. I have a second test install that was upgraded from 0.8.8h to the same 1.1.36. I put my email settings in there and I was able to send out a test email. The problem is somewhere in my OS. I'll have to dive in. Thanks for the assistance. I truly appreciate the level of help you provided me.

Bob

A quick afterthought: What module is used to send the test email? Maybe I could move that from the working install over since everything else seems to function.