Link to home
Start Free TrialLog in
Avatar of VCadmin2012
VCadmin2012Flag for United States of America

asked on

Sending external email from LAN copier

Hi everyone - I've followed the best practices way to allow a Ricoh aficio to scan to email .
Created an recv connector only for the ip of the Ricoh and it scans just fine to internal addresses. It won't however scan externally and exchange logs a relaying not allowed error on this receive connector. Te connector itself is an internal recv connector with no authentication checked and has anon and exchange servers ticked in permissions group.

Would appreciate any ideas as I think the setup is as it should be.
Cheers
ASKER CERTIFIED SOLUTION
Avatar of ArneLovius
ArneLovius
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of VCadmin2012

ASKER

Ok thanks for that - ill take a look after lunch.
Initially I dd have it set only for anon but then read somewhere to add also exchange servers.
If the recv connector is only set to receive from the LAN IP of the LAN scanner it shouldn't represent a major security concern, should it?
I would run it on a different port, that way its much harder for somebody to mistakenly allow access and turn you into an open relay.
Can I just specify the different port on the recv connector as well as the LAN scanner or is it more involved than that? And do I need to do anything else to send that recv connector to the external world? Would I still Need to keep the existing recv connector for internal scan to email then? (as this is working just fine and I don't want to create us another problem haha)
yes, just specify a different port, and configure the copier to send to that port.

all email will go over the same connection, the copier doesn't know which email addresses are local and which are remote.
Do I to use the power shell to add the command you first mentioned in your link? And how does it know which recv connector is the one to apply those anon relay perms to?
I'm working remotely today so excuse me if I've
Issued anything . I would've thought that the recv connected anon perms would've applied to through from the EMC settings
The link has instructions for adding the receive connector in the EMS and the EMC.
hi Arne, we tried this, i've been off sick and , am still getting an error from the ems.
originally i created the receieve connector in the console, but when i go to add the line for the shell i get this error : i was just going to use port 25 we knew both int and ext lan scanning was ok and then change it - my lan scanner is the .150 and exch box .is .3 appreciate your feedback


         Welcome to the Exchange Management Shell!


[PS] C:\Windows\system32>New-ReceiveConnector -Name "vc-ricoh" -Usage Custom -AuthMechanism ExternalAuthoritative -Permi
ssionGroups ExchangeServers -Bindings 192.168.1.3:25 -RemoteIpRanges 192.168.1.150
The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive conn
ector "VC-SBS1\vc-ricoh". A Receive connector must have a unique combination of a local IP address, port bindings, and
remote IP address ranges. Change at least one of these values.
    + CategoryInfo          : InvalidOperation: (VC-SBS1\vc-ricoh:ReceiveConnector) [New-ReceiveConnector], ConnectorM
   appingConflictException
    + FullyQualifiedErrorId : B5D39FED,Microsoft.Exchange.Management.SystemConfigurationTasks.NewReceiveConnector
[PS] C:\Windows\system32>