I put the Relay: entries at the top and it worked. Any idea why it didn't work at the bottom?

-Will



----- Original Message ----
From: William Bashlor<willieb_72@yahoo.com>
To: CommuniGate Pro Discussions<CGatePro@mail.stalker.com>
Sent: Mon, March 8, 2010 5:05:30 PM
Subject: Re: Blacklisted by Earthlink, how to reroute earthlink traffic?

Hmm, it didn't work. I even reloaded the service. Should I put it at the top? Here'a the entire contents of the router:

localhost =            ; domain record to accept 'localhost' as the main domain
mailhost  =            ; domain record to accept 'mailhost'  as the main domain
<blacklist-admin*@blacklisted>  = postmaster ; 'White Hole'
<syshelp>      = support@communigate.com ; tech.support address
Signal:<911@*>        = emergency@localhost  ; 911: NA emergency
Signal:<112@*>        = emergency@localhost  ; 112: EU emergency
Signal:<01@*>         = emergency@localhost  ; 01:  RU emergency
Signal:<emergency>    = emergency#pbx        ; start 'emergency' app
Signal:<\*(3-4d)@*>   = voicemail#*          ; *nnn ->  voicemail
Signal:<7(2d)@*>      = pbx{*}#pbx           ; 7nn calls go to PBX
Signal:<8(3d)@*>      = pickup{*}#pbx        ; 8nnn: pickup nnnn
Signal:<(7d)@*>       = localAreaCall{*}#pbx ; 7 digits ->  local call
<+(7-20d)@*>    = +*@telnum            ; +nnnnn calls ->  to telnum
<1(10d)@*>      = +1*@telnum           ; NA domestic calls
<011(7-20d)@*>  = +*@telnum            ; NA Intl calls
<00(7-20d)@*>   = +*@telnum            ; EU Intl calls
<810(7-20d)@*>  = +*@telnum            ; RU Intl calls
Signal:telnum  = pstn                 ; unknown telnum ->  PSTN
Signal:<*@pstn>= gatewaycaller{*}#pbx ; start 'gatewaycaller' app
Relay:earthlink.net = earthlink.net@209.86.93.226.25.smtp
Relay:mindspring.com = mindspring.com@207.69.189.217.25.smtp


-Will


  


----- Original Message ----
From: Philip Slater<pslater@communigate.com>
To: CommuniGate Pro Discussions<CGatePro@mail.stalker.com>
Sent: Mon, March 8, 2010 4:55:02 PM
Subject: Re: Blacklisted by Earthlink, how to reroute earthlink traffic?

Trick with the Router table is that everything is processed on a top to bottom basis. Take in to consideration that this may want to be at the tail end of the table. But try to keep things grouped appropriately and use the ';' for comments.

Phil


On Mar 8, 2010, at 1:27 PM, William Bashlor wrote:

   

Dang I should have asked all these questions at one time, but does it matter where I put it in the router? Thanks for the quick replies...

-Will

  


----- Original Message ----
From: Brian Gibson<gibson_brian@wheatoncollege.edu>
To: CommuniGate Pro Discussions<CGatePro@mail.stalker.com>
Sent: Mon, March 8, 2010 4:08:22 PM
Subject: Re: Blacklisted by Earthlink, how to reroute earthlink traffic?

I think all we needed to do was save the entry router then do a
"Refresh" from the general page. I do not remember having to restart our
CGPro server but I might be mistaken.

On 3/8/2010 4:03 PM, William Bashlor wrote:
     

Thanks, I'm going to try it.

Any dangers to bringing the server down in your experience?

-Will

  


----- Original Message ----
From: Brian Gibson<gibson_brian@wheatoncollege.edu>
To: CommuniGate Pro Discussions<CGatePro@mail.stalker.com>
Sent: Mon, March 8, 2010 3:54:21 PM
Subject: Re: Blacklisted by Earthlink, how to reroute earthlink traffic?

Yup, that is the format we use on our server :-)

On 3/8/2010 3:53 PM, William Bashlor wrote:

       

Awesome. Thanks Brian!

Would this be correct (Earthlink owns Mindspring)?:

Relay:earthlink.net = earthlink.net@209.86.93.226.25.smtp
Relay:mindspring.com = mindspring.com@207.69.189.217.25.smtp

Is that ...IP.25.smtp?

Given:

******************************************************************************************
M:\>nslookup


         

set type=mx
earthlink.net


           

Non-authoritative answer:
earthlink.net  MX preference = 5, mail exchanger = mx2.earthlink.net
earthlink.net  MX preference = 5, mail exchanger = mx3.earthlink.net
earthlink.net  MX preference = 5, mail exchanger = mx4.earthlink.net
earthlink.net  MX preference = 5, mail exchanger = mx1.earthlink.net


         

mindspring.com


           

Non-authoritative answer:
mindspring.com  MX preference = 5, mail exchanger = mx3.mindspring.com
mindspring.com  MX preference = 5, mail exchanger = mx4.mindspring.com
mindspring.com  MX preference = 5, mail exchanger = mx1.mindspring.com
mindspring.com  MX preference = 5, mail exchanger = mx2.mindspring.com


         

           

M:\>ping mx1.earthlink.net
Pinging mx1.earthlink.net [209.86.93.226] with 32 bytes of data:
Reply from 209.86.93.226: bytes=32 time=16ms TTL=239
M:\>ping mx1.mindspring.com
Pinging mx1.mindspring.com [207.69.189.217] with 32 bytes of data:
Reply from 207.69.189.217: bytes=32 time=16ms TTL=239
******************************************************************************************

-Will





----- Original Message ----
From: Brian Gibson<gibson_brian@wheatoncollege.edu>
To: CommuniGate Pro Discussions<CGatePro@mail.stalker.com>
Sent: Mon, March 8, 2010 2:24:44 PM
Subject: Re: Blacklisted by Earthlink, how to reroute earthlink traffic?

We do something like this now with mail destined for wheatoncollege.edu
with a router entry like this

Relay:wheatoncollege.edu = wheatoncollege.edu@192.168.10.50.25.smtp

You need to know the IP address (from an MX lookup) of one of the
Earthlink inbound servers. Notice you specify the port (25) after the IP.



On 3/8/2010 2:19 PM, William Bashlor wrote:


         

Hi,

We are blacklisted by Earthlink, and from what I can tell, Earthlink only. We forward all mail to our barracuda for sending. Is there anyway I can use the router (or something) and make cgpro not forward any mail destined for Earthlink? In other words, all Earthlink mail would be sent as normal from CGPro's SMTP service?

I've near exhausted all attempts at trying to get off Earthlink's SPAM RBL or whatever they are using. My theory here is while I'm waiting for our Barracuda to be whitelisted, I can change the IP that our mail is coming from for earthlink only. This would at least restore our customers communication with Earthlink customers.

If not the router, maybe setting a global rule?

Any ideas here?

Thanks Guys (and Gals),

-Will
Network Engineer
Mediastream