Re: Sudden attacks by something called Live Girls

From: Licensed to Quill (vintagepen_at_compuserve.nospam.com)
Date: 06/12/03


Date: Thu, 12 Jun 2003 11:58:20 -0400

Yes, what I was saying was that obviously MSIMN turns out to be outlook
express but I still cant figure out what to do about the pop ups. It seems
they are coming in through Port 135 and I cant find any rule I ever created
whereby communications through port 135 are permitted. Plus Microsoft seems
to think that if I ever want to be communicated with by themselves or by
antivirus updates with urgent messages, I have to keep this port open?
Anyway I cant find a way of preventing the pop ups from coming in through
Port 135 if there isn't a rule for it in SETTINGS and I never created one?

L2Q

""Crash" Dummy" <dvader@deathstar.mil> wrote in message
news:veh3h3hg4q9r58@corp.supernews.com...
> >Many thanks, I had wondered where the At Guard newsgroup had gone?? It
> >keeps disappearing from whatever host was currently carrying it? But the
> >people there are really knowledgeable on lots of vaguely related subjects
> >and no loonies seem to hang around on it.
>
> This isn't run by the same people. Fortunately.
>
> >CADing on Windows 2000 only shown something looking suspiciously like
> >messengering called MSINM.exe and shutting that does turns out to close
> >Outlook Express!
>
> Yes, msimn.exe is Outlook Express: MicroSoft Internet Mail and News. :-)
>
> >I am pretty sure I disabled messengering (which I never use) a few weeks
ago
> >and checked the At Guard settings to see if anything was being permitted
to
> >come in and nothing untoward was set as permissible, except for some
reason
> >Port 27015 which seems fairly innocuous (unless someone knows otherwise)
>
> Why do you have port 27015 allowed? You must have a rule that allows it
because
> AG blocks anything that isn't defined.
> --
> Dave "Crash" Dummy - A weapon of mass destruction
> crash@gpick.com
> http://lists.gpick.com
>
>
>
>



Relevant Pages

  • Re: Error 0x800CCC60
    ... port 25 as it may recognize you as a spammer especially if you are sending ... SMTP Error # 0x800ccc60 ... until I set up their e-mail in Outlook under the new logon. ... blocking SMTP traffic in some situations, so I disabled McAfee on one ...
    (microsoft.public.outlook)
  • Re: Error 0x800CCC60
    ... SMTP Error # 0x800ccc60 ... until I set up their e-mail in Outlook under the new logon. ... blocking SMTP traffic in some situations, so I disabled McAfee on one ... on port 25, even if I telnet from a working box, so I can't tell if ...
    (microsoft.public.outlook)
  • Re: Cant Send e-mails - Outlook 2003
    ... Rich, the answer to #1 is yes, at home Outlook sends messages just fine. ... I asked them about other port numbers, and they say they do not have any ... Your original settings might have been okay, but Verizon may have had server ...
    (microsoft.public.outlook.installation)
  • Re: Which SMTP port number to use
    ... AOLis SMTP port is 587. ... Diane Poremsky [MVP - Outlook] ... >> What is correct SMTP port number for outlook 2003? ... > AOL user, you will have to use whatever AOL says to use. ...
    (microsoft.public.outlook.general)
  • Re: SMTP SSL on Port Other than 25
    ... > use SSL/TLS over SMTP on a port other than 25. ... expertise with MS Outlook to offer a solution. ... and its predecessor, RFC 821, describe the SMTP protocol. ... which allows for authenticated connections by Message Submission Agents ...
    (microsoft.public.outlook)