Konica Minolta C3350 - scan to email

[Kenny]

hi guys,

got a weird one, a user is trying to scan to email on their C3350. The very first document works fine sends through straight away, if they then try send a scan to email after that they all fail in till the machine is turned off/on.

they have a C658 with the exact same set up and that works perfectly fine.

the C3350 has the latest firmware on.

could this be a HDD fault? or does the machine need a self signed cert?

any suggestions?

[Synthohol]

Re: Konica Minolta C3350 - scan to email

honestly id try a different smtp server just to see if its an issue with the email acct its trying to use or a transmission issue with the copier.
easy test..

[emujo2]

Re: Konica Minolta C3350 - scan to email

You need to provide a little more info..What is the error in the job log during a failure? I'm betting it's a disk full, or relay error message. Someone on your IT side needs to get onto the mail server and see what is happening while the C3350 is scanning..A tougher, but better for the actual answer would be to wireshark/mirror the MFP port. This will narrow it down to what, why and when your little packet of data was not able to get to the mail server..

[rrrohan]

Re: Konica Minolta C3350 - scan to email

You need to provide a little more info..What is the error in the job log during a failure? I'm betting it's a disk full, or relay error message. Someone on your IT side needs to get onto the mail server and see what is happening while the C3350 is scanning..A tougher, but better for the actual answer would be to wireshark/mirror the MFP port. This will narrow it down to what, why and when your little packet of data was not able to get to the mail server..

[Kenny]

Re: Konica Minolta C3350 - scan to email

details:

smtp.office365.com
start TLS
Port 587
added googles DNS and theirs,
created an SSL Cert
turned off all TLS apart from TLS1.2 AND SSL 3.0
the device email address is the same as admin address, they also use the address for authentication.
encryption strength is AES-256,3DES-168,RCA-128
updated to latest firmware.

I am going to site today to try your suggestions


is there anything else i am missing?

[B0265]

Re: Konica Minolta C3350 - scan to email

Is the SSL cert SHA-2?

[Gift]

Re: Konica Minolta C3350 - scan to email

The C3350 came with a weirdo controller back then

Enabled IPv6 can cause such issues from my experience.

[Kenny]

Re: Konica Minolta C3350 - scan to email

I think it might actually be a machine issue?

tried to also set up to GMAIL and sends one then doesn’t send

I’ve also formatted the machine, re configured the machines details, updated firmware again but just won’t work

[Synthohol]

Re: Konica Minolta C3350 - scan to email

i had half a dozen machines at a school do this and it turned out that the time and date were more than 5 minutes off from the email server time.
we set the time manually to match the smtp server and it just sort of worked after that.

[rrrohan]

Re: Konica Minolta C3350 - scan to email

did u use app password or account password

[ltdiniz]

Re: Konica Minolta C3350 - scan to email

Hello colleague Kenny, I already had a case similar to yours and the e-mail transmission error defect was like this.
Printer 1 bizhub C308 had the Relay SMTP enabled for the IP 192.168.100.200 on the client's SMTP server ok, and Printer 2 bizhub C558 did not have the Relay option enabled on the SMTP Server for SMTP transmission to the IP 192.168.100.202 and in this case the server blocks the immediate e-mail transmission.
Have you already checked this?
I hope I helped with the tip.

[Kenny]

Re: Konica Minolta C3350 - scan to email

the time and date are fine with the machine,

i haven't looked at the SMTP settings but will look into this, would this be the case for office365 and Gmail? pulling my hair out with this one

[Kenny]

[femaster]

Re: Konica Minolta C3350 - scan to email

That will definitely give you intermittent scanning issues. Hopefully that is all that it was.

[rrrohan]

Re: Konica Minolta C3350 - scan to email

guy using that PC must never bothered reporting the IP conflict warning that would of been popping up on PC