Hello All,<u1:p></u1:p><o:p></o:p>

We have Exchange Server 2013 in my environment, and we have issue with Receive connector a scan to email, the technical support can configure the multi-function print device scan to email successful using Internal SMTP relay without any permission from the Exchange side.<u1:p></u1:p><o:p></o:p>

I Have the custom Received connector created before and also removed the default IP address range remote network settings.<u1:p></u1:p><o:p></o:p>

Any setting needs to check or to apply to prevent this type of scan to email ,  and only provide the permission to Multi-function print device or any device through the Exchange side.<o:p></o:p>

<u1:p>Thank you .</u1:p><o:p></o:p>

 

Hello,

I have explained about the creation of such a connector in my blog here: http://exchangeonline.in/smtp-server-error-5-7-1-unable-relay/

This is for Exchange 2010, and applicable for 2013 too

Thank you

No need to check box Anonymos users ?

Thank you again .

 

Hello ,

I  received  this error when try to send email using telnet

Remote
Server returned '550 5.7.1 TRANSPORT.RULES.RejectMessage; the message was
rejected by organization policy'

Thank you

Hi,

Check if some Transport Rules are blocking the email delivery.

Also add the domain name into "The sender's domain is" exception of anti spam transport rule

Hi ,

Yes there are Transport Rules its Ok now , but I have issue with custom recvice connector it is  can any device connected on the Network  relay internal smtp without any permission from Exchange side !!!

how can fix the issue ?

Thank you

• Edited by Mohammad B 15 hours 18 minutes ago aa

Hi ,

Yes there are Transport Rules its Ok now , but I have issue with custom recvice connector it is  can any device connected on the Network  relay internal smtp without any permission from Exchange side !!!

how can fix the issue ?

Thank you

• Edited by Mohammad B Sunday, July 12, 2015 4:10 PM aa

Hi ,

Yes there are Transport Rules its Ok now , but I have issue with custom recvice connector it is  can any device connected on the Network  relay internal smtp without any permission from Exchange side !!!

how can fix the issue ?

Thank you

• Edited by Mohammad B Sunday, July 12, 2015 4:10 PM aa

Hi Mohammand,

Thank you for your question.

By my understanding, if you want to any devices which connect to internal relay with any permission(if I misunderstanding, please be free to let me know). If that, we could check Basic Auth.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim , 

Thank you for your Reply.

Yes that what we need , after assign "Basic Auth" which services need to restart ?

I Have questions on the "Remote Network settings" on custom receive connector i removed all the default IP Range and only add  one Ip Address for the specific printer  but all others  printers can relay the Internal SMTP  Could you please help me for this issue ?

Best Regards , 

Mohammad .

Hi Mohammad,

We need not to restart any services.

Run the following command to check if we just have a one IP:

Get-ReceiveConnector Identity <receive connector name> | FL

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim ,

Yes thers one IP Address ---- look the result please

RunspaceId                              : fe74c6f1-9bf2-4263-a63c-4e441159fe49
AuthMechanism                           : Tls, BasicAuth
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {0.0.0.0:25}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : CAS01..local
ServiceDiscoveryFqdn                    :
TlsCertificateName                      :
Comment                                 :
Enabled                                 : True
ConnectionTimeout                       : 00:10:00
ConnectionInactivityTimeout             : 00:05:00
MessageRateLimit                        : Unlimited
MessageRateSource                       : IPAddress
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 128 KB (131,072 bytes)
MaxHopCount                             : 60
MaxLocalHopCount                        : 12
MaxLogonFailures                        : 3
MaxMessageSize                          : 35 MB (36,700,160 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
PermissionGroups                        : ExchangeServers, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {10.50.1.1}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : CAS01
TransportRole                           : FrontendTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : connector
DistinguishedName                       : CN=connector,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=CAS01,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=my,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=,DC=local
Identity                                : CAS01\connector
Guid                                    : eb75de00-b92b-4064-b31f-531847df044e
ObjectCategory                          : .local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 7/13/2015 9:18:09 AM
WhenCreated                             : 7/12/2015 10:39:55 AM
WhenChangedUTC                          : 7/13/2015 6:18:09 AM
WhenCreatedUTC                          : 7/12/2015 7:39:55 AM
OrganizationId                          :
OriginatingServer                       : AD..local
IsValid                                 : True
ObjectState                             : Unchanged

Hi Mohammad,

Are there any other receive connector which was configured on Exchange server?

Run the follow command to check:

Get-ReceiveConnector | FL name,*RemoteIPRange*

Then we could check if the other printer was included in other receive connector.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim , 

Yes , there is Exchange "Default Frontend " . It is by default allow the printers or devices send email ?

BR,

Mohammad .

Hi Jim,

Please look below the result 

Name           : Default Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : connector
RemoteIPRanges : {10.10.50.1}

Name           : connector
RemoteIPRanges : {10.10.50.1}

• Edited by Mohammad B 21 hours 36 minutes ago l

Hi Jim,

Please look below the result 

Name           : Default Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : connector
RemoteIPRanges : {10.10.50.1}

Name           : connector
RemoteIPRanges : {10.10.50.1}

• Edited by Mohammad B Tuesday, July 14, 2015 9:53 AM l

Hi Jim,

Please look below the result 

Name           : Default Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Outbound Proxy Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Frontend CAS02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB01
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Default MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : Client Proxy MB02
RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Name           : connector
RemoteIPRanges : {10.10.50.1}

Name           : connector
RemoteIPRanges : {10.10.50.1}

• Edited by Mohammad B Tuesday, July 14, 2015 9:53 AM l

Hi Mohammad,

you could remove the IP of other printer on all receive connector to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim ,

I removed the IP of the printer , still the issue existing .

The default Exchange Receive connector by default allow Devices like printers send e-mail ?

Thank you for your help

Hi,

In order to troubleshoot, we could delete this internal reply to check if printer could send email.

If the printer didnt send email , we could rebuild it to check if the issue persiot.

If the printer still send email, we could collect trace message log and head information for troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim