Just people in our IP space, it seems. Oddly I can telnet to port 25 
from any of our mail server's bind IP's and do an SMTP session.  I'll 
have to do some logging.  It's hard to email someone you're having a 
problem when their email.

16 15:23:25.00:Info:-1310827664: msg: log_reason [200237750] Later: 
216.8.136.155 HIDDEN@ul@mnsi.net> <postmaster@pelicanparts.com> 965 
<4.3.2.7.2.20140516104421HIDDEN@f0@in.mnsi.net> "Open (23.251.218.13) 
Error 61sec (399 TCP Read failed (Connection refused after 0 seconds) 0 
sec)"

I should just turn on TCP logging and see what's happening...

- SteveP

On 5/16/2014 2:24 PM, Frank Bulk wrote:
> So do all email senders need to work around pelicanparts.com's issue?
>
> Frank
>
> -----Original Message-----
> From: Steve Perrault [mailtoHIDDEN@psp101.net]
> Sent: Friday, May 16, 2014 9:04 AM
> To: surgemailHIDDEN@etwinsite.com
> Subject: [SurgeMail List] Overriding an MX for an external domain
>
> Our clients cannot email a domain that has 7 MX records of increasing
> priority
>
> pelicanparts.com.       6964    IN      MX      10
> pelicanserver-7.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      20
> pelicanserver-3.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      30
> pelicanweb3.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      40 forums.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      50
> pelicanserver3mail.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      60
> pelicanserver7mail.pelicanparts.com.
> pelicanparts.com.       6964    IN      MX      70 forums4.pelicanparts.com.
>
>
>
> When surgemail tries to send, it always tries the highest priority one,
> but the connection is dropped for some reason. They use cloudflare and
> it'll take time for me as an outsider to get this fixed.    The email is
> processed hourly in the queue, each attempt trying to send to
> pelicanserver-7.pelicanparts.com.  I'm assuming the other MX's aren't
> attempted because the error is a temporary one.
>
> How can I bypass this in the meantime?  Can I specify a preferred MX for
> a particular external domain?
>
> - SteveP
>
>
>
>