E-Mail Sending Has Stopped Working On Hardware Devices
-
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
-
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
-
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
-
@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:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
If you screen shot your connector, @JaredBusch might have time later to look at it compared to his.
-
@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:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
With the connector in place, something I would try is - try telneting to port 25 from your PC and see if you can go through an entire send process from your PC (On the same network as the printer/AIO device).
-
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@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:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
With the connector in place, something I would try is - try telneting to port 25 from your PC and see if you can go through an entire send process from your PC (On the same network as the printer/AIO device).
This is what I got when telnet with port 25..didn't get past the Mail From:
mail from: [email protected] 530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM [DM5PR05CA0003.namprd05.prod.outlook.com] -
OK, that's what the connector is supposed to fix. authentication is IP based instead of username/password based.
did you confirm that your PC's external IP is the same as the IP you provided in the connector? (google - what's my IP?)
-
@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.
-
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
OK, that's what the connector is supposed to fix. authentication is IP based instead of username/password based.
did you confirm that your PC's external IP is the same as the IP you provided in the connector? (google - what's my IP?)
Yessir...shows correct IP Address.
-
@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...
-
@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.
This is wrong. There’s no issue because I connector validates by your IP. If you get a new ISP you update the IP. That’s it done. A relay is useful so that you only need to send out from one local device, and thus you can blacklist SMTP out for everything except that One device. But that is not directly related to sending email out via a connector.
-
@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...
I use the relay simply because port 25 is not allowed to be sent out of my network except from the relays IP address. You do not have that restriction, so you do not need a relay for that reason. You have obviously set something up incorrectly in your connector. I’m driving home tonight but I can screenshot mine and/or other clients tomorrow
-
What's the security on your connector?
Should include anonymous
-
@JasGot said in E-Mail Sending Has Stopped Working On Hardware Devices:
What's the security on your connector?
Should include anonymous
That may be part of the problem...I do not see these options for my connector...is it on a different screen? I also didn't see these options when setting up the connector.
-
@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.
