Howdy,
Need some help in setting up scan to email when a customer is using Office 365? This is new to me. Does anyone have any ideas or documents that you can send to me?
Are there other ways to scan into Office 365?
Original Post
can't scan to email after switching to office365 from local exchange server
- 4 Followers
- 12 Replies |
- This post has 2 verified answers |
This question is answered  |
Posted
on 2011-Sep-29
3:05 AM
|
Hi All,
we used to have a local exchange server to handle all the emails, we just moved to the online office365.
Everything is working fine except scanning stuff to emails ( from our sharp printer ).
I've attached a screenshot for the settings.
I have also changed the SMTP port to 587, the port changing is on another page, not the page shown below.
Any help is appreciated.
Cheers,
Hubery
Verified
Answer
-
Postreplied on 2011-Oct-04 6:10 PMVerified Answer
Thanks guys for the help.
I have figured out the problem, there was one misconfiguration on the printer, the sender address configured on the printer is actually a email group name and it is not a valid account in the office 365. So when I changed it to be a valid user account, it just worked.
Cheers,
Hubery
-
Postreplied on 2011-Oct-06 12:20 AMVerified AnswerSure.
So let's name this email group as group@domain.com, and the valid account as user@domain.com. Here's the step-by-step procedure to achieve the same:
1. Create a Distribution Group on Office 365 console by the name: group@domain.com (Distribution Group, so that it doesn’t consume any license)
2. Grant Send-As permission to the user (user@domain.com) over this DL
a. Download the 32-bit or 64-bit Office 365 Module for Windows Powershell:
http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh124998.aspxb. Connect Windows PowerShell to the Service:
http://help.outlook.com/en-us/140/cc952755.aspxc. Grant SendAs permission using the following cmdlet:
Add-RecipientPermission -Identity “Group” -AccessRights SendAs -Trustee “User”You can verify if the SendAs permission has been successfully granted, by logging in to “User’s” mailbox, changing the FROM address as “group@domain.com”, and sending out a mail. Though the mail is sent out from your mailbox, the recipient would receive it as if it was sent by “group@domain.com”.
3. In the Sharp Printer, set the FROM address as “group@domain.com” (the email group name that was originally in there), and under SMTP Authentication you can use the credentials of “user@domain.com” (who was set as Trustee when granting the SendAs permission)
That should help. Keep us posted on the progress.
[For more info on Send-As permission, ref: http://technet.microsoft.com/en-us/exchangelabshelp/ff852815]
Regards,
Boney Francis
All Replies
-
Postreplied on 2011-Sep-29 5:28 AM
By default, Transport Layer Security (TLS) is required to be enabled on SMTP client. You may consult you scanner vendor to check if the device supports TLS. If not, you need to disable the TLS by using FOPE.
This thread may be helpful for you.
Scans forwarded to SMTP server
http://community.office365.com/en-us/f/158/p/5882/45797.aspx#45797Sky
-
Postreplied on 2011-Oct-03 2:46 AM
Hi Jack,
Sorry for the late reply.
No, I have followed Sky's suggestion, but still no luck.
As there is no place to set up TLS in the printer, so I just select "My outgoing server (SMTP) requires an encrypted connection (SSL) option." in the printer.
I am trying to contact our printer service provider to see if they have met the similar problem before.
If you have any suggestions, please feel free to let me know.
Thanks,
Hubery
-
Postreplied on 2011-Oct-03 8:51 AM
Hi Hubery,
1. If there are any connection logs on the Sharp printer, analyzing that would be the best way
2. If you still have your local Exchange server, you can continue to point the Sharp printer to the Exchange server, and from there direct the mails to Office 365
3. If the Exchange server has been decommissioned, an IIS box should do the trick (which will act as a relay device between the printer and Office 365)
4. If step-2 and step-3 is not feasible, loop back to step-1: you could provide us with the logs (if any)
Either ways, I'd be curious to know if the recipients of this mail from printer would all be internal recipients (users on your O-365 domain)? If so, you can have the printer configured with minimal settings and it would still work. If the recipients can/may be external as well, then we need to strictly stick with the discussed settings.
Most importantly, I'm presuming that you are able to receive normal external mails to your Office365 domain with no issues. If the domain is not receiving inbound, the printer wouldn't be able to send to the users email addreses either.
Best
Regards,
Boney Francis
-
Postreplied on 2011-Oct-04 6:10 PMVerified Answer
Thanks guys for the help.
I have figured out the problem, there was one misconfiguration on the printer, the sender address configured on the printer is actually a email group name and it is not a valid account in the office 365. So when I changed it to be a valid user account, it just worked.
Cheers,
Hubery
-
