Yup. Spent a good part of the day trying to find some discrepancy. Found nothing. However, the problem - which appeared spontaneously disappeared in the same way.

With luck the firewall will never see me as "special" again.  

Thanks

M

I'm running Windows XP - Pegasus mail v 4.51,  Mercury Mail v 4.52, a physical firewall sits between the mail server the the world.

Over the weekend the WAN IP in the firewall was changed (ISP required switch due to company split). 

On Monday I could not send mail via Pegasus via our Mercury server - I got the message:  553 We do not relay non-local mail  (no one else in the company had any problems)

On Tues I could not longer send mail - getting he message: 15. Peer Connect Failure (the host has refused the connection)

Session logs:

SEND

--- Tue, 03 Nov 2009 10:24:54 ---
Connect to 'server IP' port 25, timeout 15.
10:24:55.125 15: Peer connect failure (the host has refused the connection). 

 RECEIVE

--- Tue, 03 Nov 2009 10:24:32 ---
Connect to 'server IP' port 110, timeout 15.
10:24:33.187 15: Peer connect failure (the host has refused the connection).

 I can not telnet from my computer to either port 25 or 110 via the IP of the mail server - but I can telnet to both ports from other computers on the newtwork

Windows firewall is Off on my machine.  NAV is not blocking ports.  I have checked my mail settings against others on the network and the they are the same ports, hosts, etc...

Is there something I am missing?  It seems odd that of the 15 machines with identical settings mine is the only one which can not send/receive mail.

thank you

 Michele

[quote user="Michele"]

 I can not telnet from my computer to either port 25 or 110 via the IP of the mail server - but I can telnet to both ports from other computers on the newtwork

[/quote]

You have a networking issue with your machine. You will need to find what is different from the other machines on the network. Maybe the firewall has you singled out for 'special attention' [:)].