E-Mail Sending Has Stopped Working On Hardware Devices
-
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Pete-S said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
In most cases like this, we run a Postfix server on Fedora that accepts unauthenticated port 25 from the devices and then sends out authenticated through O365 or whatever. Often that's the only way.
Feels like a smtp relay for sure is the best way to handle networks where you have devices sending email.
Just imagine changing ISP or whatever and then have to go through all email capable devices to make sure they now have the proper outgoing email settings.
I believe this is going to be in my near future...just weird for it to BAM! and stop...makes me wonder if I have a network issue...I had a feedback loop a few months ago that drove me crazy until I could finally locate it...
feedback loop?
-
-
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
Thank you...that was helpful...it looks like I did set it up correctly...that said, I do not have options like in this photo below...
-
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
Thank you...that was helpful...it looks like I did set it up correctly...that said, I do not have options like in this photo below...
That looks like an on prem screenshot. Office 365 does not have a screen like that.
Edit: Yup. Here is Exchange 2013 ECP.
-
Post everything you did to test.
[jbusch@dt-jared ~]$ nslookup -type=mx bundystl.com Server: 10.254.103.4 Address: 10.254.103.4#53 Non-authoritative answer: bundystl.com mail exchanger = 0 bundystl-com.mail.protection.outlook.com. Authoritative answers can be found from:[jbusch@dt-jared ~]$ telnet bundystl-com.mail.protection.outlook.com 25 Trying 104.47.48.36... Connected to bundystl-com.mail.protection.outlook.com. Escape character is '^]'. 220 CO1NAM05FT012.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 1 Aug 2019 15:52:15 +0000ehlo 250-CO1NAM05FT012.mail.protection.outlook.com Hello [207.244.223.13] 250-SIZE 157286400 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 SMTPUTF8mail from:<[email protected]> 250 2.1.0 Sender OK rcpt to: <[email protected]> 250 2.1.5 Recipient OKdata 354 Start mail input; end with <CRLF>.<CRLF> Subject: Test SMTP Test Message . 250 2.6.0 <f9a30b1f-7517-4a63-8fe2-7ea58eeae635@CO1NAM05FT012.eop-nam05.prod.protection.outlook.com> [InternalId=2173253459470, Hostname=DM6PR07MB4618.namprd07.prod.outlook.com] 9295 bytes in 5.960, 1.523 KB/sec Queued mail for delivery quit 221 2.0.0 Service closing transmission channel Connection closed by foreign host. [jbusch@dt-jared ~]$
-
@JaredBusch Not sure if more impressed that you made all those screenshots, or horrified at how Microsoft buried that setting.
-
@travisdh1 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch Not sure if more impressed that you made all those screenshots, or horrified at how Microsoft buried that setting.
It's not buried. it is right there. Just lots of clicking.
You can do it all with PowerShell also, but I don't know the commands. I do not set up enough connectors to have ever bothered to learn that.
This is a once and done, for the most part, at a client.
-
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
data
354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test SMTPTest Message
.Here are my results...
-
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
-
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
-
This post is deleted! -
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld...
-
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld...
Oh, you were using an old O365 IP address? Yeah - that's what sucks about using IPs instead of DNS entries. If you change the IP, you have to change everything that points to it... but if you use a DNS entry instead... they change where it points and all remains good.
-
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
Thank you...that was helpful...it looks like I did set it up correctly...that said, I do not have options like in this photo below...
That looks like an on prem screenshot. Office 365 does not have a screen like that.
Thanks Jared, I completely missed this in his question :flushed_face:
"We use Exchange Online with our Office 365 account and it is 100% cloud based"
-
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld...
Oh, you were using an old O365 IP address? Yeah - that's what sucks about using IPs instead of DNS entries. If you change the IP, you have to change everything that points to it... but if you use a DNS entry instead... they change where it points and all remains good.
The sad thing is. I used the DNS entry during all of this troubleshooting and it would never take it.
-
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld...
Oh, you were using an old O365 IP address? Yeah - that's what sucks about using IPs instead of DNS entries. If you change the IP, you have to change everything that points to it... but if you use a DNS entry instead... they change where it points and all remains good.
The sad thing is. I used the DNS entry during all of this troubleshooting and it would never take it.
yeah, I've seen that before, crappy printers.
-
can we get some tags added to this?
o365
scan2email
receiveconnector
