Scan to Email, MP C3001

[Notrons]

Scan to email was working fine, one day and not working the next. Using port 587 (also tried 25 and 465), TLS is set up correctly though WIM, STMP/Auth info are good. Firmware is up to date. When I do a connection test, I get successful connection. Yet, when I try to scan, I get transmission failed. Log just says SMTPC connection closed.

Any ideas?

[NeoMatrix]

Scan to email was working fine, one day and not working the next. Using port 587 (also tried 25 and 465), TLS is set up correctly though WIM, STMP/Auth info are good. Firmware is up to date. When I do a connection test, I get successful connection. Yet, when I try to scan, I get transmission failed. Log just says SMTPC connection closed.

Any ideas?

Operating system.........
Mail server system.............
TLS Certificate up to date ?
Password changed ?
Firewall changed ?
Company external email access allowed?
Is GMAIL using two type confirmation settings?

[Notrons]

Operating system.........
Mail server system.............
TLS Certificate up to date ?
Password changed ?
Firewall changed ?
Company external email access allowed?
Is GMAIL using two type confirmation settings?

Sorry, cant answer most of those questions. What I do know, is that this is our office machine and nothing downstream from the copier to our server/modum was changed. Nothing on our end has changed, so looks like something did change on the email provider side.

[bsm2]

TLS change from MS office 365 to 2.0 your machine is most likely 1.0 may need a firmware update if available or they can setup a mail relay IE connector in office 365

What's the mail server are they using?

[NeoMatrix]

Sorry, cant answer most of those questions. What I do know, is that this is our office machine and nothing downstream from the copier to our server/modum was changed. Nothing on our end has changed, so looks like something did change on the email provider side.

Okay no worries, we're use to guessing....

<Shaking in my boots>
I'm about to ask the CTN guys for the latest firmware update for my crystal ball, its not working at the moment.

[Notrons]

TLS change from MS office 365 to 2.0 your machine is most likely 1.0 may need a firmware update if available or they can setup a mail relay IE connector in office 365

What's the mail server are they using?

The last time anything network related was updated by Ricoh, for this machine was in 2013. You might be right about TLS being v1.0. I just checked and there is no indication what version it is.

Our email is being provided by our ISP using our own domain.

[sandmanmac]

Our email is being provided by our ISP using our own domain.

Best contact them then and ask.
Not sure if that model supports TLS or not. If not, there are scads of unencrypted alternatives to configure scan to email regardless of your provider.

[slimslob]

Best contact them then and ask.
Not sure if that model supports TLS or not. If not, there are scads of unencrypted alternatives to configure scan to email regardless of your provider.

I don't think it does. If it does then I am sure that it does not support StartTLS. Too old.

Check the ISP to see if they provide a port 25 relay server option.

[JayPaul]

Check the ISP to see if they provide a port 25 relay server option - I second that idea
This may be a weird one but I have had something happen with scan to email a couple of times lately. One of them I think suddenly dropped the exception it had for the IP address, put it on DHCP and let it find it's own address and scan to email started working again instantly. This could be worth a try it will only take a minute to do.

[NeoMatrix]

Check the ISP to see if they provide a port 25 relay server option - I second that idea
This may be a weird one but I have had something happen with scan to email a couple of times lately. One of them I think suddenly dropped the exception it had for the IP address, put it on DHCP and let it find it's own address and scan to email started working again instantly. This could be worth a try it will only take a minute to do.

MFD probably lost its DNS server IP. DHCP would have reallocated the old DNS-IP or set up another one.