kryanC
asked on
Exchange 2010 Relay Connectors for Scan and email copiers
I have a need to allow scanning and email via three different scanners. They are all within the same domain but will need to email outside of it. Also, it is requested that they have access to the address book on the scanner.
I have an Exchange 2010 SP3 environment.
how do I set the relay connector to ensure it can reach outside our domain and get the address book onto the scanners. Or is the address book access more of a setup on the scanners themselves.
Am I on the right track thinking I need to create a new relay connector and do I need one for each scanner, and do they need their own ports?
Sorry for such a lame question but I just got blindsided with this and a very small window to do it. In
Thanks
Kry
I have an Exchange 2010 SP3 environment.
how do I set the relay connector to ensure it can reach outside our domain and get the address book onto the scanners. Or is the address book access more of a setup on the scanners themselves.
Am I on the right track thinking I need to create a new relay connector and do I need one for each scanner, and do they need their own ports?
Sorry for such a lame question but I just got blindsided with this and a very small window to do it. In
Thanks
Kry
Amit
You need only one relay connector.
We have a similar setup requirement for scan to email on various devices. Not sure if you have additional security requirements than we do, but I accomplished this by setting up a new user account within Exchange. i.e. C6000s@mydomain.com
Then use that account within the scanners. It will allow you to connect to address books (if scanner can use LDAP lookups) otherwise the address book might be a separate setup depending on the device capabilities.
I would not recommend setting up a relay connector for this setup.
Then use that account within the scanners. It will allow you to connect to address books (if scanner can use LDAP lookups) otherwise the address book might be a separate setup depending on the device capabilities.
I would not recommend setting up a relay connector for this setup.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@amitkulshrestha like most, I am not a big fan of Anonymous relays...
But if you must allow anonymous relays, I would add one more step after #7 of your instructions:
7) Click on Permission Group> Select only Anonymous User and uncheck others and click apply ok.
8. On the Relay tab, select Only the list below, type the IP addresses of the client computers (LOB applications ) that will be sending email messages, and then click OK.
But if you must allow anonymous relays, I would add one more step after #7 of your instructions:
7) Click on Permission Group> Select only Anonymous User and uncheck others and click apply ok.
8. On the Relay tab, select Only the list below, type the IP addresses of the client computers (LOB applications ) that will be sending email messages, and then click OK.
ASKER
Ok so here is where I am. I can see the scanner, and scan/email to anyone within my domain fine. Outside though and it fails. We traffic through outside dns so giving a local dns record with the same IP seems risky. Real time environment and if I make it hiccup I am dead. So, how do I get this to go outside our domain sending the scanned email?
Please!
Please!
Which method are you using? Anonymous relay or an authenticated user account?
ASKER
Anonymous,
ASKER
My other relay service reach out without issue: like my RMFT.
Sorry I am not sure what you mean with other relay service..."like RMFT" ?
FYI, I know that Comcast will allow their business class customers to use their SMTP as a relay for this type of scenario.
Not sure if your ISP's (DNS and SMTP) will allow this too, but it may be worth a try. Not really a big risk since it will either make it out, or get denied. Using ISPs external SMTP makes for a lot of hops to get email delivered back into your domain, but...
FYI, I know that Comcast will allow their business class customers to use their SMTP as a relay for this type of scenario.
Not sure if your ISP's (DNS and SMTP) will allow this too, but it may be worth a try. Not really a big risk since it will either make it out, or get denied. Using ISPs external SMTP makes for a lot of hops to get email delivered back into your domain, but...
The reason it will work for internal users is because that isn't relaying.
The primary reason it fails is that you haven't got the permissions right, or the scope of the connector is wrong and it is using the wrong one.
Simon.
The primary reason it fails is that you haven't got the permissions right, or the scope of the connector is wrong and it is using the wrong one.
Simon.
ASKER
Thanks to everyone here. Along with the suggestions I also had to make sure the Print policy on the Machines were enabled as well. I read two article saying MS assumes you have done this. Well enough said about the word assume. Anyway, thanks for the steps Amitkulshrestha and everyone who contributed.
Kry
Kry