I've never used Zimbra. (It looks like you do.) How is your edge-facing Zimbra instance determining what internal addresses are viable?
On Tue, Apr 26, 2011 at 11:18 PM, Don Kuhlman <[email protected]> wrote: > Yep Richard - you're undestanding perfectly - outside parties - say > [email protected] <[email protected]> can't send to the company > Comcast's email immediately generates a huge error that I can't even copy > and paste. I did type the major parts of it and they are pasted below with > email and company.com being substituted out, etc. > > This worked about a week ago(no problems sending from comcast to our > domain). At first I thought something had changed at Comcast. I googled > the SCC-1203 and SCC-1204 codes along with the error text below and it led > me to Comcast's forum. That in turn led me to posts saying the target email > address was not on a secure server or that the target domain was not allowed > to be sent to, which then led me to search for blacklisting and I found the > domain blacklisted on two sites, which I went to and manually asked them to > remove us by putting our external email server ip address into the forms on > the blacklist sites. > > However, just trying it now from Comcast still causes it to fail > immediately with this error. Since I orginally thought it was a Comcast > issue because I hadn't heard about any other failures from other domains > sending to us (hitachi, etc.), I opened a case with Comcast. They are > supposed to be investigating which maybe they can enlighten me too ;) > > Thanks! > > Don K > Message not sent; The following addresses were not accepted: {0} SCC-1203 > Message not sent; The following addresses were not accepted: > [email protected] SCC-1204 > method: SendMsgRequest > msg: Invalid address: > [email protected]$SafeSendFailedException: > code: mail.SEND_ABORTED_ADDRESS_FAILURE > detail: soap:Sender > trace: btp00l0-121808:1303873522184:a35c69230074fa82 > > request: Body: { > > > > > ------------------------------ > *From:* Richard Stovall <[email protected]> > *To:* MS-Exchange Admin Issues <[email protected]> > *Sent:* Tue, April 26, 2011 9:07:34 PM > *Subject:* Re: Fixing Exchange 2007 server that might be hijacked or used > as a relay and has been blacklisted > > Blacklisting, as I typically understand it, means that you can't send to > the other party. What you're describing, unless I misunderstand, is a > situation where outside parties are unable to send to you. > > What are the exact (full text) errors you received from Comcast when > testing? > > On Tue, Apr 26, 2011 at 9:30 PM, Don Kuhlman <[email protected]> wrote: > >> Hi folks. This is probably a very basic question for the Exchange >> gurus...I'm trying to support of an exchange 2007 server (on SBS 2008) and >> found that it looks like we're being blacklisted by certain sites. Internal >> users were reporting that they couldn't receive emails from outside >> customers using comcast.net, and hitachi among others. I tried to send >> to emails internally from comcast and was also getting errors that we were >> being blocked or not allowed from comcast. >> >> I ran some scans from different sites such as >> http://www.mxtoolbox.com/SuperTool.aspx that show if you're blacklisted >> and found a couple instances where we were. >> >> I've been trying to find a way (internally from the server logs or >> firewall logs) to see if the Exchange 2007 server was hijacked or is being >> used as a relay. I'm not sure what to look for as traffic patterns on the >> firewall so that I can set rules to block this, nor what I might want to try >> initially on the server to protect it. >> >> I looked (googled) for how to test for blacklisting and all I'm finding is >> sites that tell you how to request you be removed temporarily from a >> blacklist or how to test your ip for blacklist status. >> >> Are there good sites that I can study to find out from the server's >> perspective or how to make sure it's not being used maliciously for relaying >> or spamming or some sites that tell me how to lock it down or verify it's >> okay (not to mention getting it permanently off the blacklists) ? >> >> Thanks! >> >> Don K >> >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to [email protected] >> with the body: unsubscribe exchangelist >> > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
