Re: End of Gmail: May 30th 2002?
We made the decision several years back not to support scan to email for any customer that didn't use an email account that was part of their regular domain. We had a few get a little angry at first, but when we made our case, they saw the logic of the decision.
I've had several customers hit in the past with emails with attachments that were supposedly a scanned file but were in fact malware. Every one of them came from some kind of consumer email account like gmail, hotmail, or yahoo.
As cheap as email hosting has become there's very little reason for not having a dedicated account for such devices, or at least a group email that a machine account has permissions to send from.
Using your own account on a customer's device opens up a whole pile of legal liabilities since their files and potentially proprietary or private information are being sent from an account they do not have control over. If you've done it, make sure you move it off now.
For any customer that we are not responsible for all IT services, we will give the customer their potential options and show their support staff how to configure and update settings for scan to email and also have them sign a document that they are solely responsible for all data transmitted using the feature. Just like implementing SMB1, or setting up rogue FTP servers you're just asking (BEGGING) to be sued when something goes wrong.
Sent from my BlackBerry using Tapatalk
We made the decision several years back not to support scan to email for any customer that didn't use an email account that was part of their regular domain. We had a few get a little angry at first, but when we made our case, they saw the logic of the decision.
I've had several customers hit in the past with emails with attachments that were supposedly a scanned file but were in fact malware. Every one of them came from some kind of consumer email account like gmail, hotmail, or yahoo.
As cheap as email hosting has become there's very little reason for not having a dedicated account for such devices, or at least a group email that a machine account has permissions to send from.
Using your own account on a customer's device opens up a whole pile of legal liabilities since their files and potentially proprietary or private information are being sent from an account they do not have control over. If you've done it, make sure you move it off now.
For any customer that we are not responsible for all IT services, we will give the customer their potential options and show their support staff how to configure and update settings for scan to email and also have them sign a document that they are solely responsible for all data transmitted using the feature. Just like implementing SMB1, or setting up rogue FTP servers you're just asking (BEGGING) to be sued when something goes wrong.
Sent from my BlackBerry using Tapatalk
Comment