test unsuccessfull scan to email LaserJet MFP M477fdw

[jdoza15]

Hi, I'm having an issue with the scan to email function.  I've setup scan to email for a set of users but 3 of them I'm getting the "Test was unsuccessful. Try again".  I have all the same smtp server settings and the correct smtp authentication credentials as well.  I've verified by logging into webmail as the users and the usernames and passwords are correct.  Is there a way to get into some low level logging to see exactly what the issue is?  The error message provided by the printer is very generic.  I have all the users setup the same way but only 3 users are having this issue when I run the test.  The others complete fine.  Please advise.

[jdoza15]

I guess no one has ever come across this issue?

[Copier-Pro]

Hi I would like to assist to the best of my ability to solve your problem.I hope the information i supply will be of help.

I haven't got to the solution to this problem yet,but it seems like it could be the updates of the operating system that causes this.Although HP does not recommend 3rd party software i tried file zilla server with some success.This might just help you to solve this.Hope this will help.

[Graham_Wharton]

I know it is a bit late now, but deep in the menu structure somewhere, is an SMTP Communication Report, which will give you a plain text output of the SMTP conversation the printer had with your mail server. This helped me as my mail server was reporting that it supported CRAM-MD5 login, which the printer tried to use, but my server was misconfigured for. Logging into the mail server using other clients didn't use CRAM-MD5 so the error was difficult to track down.

Hope this helps

[JustinMaxwell]

Unfortunately, I can't seem to find that SMTP report anywhere.

I even have Syslog set up capturing printer log output, and there are no entries added when I test the outgoing email profile.

Just "The test was unsuccessful. Try again."  

Going slowly mad.

MFP M426fdw FWIW

[eCorbett]

Same here. I believe last time I came across this the fix was a firmware upgrade (due to TLS / SSL changes) but this time the printer already has the latest firmware.  Has to be something within Exchange Server but I can't find it.  Logging is difficult.  Using a local ISP email service works fine but isn't the solution in our situation.

[eCorbett]

Found the problem and solution, at least as it pertains to using Microsoft Exchange server.

Digging deeper through the logs, searching for source IP address, first we see the initial “Client Front End <servername>” logging receiving the connection.

C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive

It then passes the client over to the “Client Proxy <servername>” which is part of the hub transport logs.  “Proxy session was successfully set up. Session for <username> will now be proxied”

C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog\SmtpReceive

Searching by source IP address in the hub logs, I could see the error “Client does not have permissions to send as this sender,” which really makes no sense to me as the connection has gone past the “front end transport” of Exchange.

At any rate, adjusting permissions on the Client Proxy receive connector (via ADSIEdit) seems to have solved the problem.

https://somoit.net/exchange/exchange-smtp-error-550-5-7-1-client-not-permissions-send-sender

Corbett.

[JustinMaxwell]

Cross-posting here incase useful:

 If I enter the Google Restricted Gmail SMTP server IP address ( 108.177.104.26 ) rather then it's DNS name (aspmx.l.google.com) the Outgoing Email Profile works(!!!),

The printers DNS server settings have been pointing at Google (8.8.8.8 & 8.8.4.4) forever, so it's clearly some bug in HPs firmware (what a surprise, not!).  I have confirmed that adding IPv6 DNS resolvers doesn't change anything.

That's four hours of frustration I could have done without.  Hopefully, if this bug is impacting you, you found this thread sooner than that!

[ErtjeTheFreeze]

About not resolving via DNS: I found out that I HAD to fill in the DNS server in the printer settings, as setting "default" didn't seem to work. In my printer (M281fdw) I've set the DNS to my home routers IP-address in Networking, Network identification, DNS Primary (IPv4)