I have only one standalone server...no edge server. I have one send connector and that has been changed to the mail.aptn.ca entry. When I try to change the receive connector, I get the following error.
-------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- The following error(s) occurred while saving changes: Set-ReceiveConnector Failed Error: If the AuthMechanism attribute on a Receive connector contains the value ExchangeServer, you must set the FQDN parameter on the Receive connector to one of the following values: the FQDN of the transport server "APTNEXCH.aptn.local", the NetBIOS name of the transport server "APTNEXCH", or $null. -------------------------------------------------------- OK -------------------------------------------------------- On Wed, Apr 9, 2014 at 10:07 AM, Kennedy, Jim <kennedy...@elyriaschools.org>wrote: > You are on your Hub Transport or Edge if you have that…..’Send > Connectors’? You see it, but it’s grayed out…what are you seeing? You got > the right permissions? > > > > http://technet.microsoft.com/en-us/library/dd638213(v=exchg.150).aspx > > > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Steve Ens > *Sent:* Wednesday, April 9, 2014 11:00 AM > > *To:* exchange@lists.myitforum.com > *Subject:* Re: [Exchange] Relaying > > > > OK, doesn't let me adjust that from the EMC. > > > > On Wed, Apr 9, 2014 at 9:36 AM, Kennedy, Jim <kennedy...@elyriaschools.org> > wrote: > > On your outgoing mail connector on the general tab. ‘specify the fqdn > this connector will provide in response to…..’ > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Steve Ens > *Sent:* Wednesday, April 9, 2014 10:33 AM > *To:* exchange@lists.myitforum.com > *Subject:* Re: [Exchange] Relaying > > > > So I am also looking into DNS and my hoster tells me this... > > > > DNS is fine. Forward: > > > > mail.aptn.ca. 7200 IN A 139.142.213.125 > > > > Reverse: > > > > 125.213.142.139.in-addr.arpa. 86400 IN PTR mail.aptn.ca. > > > > But the banner on the server is the .local name: > > > > Trying 139.142.213.125...Connected to mail.aptn.ca.Escape character is > '^]'.220 aptnexch.aptn.local Microsoft ESMTP MAIL Service ready at Wed, 9 > Apr 2014 > > 07:13:45 -0500 > > > > How do I change my banner on my local server? > > > > On Tue, Apr 8, 2014 at 9:55 PM, Steve Ens <stevey...@gmail.com> wrote: > > I think Don has not been in this conversation yet, and i do use Vipre for > backscatter and spam protection. I don't think having 600 messages > undelivered in the queue is reasonable. We have been blacklisted a couple > of times and been delisted so far. I also have all traffic on port 25 > blocked out of the firewall except for the Exchange box. I'm looking at the > smtp logs and can;t seem anything off yet. > > > > On Tue, Apr 8, 2014 at 7:07 PM, Richard Stovall <rich...@gmail.com> wrote: > > I think this answer is correct in some circumstances, but not > universally by any means. Don, do you have any backscatter protection > enabled? This would eliminate these as NDRs resulting from spam from > spoofed addresses you own. If you don't have backscatter protection, my > guess is that spam which does spoof existing addresses would be far more > problematic than that which does not. > > > > On Tue, Apr 8, 2014 at 7:13 PM, Mike Tavares <miketava...@comcast.net> > wrote: > > the sender <> is normal exchange NDR’s being delivered. Since your > exchange server is authoritative for you domain any messages addressed to > non existent email address will cause these, since a lot of spam has bogus > address you tend to see them sitting in your ques for a while. They will > eventually time out and go away on their own. > > > > Nothing to worry about. > > > > > > *From:* Steve Ens <stevey...@gmail.com> > > *Sent:* Tuesday, April 08, 2014 4:30 PM > > *To:* exchange@lists.myitforum.com > > *Subject:* [Exchange] Relaying > > > > I'm running exchange 2010 here with all the service packs. I think that I > must have misconfigured one of my receive connectors. I know I am not an > open relay from the outside, but I think I have a machine inside my network > that is compromised and using exchange to send out since I have many > messages sitting in my queue that are undeliverable. Any suggestions as to > how I'd determine from which IP these messages are originating? The sender > always looks like <> I've opened up the message tracking logs, but can't > find any incriminating evidence there. > > > > > > > > >
