If the request was sucessful each line should be prepended by a 2xx status code and SMTP in the line.

$line =~ /^2\d\d .*SMTP/ should work as a rudimentary test for the first line back.

Update:

use strict;
use warnings;

use Net::Telnet;

my $tel = Net::Telnet->new(-host => 'localhost', -port => 25, -errmode
+ => 'return') 
     or die "Port not available\n";
my $rtn = $tel->getline() 
     or die "No Reponse\n";
print $rtn =~ /^2\d\d .*SMTP/ ? 'OK' : 'Fail';
[download]

There are all kinds of checks that you could do. You could try to ping the host (Net::Ping) and see if that works - although that doesn't test that port 25 is open. You could try to connect to port 25 - but that doesn't guarantee that it's actually a mail server listening, or that your connection hasn't been redirected to the ISP's mail server (which might require SMTP Auth, limit who you can send as, etc).

I would think that the only safe, robust way of checking would be to send a test email from the user to themselves, and include some kind of id in the body so that you know that it's been sent properly. You can then immediately delete that email once you see it. This will allow you to test both their SMTP and POP/IMAP settings at the same time, and uses modules that you've probably got installed anyway, rather than introducing something new.

I already have Net::Ping check that there is a machine at the other end. What I need to do is offer a Check Server button where they enter the server details.

However your idea of looping an email around is a good one, I will give it some thought.

jdtoronto