Re: SMTP Security

From: NoSpam (me_at_here.com)
Date: 02/23/05

  • Next message: John Sommer: "Firewall suggestions" 
    Date: Thu, 24 Feb 2005 09:25:19 +1100

    Thanks Hairy One,

    Nice try, but I use this tool all of the time and the ini files, etc came
    along too and got tweeked as required.

    This would also not explain why I can not telnet to my own port 25 but I can
    telnet to my own port 80.

    Regards,
    Dean.

    "Hairy One Kenobi" <abuse@[127.0.0.1]> wrote in message
    news:X81Td.8$3C3.7@newsfe3-win.ntli.net...
    > "NoSpam" <me@here.com> wrote in message
    > news:IYySd.8926$i6.97883@nasal.pacific.net.au...
    > > I am currently upgrading my Exchange from E2000/W2000 to E2003/W2003.
    > W2003
    > > has all of the latest hot fixes and service packs.
    > >
    > > I have a command-line utility for sending SMTP messages. On my old
    W2000
    > > server, I run a small task every day and e-mail the statistics to
    myselve
    > > via this command line utility.
    > >
    > > I have tried to port this to my new W2003 with disappointing results.
    > >
    > > From my desktop PC, I can use the SMTP utility to send to both the W2000
    > and
    > > the W2003 server without a problem. However, when I try to use the
    > > command-line SMTP utility on the W2003 server to send a message to
    itself,
    > > connection fails.
    > >
    > > When I try troubleshooting with Telnet to port 25, I get the following
    > > message, "Connecting To a.b.c.d...Could not open connection to the host,
    > on
    > > port 25: Connect failed". This happens no matter what server I attempt
    to
    > > contact (external servers as well). I can also connect from the W2000
    > > server to itself.
    > >
    > > Is there a feature in a hotfix or a service pack, possibly aimed at
    > stopping
    > > SPAM, etc, that is designed to prevent a W2003/E2003 server connecting
    to
    > > port 25 from the command line?
    >
    > I (for one) have not heard of a specific block.
    >
    > OTOH, might you be missing some config info that was entered all those
    years
    > ago, and isn't mirrored on the new server? If it's CLI, then it's quite
    > possibly an INI file dropped somewhere, rather than (e.g.) registry.
    >
    > --
    >
    > Hairy One Kenobi
    >
    > Disclaimer: the opinions expressed in this opinion do not necessarily
    > reflect the opinions of the highly-opinionated person expressing the
    opinion
    > in the first place. So there!
    >
    >

  • Next message: John Sommer: "Firewall suggestions"

    Relevant Pages

    • Re: SMTP Security
      ... Nice try, but I use this tool all of the time and the ini files, etc came ... >> has all of the latest hot fixes and service packs. ... >> server to itself. ... the opinions expressed in this opinion do not necessarily ...
      (microsoft.public.windows.server.general)
    • Re: SMTP Security
      ... > has all of the latest hot fixes and service packs. ... > I have tried to port this to my new W2003 with disappointing results. ... > the W2003 server without a problem. ... the opinions expressed in this opinion do not necessarily ...
      (microsoft.public.windows.server.security)
    • Re: SMTP Security
      ... > has all of the latest hot fixes and service packs. ... > I have tried to port this to my new W2003 with disappointing results. ... > the W2003 server without a problem. ... the opinions expressed in this opinion do not necessarily ...
      (microsoft.public.windows.server.general)
    • Re: Capturing Windows Login Name
      ... that among other protocols supports NTLM. ... That demonstrates that you lack of rhetorical skills and your reputation ... Since you run out facts to sustain your opinions, ... server in the last step, ...
      (comp.lang.php)
    • Re: So fn sick of viruses from just surfing the web!
      ... I purposely made statements that were purely opinions but you still ... on other hand, if you have a samba server, you might wanna have a AV ... to keep it clear so that windows clients don't get infected using your ... don't fight malware with anti-malware... ...
      (microsoft.public.windowsxp.general)