You are right. But sometimes, you may have some luck:
- Querying the DNS for the MX record of the host's domain may work. (But I've seen several LANs where DNS either giving no MX records at all or the wrong ones, unreachable on the other side of the firewalls.)
- The DHCP server's response may include option 69 "SMTP-Server". (Well, I've never seen that.)
- Try to resolve some common host names / aliases (mail, mx, smtp, mailer, post, ...; append 1, 2, 3, 01, 02, 03, -1, -2, -3, -01, -02, -03)
For each candidate, try to connect to the SMTP server on ports 587/tcp (submission) and 25/tcp (smtp).
(Occasionally, I've found LAN mail servers with a brute force nmap scan, scanning for servers with at least one of the two ports open. But don't do that without permission from the network admin, and never in foreign networks!)
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
