Why not set up an RDP server at home and use that? Us DynDNS or livemesh to get access to your home machine.
~Kevinm WLKMMAS- This message is Certified Swine Flu Free My life http://www.hedonists.ca -----Original Message----- From: Bill Songstad (WCUL) [mailto:administra...@waleague.org] Sent: Tuesday, April 28, 2009 4:50 PM To: MS-Exchange Admin Issues Subject: RE: remotely testing smtp I've wished I've had a box outside my perimeter so many times that I think this excuse is a good one. I don't have a spare port on the firewall, but I can drop a little hub on the line outside the firewall and build a little box with one of our public ips on it. Then all your telnet are belong to us Good info on the logs too. And putting those hands together, I can put a sniffer on the outside machine and work at it from there. thanks Bill -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Tuesday, April 28, 2009 4:19 PM To: MS-Exchange Admin Issues Subject: Re: remotely testing smtp [reply to multiple messages from the same sender] On Tue, Apr 28, 2009 at 5:56 PM, Bill Songstad (WCUL) <administra...@waleague.org> wrote: > Does anybody know of a website/service that I can use to start an SMTP > session remotely? The problem is that most mass-market Internet feeds block TCP/25 outbound, as an anti-spam measure. "Business class" feeds generally don't (or have the option), but they cost more. Myself, for this sort of thing, I use a Unix shell account on a server at an Internet hosting provider. The server has a static IP address and no filtering. I can SSH (secure shell) in to that remotely, then "telnet foo 25" or whatever. There are companies which rent such Unix shell accounts, but that might be overkill for your needs. Since you're dealing with your ISP, see if they might be able to provision you with a temporary shell account on one of their servers. Another option would be to put a computer on the public side of the WatchGuard, with a public IP address on that Ethernet, and connect from that. This isn't the same as coming in from the cloud, but if you want to focus on that WG in particular, it's a good test. Of course, you may not have a free IP address on the public side of the WatchGuard. In a pinch, one thing you can do is configure a computer with the same IP address as the upstream gateway, and plug that computer into the public interface of the WG with a cross-over cable. The WG will think your computer is the upstream gateway, and you'll be able to run a simple "TELNET foo 25" test. This will, of course, knock out your Internet connection for the duration. On Tue, Apr 28, 2009 at 6:32 PM, Bill Songstad (WCUL) <administra...@waleague.org> wrote: > Probably, but I really think the problem is at the firewall proxy. Besides, > I have the smtp logs from the server. Shouldn't they have all that data? Sending or receiving server? If receiving, no, because your receiving server is behind the WatchGuard, and the WG is doing we-don't-know-what to filter SMTP. If you have logs from the sending server, well, yes, sort-of, but since somebody is blaming you, I suspect you'll want logs from your end anyway. Plus, logs sometimes lie. Packet sniffer traces show what was *actually on the wire*, not what the server *claims* it sent/received. If we could always trust software to perform as advertised then you wouldn't be having this problem. :-) So I second the suggestion of putting a sniffer in front of the WatchGuard. -- Ben ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
