Just recently a customer scan to email stopped working. The mfp is a mx-4501 using the following SMTP settings:
smtp.gmail.com
port 587
smtp authentication is enabled using a gmail account
I realize that this machine does not support SSL and am curious if that has anything to do with the recent failure to scan. Any other ideas?
The connection test within the MX web page is successful however from the mfp I receive the typical scanning errors at the display.
What gives??
If your device or application does not support SSL - connect to aspmx.l.google.com on port 25.Originally Posted by teklife256
From this page: https://support.google.com/a/answer/176600?hl=en
I haven't tried it, so, I don't know if this will work or not.
"You can't trust your eyes, if your mind is out of focus" --
Just now read the details in the link. Entry in Spf record? Recipients must be gmail? There must be another workaround with this non-SSL machine. Right??
Yeah, I didn't understand that either - maybe one of the experts will post. There probably is a fix other that an upgrade.
"You can't trust your eyes, if your mind is out of focus" --
Maybe there is a custom frimwar out there. Yikes!
Use GMX instead.
Not familiar with that. Well have to Google. Insight?
Most endusers that scan to Gmail never actually log in to their account, so Gmail just cuts them off due to inactivity. All they have to do is log on once in a while, and clear out the spam. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
The Sender Policy Framework (SPF) is an open standard specifying a technical method to prevent sender address forgery. More precisely, the current version of SPF — called SPFv1 or SPF Classic — protects the envelope sender address, which is used for the delivery of messages. See the box on the right for a quick explanation of the different types of sender addresses in e-mails.
(There are other solutions that protect the header sender address or that do not care at all about who sent the message, only who originally wrote it.)
Even more precisely, SPFv1 allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain. The technology requires two sides to play together: (1) the domain owner publishes this information in an SPF record in the domain's DNS zone, and when someone else's mail server receives a message claiming to come from that domain, then (2) the receiving server can check whether the message complies with the domain's stated policy. If, e.g., the message comes from an unknown server, it can be considered a fake.
Once you are confident about the authenticity of the sender address, you can finally "take it for real" and attach reputation to it. While IP-address-based reputation systems like Spamhaus or SpamCop have prevailed so far, reputation will increasingly be based on domains and even individual e-mail addresses in the future, too. Furthermore, additional kinds of policies are planned for a future version of SPF, such as asserting that all of a domain's outgoing mail is S/MIME or PGP signed.
looks like google is adding extra security to their emailIf the users are not sending to a gmail or google apps account without ssl it now will not go through. Unless you use google smtp relay service which I think is a pay service. Check the connectivity forums as there as been threads about gmail not working recently from mfps. Try Blackcats' suggestion of going into the gmail account for the mfp and deleting messages and the such. Depending on when google added the "SPF" to the emails the mail servers down the line can't verify the address/domain of were the email is coming from.
On the mfp web page when you do the connection test, all it does is verify that the address of the mail server is a mail server.
this model support ssl authentication
Posting Permissions
Thanks: 
Likes: 
Dislikes: 
Reply With Quote
Bookmarks