Scan to email failure

[dc313zd]

Re: Scan to email failure

I still don't see how this is tied to Net Neutrality. .

Net Neutrality is NOT the bill of goods sold to the general public. The government now deems the 'internet' as a public utility and subject to more Federal regulation. Part of this regulation makes anyone unknowingly relaying SPAM as guilty as the perpetrator. Effects of this legislation started in January. Now, at least in my area, customers that have been scanning to email for 2-4 years with the same equipment and the same setup as was done from the install date are being blocked. Coincidence?

[dc313zd]

Re: Scan to email failure

They don't happen to be using satellite internet are they.

No, unfortunately this particular ISP has had a monopoly in this area until recently. In fact their DNS was hosed for about 2 weeks before they got a handle on it.

[rthonpm]

Re: Scan to email failure

It looks as though there's a throng of opinions stating that Net Neutrality would lead to MORE spam. Just two examples:

Net neutrality could hinder efforts to safeguard Web, worry security experts - CSMonitor.com

https://www.ltnow.com/the-flipside-of-net-neutrality/

It still sounds like you've got customers using a weak setup relying on an ISP SMTP server to send email for a domain that doesn't use the same server for its MX records and the like, or as the first post stated: a malware related botnet style relay attack. With the latter, you're likely looking at enough traffic that third party security tools are blocking the IP.

Stated simply: if JoeLawyer@lawoffice.com is using their ISP SMTP server to send their email, but the lawoffice.com domain's DNS MX record shows a different server then it's probably going to get blocked by any modern spam filtre and reported for inclusion on a blacklist.

Try using this site to see if your customer's email domain is being blocked and what their domain DNS shows as their email server or provider: MX Lookup Tool - Check your DNS MX Records online - MxToolbox

[dc313zd]

Re: Scan to email failure

Already there Brother, MXTOOLBOX is a godsend. The end game is for me to transition all these people to SMB/FTP scan and attach as an email. Slimslob posted that he can associate user emails with user codes which will use the actual senders email address instead of the default MFP address on Ricoh's. Unfortunately most of what I deal with doesn't have that option.

[rthonpm]

Re: Scan to email failure

Already there Brother, MXTOOLBOX is a godsend. The end game is for me to transition all these people to SMB/FTP scan and attach as an email. Slimslob posted that he can associate user emails with user codes which will use the actual senders email address instead of the default MFP address on Ricoh's. Unfortunately most of what I deal with doesn't have that option.

I only really deal with Ricoh devices so I guess I've been spoiled. The logic is generally to assign every user of the device the ability to both receive and send emails from the MFP, then by restricting the Scanner feature with a user code, when the user puts their code in to use the function, they're automatically set as the sender of the file. Where this method gets tricky is in Active Directory or other account methods where users change their passwords frequently. For these accounts, I generally recommend Scan to SMB with a service account, or some kind of similar AD account that can't log onto a workstation, with a static password to authenticate to the share. Changing passwords for email authentication gets a little ugly when users have to update their credentials every 60 days or so, especially on the terrible keyboards on most MFP's.

MXToolBox has been a great resource, though I also use the Android app DNS Tools on my BlackBerry and a few Android tablets since it will also give MX data through its email validation feature.

https://appworld.blackberry.com/webstore/content/19752450/?lang=en&countrycode=US

https://play.google.com/store/apps/details?id=appinventor.ai_icetreeandroid.DNSSniffer

[slimslob]

Re: Scan to email failure

Where this method gets tricky is in Active Directory or other account methods where users change their passwords frequently.

Active directory password change should not affect Scan to email unless they are using a local Exchange server and changing the password for the email account that is used to authenticate to the SMTP server. User code only enters the sender email address. It does not change the authentication with the SMTP server. If they are using a local Exchange server that is part of their Active Directory, there is only one password that would need to be changed. They can also set that user as password never expires. Many companies with Exchange servers usually do not require authentication to send from within domain. Many also do not set a size limit on any email that is going to stay within the domain.

[qbert69]

Re: Scan to email failure

Well I found one of my problems regarding a local ISP (Hargray). In their ULA they deem anything over 10mb 'heavy traffic'. Yesterday one of my customers emails from their MFP were being truncated, turns out they are scanning 80-100 pages with photos at 400 DPI.

Have them scan to themselves and then attach the scan at :

https://www.sendspace.com/

That should fix it for 'em!

[slimslob]

Re: Scan to email failure

No, unfortunately this particular ISP has had a monopoly in this area until recently. In fact their DNS was hosed for about 2 weeks before they got a handle on it.

They might want to try satellite then. Hughes Net is available internationally. When I was in Iraq in 2005, we had satellite internet in our rooms. Hughes Net was the ISP with DNS in Germany. Can be a little expensive but if there is only one local provider of internet it does give the customer some leverage power.
HughesNet International, WA | 1-866-641-8709

[kylebishop]

Re: Scan to email failure

Here is my instruction I made for myself. It's a little sloppy but I haven't the time to edit for you but I'm sure you can figure out the issue by reading thru this.

To Scan to E-mail MFX-3530:


Gmail:
Add the user in user registration. Add their e-mail and password info. Name/User ID keep the same name.
Add the user into Address book. Add their name and e-mail address. Keep the name the same as the user registration name.
Goto Machine settings, Email settings, SMTP/POP settings. Enter the users name, keep the name the same as user registration.
SMTP server address: smtp.gmail.com port 25.
SSL turn to on.
SMTPS port 465
Authentication turn to login.
SMTP authentication user name ?????@gmail.com "their email address".
SMTP authentication password. enter the users email password.
Do not enter any POP info.
Click save.
Make sure to add the users DNS address into the copier.
In their gmail settings they must change the setting "Allow less secure apps."turn to ON" found at Myaccount.google.com/security


Yahoo
smtp.mail.yahoo
port 465


Comcast
smtp.comcast.net
smtp port 587
ssl checked


Outlook
smtp.live.com
outgoing smtp port 587
ssl/tls required