[Exchange] Re: REceive connector Exchnage 2010
Me niether
Anti spam tab wasn't in the GUI
So had no reason to believe it had ever been active
But moment it was mentioned
I thought bet that's it
But it's sorted now
Thanks again
Graeme
On Saturday, 6 September 2014, Michael B. Smith mich...@smithcons.com
wrote:
I never would have guessed that.
*From:* listsad...@lists.myitforum.com
javascript:_e(%7B%7D,'cvml','listsad...@lists.myitforum.com'); [mailto:
listsad...@lists.myitforum.com
javascript:_e(%7B%7D,'cvml','listsad...@lists.myitforum.com');] *On
Behalf Of *Graeme Carstairs
*Sent:* Friday, September 5, 2014 1:06 PM
*To:* exchange@lists.myitforum.com
javascript:_e(%7B%7D,'cvml','exchange@lists.myitforum.com');
*Subject:* [Exchange] Re: REceive connector Exchnage 2010
Ok
Problem solved
A discussion with the previous system
Admin and he informed me that they were using exchange anti spam
When they moved to a hosted anti spam they co existed for a month and the
removed anti spam from exchange
Hence no anti spam in the GUI
Powershell commands to disable ip allow and up block list and it sprung
into life
Thanks to everyone for their help
Graeme
On Friday, 5 September 2014, Graeme Carstairs loonyto...@gmail.com
javascript:_e(%7B%7D,'cvml','loonyto...@gmail.com'); wrote:
Ok If I setup an SMTP relay listening onporn26
It accepts mail in but when it tried to forward Tor the exhange SMTP on
port 25 I get the same error192.168.10.2 does not have permission to send
to this server
I'm at my wit send the customer is losing the plot
Everything is set right
Even creating a login and trying that is failing
Any ideas
On Friday, 5 September 2014, Graeme Carstairs loonyto...@gmail.com
wrote:
I have tried all the changes suggested even adding a new ip into the
server nic
Creating a new connector bound to it
With the settings as described
Changed the nat and still getting the same error
There at be something else where stopping it
I'm going to stick mail relay software on listening on a different port
and get it to forward the mail locally
See if that works
Graeme
On Friday, 5 September 2014, Daniel Chenault dani...@hotmail.com
javascript:_e(%7B%7D,'cvml','dani...@hotmail.com'); wrote:
I dunno about that but as it stands, like I said earlier, your connectors
will only receive from internal addresses.
On Sep 4, 2014, at 16:21, Michael B. Smith mich...@smithcons.com
javascript:_e(%7B%7D,'cvml','mich...@smithcons.com'); wrote:
This is way SBS does things.
Sent from my Windows Phone
--
*From: *ccollins9
*Sent: *9/4/2014 7:10 PM
*To: *exchange
*Subject: *Re: [Exchange] REceive connector Exchnage 2010
U, is it me or are none of these connectors are set to receive from
0.0.0.0
- 255.255.255.255? Going to be hard to receive email from the internet if
all your connectors can only receive from a 192.168 address, no? You need
to set a receive connector to ip range 0.0.0.0-255.255.255.255 AND
permissions group 'anonymous'. For example, here's my output from our
internet connector:
PermissionGroups: AnonymousUsers
PipeliningEnabled: True
ProtocolLoggingLevel : None
RemoteIPRanges
: {::-:::::::, 0.0.0.0-255.255.255.255}
RequireEHLODomain : False
On Thu, Sep 4, 2014 at 6:00 PM, Michael B. Smith mich...@smithcons.com
javascript:_e(%7B%7D,'cvml','mich...@smithcons.com'); wrote:
You’ve got 3 receive connectors in your output. The first one doesn’t have
AnonymousUsers set on it. You probably want it to. Especially if you are
trying to, for example, accept non-authenticated email in the “Default
WC-SBS1” connector from IP addresses in the range of 192-168.10.0/24.
[1]
PermissionGroups: ExchangeUsers, ExchangeServers,
ExchangeLegacyServers
RemoteIPRanges : {192.168.10.255-192.168.10.255,
192.168.10.0-192.168.10.253}
Name: Default WC-SBS1
[2]
PermissionGroups: AnonymousUsers
RemoteIPRanges : {192.168.11.0-255.255.255.255,
192.168.10.254-192.168.10.254, 0.0.0.0-192.168.9.255}
Name: Windows SBS Internet Receive
WC-SBS1
[3]
PermissionGroups: AnonymousUsers, ExchangeUsers
RemoteIPRanges : {127.0.0.1-127.0.0.1}
Name: Windows SBS Fax Sharepoint
Receive WC-SBS1
*From:* listsad...@lists.myitforum.com
javascript:_e(%7B%7D,'cvml','listsad...@lists.myitforum.com'); [
mailto:listsad...@lists.myitforum.com
javascript:_e(%7B%7D,'cvml','listsad...@lists.myitforum.com');] *On
Behalf Of *Graeme Carstairs
*Sent:* Thursday, September 4, 2014 5:47 PM
*To:* exchange@lists.myitforum.com
RE: [Exchange] Re: REceive connector Exchnage 2010
I never would have guessed that.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Graeme Carstairs
Sent: Friday, September 5, 2014 1:06 PM
To: exchange@lists.myitforum.com
Subject: [Exchange] Re: REceive connector Exchnage 2010
Ok
Problem solved
A discussion with the previous system
Admin and he informed me that they were using exchange anti spam
When they moved to a hosted anti spam they co existed for a month and the
removed anti spam from exchange
Hence no anti spam in the GUI
Powershell commands to disable ip allow and up block list and it sprung into
life
Thanks to everyone for their help
Graeme
On Friday, 5 September 2014, Graeme Carstairs
loonyto...@gmail.commailto:loonyto...@gmail.com wrote:
Ok If I setup an SMTP relay listening onporn26
It accepts mail in but when it tried to forward Tor the exhange SMTP on port 25
I get the same error192.168.10.2 does not have permission to send to this server
I'm at my wit send the customer is losing the plot
Everything is set right
Even creating a login and trying that is failing
Any ideas
On Friday, 5 September 2014, Graeme Carstairs
loonyto...@gmail.comjavascript:_e(%7B%7D,'cvml','loonyto...@gmail.com');
wrote:
I have tried all the changes suggested even adding a new ip into the server nic
Creating a new connector bound to it
With the settings as described
Changed the nat and still getting the same error
There at be something else where stopping it
I'm going to stick mail relay software on listening on a different port and get
it to forward the mail locally
See if that works
Graeme
On Friday, 5 September 2014, Daniel Chenault
dani...@hotmail.commailto:dani...@hotmail.com wrote:
I dunno about that but as it stands, like I said earlier, your connectors will
only receive from internal addresses.
On Sep 4, 2014, at 16:21, Michael B. Smith
mich...@smithcons.commailto:mich...@smithcons.com wrote:
This is way SBS does things.
Sent from my Windows Phone
From: ccollins9
Sent: 9/4/2014 7:10 PM
To: exchange
Subject: Re: [Exchange] REceive connector Exchnage 2010
U, is it me or are none of these connectors are set to receive from 0.0.0.0
- 255.255.255.255? Going to be hard to receive email from the internet if all
your connectors can only receive from a 192.168 address, no? You need to set a
receive connector to ip range 0.0.0.0-255.255.255.255 AND permissions group
'anonymous'. For example, here's my output from our internet connector:
PermissionGroups: AnonymousUsers
PipeliningEnabled: True
ProtocolLoggingLevel : None
RemoteIPRanges :
{::-:::::::, 0.0.0.0-255.255.255.255}
RequireEHLODomain : False
On Thu, Sep 4, 2014 at 6:00 PM, Michael B. Smith
mich...@smithcons.commailto:mich...@smithcons.com wrote:
You’ve got 3 receive connectors in your output. The first one doesn’t have
AnonymousUsers set on it. You probably want it to. Especially if you are trying
to, for example, accept non-authenticated email in the “Default WC-SBS1”
connector from IP addresses in the range of 192-168.10.0/24.
[1]
PermissionGroups: ExchangeUsers, ExchangeServers,
ExchangeLegacyServers
RemoteIPRanges : {192.168.10.255-192.168.10.255,
192.168.10.0-192.168.10.253}
Name: Default WC-SBS1
[2]
PermissionGroups: AnonymousUsers
RemoteIPRanges : {192.168.11.0-255.255.255.255,
192.168.10.254-192.168.10.254, 0.0.0.0-192.168.9.255}
Name: Windows SBS Internet Receive WC-SBS1
[3]
PermissionGroups: AnonymousUsers, ExchangeUsers
RemoteIPRanges : {127.0.0.1-127.0.0.1}
Name: Windows SBS Fax Sharepoint Receive
WC-SBS1
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Graeme Carstairs
Sent: Thursday, September 4, 2014 5:47 PM
To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com
Subject: Re: [Exchange] REceive connector Exchnage 2010
Ok
I have tried the command
Deleteing and recreating all connectors.
uninstalling and reinstlaling the hub transport role, and using windows SBS
manager fix netowrk connectivity to rebuild the connectors
and still the same errors
I have ran the
get-receiveconnector |fl
Here are the results
RunspaceId : 70374003-32d5-4db1-a7f9-13e7c949b853
AuthMechanism : Tls, Integrated, BasicAuth,
BasicAuthRequireTLS, ExchangeServer
Banner :
BinaryMimeEnabled : True
Bindings:
{192.168.10.2:25http://192.168.10.2:25
[Exchange] Re: REceive connector Exchnage 2010
Ok If I setup an SMTP relay listening onporn26
It accepts mail in but when it tried to forward Tor the exhange SMTP on
port 25 I get the same error192.168.10.2 does not have permission to send
to this server
I'm at my wit send the customer is losing the plot
Everything is set right
Even creating a login and trying that is failing
Any ideas
On Friday, 5 September 2014, Graeme Carstairs loonyto...@gmail.com wrote:
I have tried all the changes suggested even adding a new ip into the
server nic
Creating a new connector bound to it
With the settings as described
Changed the nat and still getting the same error
There at be something else where stopping it
I'm going to stick mail relay software on listening on a different port
and get it to forward the mail locally
See if that works
Graeme
On Friday, 5 September 2014, Daniel Chenault dani...@hotmail.com
javascript:_e(%7B%7D,'cvml','dani...@hotmail.com'); wrote:
I dunno about that but as it stands, like I said earlier, your connectors
will only receive from internal addresses.
On Sep 4, 2014, at 16:21, Michael B. Smith mich...@smithcons.com
wrote:
This is way SBS does things.
Sent from my Windows Phone
--
From: ccollins9
Sent: 9/4/2014 7:10 PM
To: exchange
Subject: Re: [Exchange] REceive connector Exchnage 2010
U, is it me or are none of these connectors are set to receive from
0.0.0.0
- 255.255.255.255? Going to be hard to receive email from the internet if
all your connectors can only receive from a 192.168 address, no? You need
to set a receive connector to ip range 0.0.0.0-255.255.255.255 AND
permissions group 'anonymous'. For example, here's my output from our
internet connector:
PermissionGroups: AnonymousUsers
PipeliningEnabled: True
ProtocolLoggingLevel : None
RemoteIPRanges
: {::-:::::::, 0.0.0.0-255.255.255.255}
RequireEHLODomain : False
On Thu, Sep 4, 2014 at 6:00 PM, Michael B. Smith mich...@smithcons.com
wrote:
You’ve got 3 receive connectors in your output. The first one doesn’t
have AnonymousUsers set on it. You probably want it to. Especially if you
are trying to, for example, accept non-authenticated email in the “Default
WC-SBS1” connector from IP addresses in the range of 192-168.10.0/24.
[1]
PermissionGroups: ExchangeUsers,
ExchangeServers, ExchangeLegacyServers
RemoteIPRanges :
{192.168.10.255-192.168.10.255, 192.168.10.0-192.168.10.253}
Name: Default WC-SBS1
[2]
PermissionGroups: AnonymousUsers
RemoteIPRanges : {192.168.11.0-255.255.255.255,
192.168.10.254-192.168.10.254, 0.0.0.0-192.168.9.255}
Name: Windows SBS Internet Receive
WC-SBS1
[3]
PermissionGroups: AnonymousUsers, ExchangeUsers
RemoteIPRanges : {127.0.0.1-127.0.0.1}
Name: Windows SBS Fax Sharepoint
Receive WC-SBS1
*From:* listsad...@lists.myitforum.com [mailto:
listsad...@lists.myitforum.com] *On Behalf Of *Graeme Carstairs
*Sent:* Thursday, September 4, 2014 5:47 PM
*To:* exchange@lists.myitforum.com
*Subject:* Re: [Exchange] REceive connector Exchnage 2010
Ok
I have tried the command
Deleteing and recreating all connectors.
uninstalling and reinstlaling the hub transport role, and using windows
SBS manager fix netowrk connectivity to rebuild the connectors
and still the same errors
I have ran the
get-receiveconnector |fl
Here are the results
RunspaceId :
70374003-32d5-4db1-a7f9-13e7c949b853
AuthMechanism : Tls, Integrated, BasicAuth,
BasicAuthRequireTLS, ExchangeServer
Banner :
BinaryMimeEnabled : True
Bindings: {192.168.10.2:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
BareLinefeedRejectionEnabled: False
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
LongAddressesEnabled: False
OrarEnabled : False
SuppressXAnonymousTls : False
AdvertiseClientSettings : False
Fqdn: WC-SBS1.wce.local
Comment :
Enabled : True
ConnectionTimeout : 00:10:00
ConnectionInactivityTimeout : 00:05:00
MessageRateLimit: unlimited
