I had a similar problem last week. It turns out that if we
switched from using one mail server to another it was OK.
The server that was blocked was actually not our normal one.
It was our ISP's mail server, not ours.
It was only to email addresses with
@ezweb.ne.jp
All the other older ezweb domains were fine which made it hard to detect.
We were told it might be because "reverse lookups" were not
enabled. But this wasn't confirmed. So the cause could have been something
else. Also I'm not sure if I got the terminology right. By reverse lookup I
mean when ezweb looks up your server name based upon its IP, then
they were getting no result.
You can try that first.... Maybe it will work.
Our ISP's ISP was the source of the difficulty.... They were not cooperating.
(Yes my ISP has an ISP or so it seems).
Curt Sampson wrote:
> It turns out that one of my mail servers seems to have been blocked by
> ezweb's firewall; TCP connections to their MX host just time out. Does
> anybody have any thoughts on who I might contact to get this fixed?
>
> cjs
> --
> Curt Sampson <cjs_at_cynic.net> +81 90 7737 2974 http://www.netbsd.org
> Don't you know, in this new Dark Age, we're all light. --XTC
>
> This mail was sent to address paul.lester@lincmedia.co.jp
> Need archives? How to unsubscribe? http://www.appelsiini.net/keitai-l/
--
*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*F=m(dv/dt)
Paul B. Lester
thetamusic.com（有）
Chief Engineer
EMAIL: paul@thetamusic.com
--
http://www.thetamusic.com/
personal homepage: http://pbl1.tripod.com/
personal EMAIL: pbl1@cornell.edu
*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*=*+*F=m(dv/dt)
Received on Thu Apr 17 13:07:06 2003