From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0388_01C56D31.3303CF80
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Password prompts are triggered by authentication demands from the =
server.  If you are getting prompted it is because the server requested =
it or you configured Outlook to prompt.  Enabling Outlook logging and/or =
capturing a network trace would go a long way to indicate why a prompt =
occurs.

Rich

  "Glenn Meadows"  wrote in message =
news:42a8fc91$1{at}w3.nls.net...
  On my system, it's SurgeMail, POP3/SMTP, and an IMAP account on our =
NBX=20
  phone system for voice mail, and a POP3 account to the server that =
Scott has=20
  for the other office (MailMax), which is located in Texas, so there =
are 3=20
  accounts right now.  But this happened prior to the addition of the =
POP3=20
  account in Texas.  The popup is for the surgemail pop3 account.  I've =
used=20
  the SMTP authentication both on and off, no change.  This comes and =
goes.=20
  It will stay for a day or so, then just go away for weeks/months.  The =

  suspect machine (bosses laptop a Dell), Windows XPPro, fully patched.  =
No=20
  network connectivity problems. I have the connection icon displayed in =
the=20
  task bar, and have no notification messages about loss of network=20
  connection.  And during this mail is sent and retrieved between =
popups.  His=20
  machine has been repeatedly rebooted, as has the mail server, and the =
switch=20
  between him and the mail server.

  --=20

  Glenn M.
  "Rich"  wrote in message news:42a794df{at}w3.nls.net...
     Account settings are a per-user.  This could be a difference, =
either by a=20
  settings change or disk/memory corruption.  It would be interesting if =
other=20
  users on the same machine or another MAPI profile under the same user =
have=20
  this issue.

     Password prompting is a per-use per-account setting.  It also can =
be=20
  triggered by the server.  As one example, below is the setting for a=20
  Microsoft Exchange Server account in Outlook 2003.  Your intermittent=20
  behavior though sounds like it is the server rejecting the =
authentication=20
  and forcing the reauth for the session.

     What I haven't seen in this thread is the type of account, type of=20
  server, and authentication mechanism used.  If using Windows =
integrated auth=20
  then whether these are domain accounts or not, if the user logs on to =
that=20
  domain account or uses saved passwords, and similar is probably also=20
  relevant.




  Rich

    "Glenn Meadows"  wrote in message=20
  news:42a78d57$1{at}w3.nls.net...
    But why would it work for some clients going to the same address =
from the
    same network, and not others (I know Scott, and we've been =
struggling with
    this for some time).

    I still have one or two Outlook XP installs where the login window =
pops=20
  up,
    asking for password, you click OK after entering it, and it goes =
away.
    Then, on the next retrieve cycle, it's back.  Mail still sends and=20
  retrieves
    properly, and nobody else in the building has that problem.  I've =
moved to=20
  a
    different switch port, etc.  Then, when it goes away, it's gone for =
weeks.
    We even ran that laptop without AV for a couple of days.

    --=20

    Glenn M.
    "Rich"  wrote in message news:42a76d60{at}w3.nls.net...
       I'm surprised that a virus scanner could cause the error =
reported.  I
    believe that error indicates that none of the email accounts support =
the
    recipient's address usually because it's an unsupported transport =
(not
    SMTP).

    Rich

      "John Cuccia"  wrote in message
    news:d4dea1d9dqjoijde9hnhvmd686k4n40k36{at}4ax.com...
      Did you try sending mail with no virus scanner installed?

      On Wed, 08 Jun 2005 12:02:45 -0400, Scott 
      wrote:

      >Replaced it with AVG Anti-Virus; same problem(s)
      >Scotty/SpiritWolf
      >
      >
      >John Cuccia wrote:
      >> On Tue, 07 Jun 2005 18:00:10 -0400, Scott =

      >> wrote:
      >>
      >>
      >>>Problem:
      >>>
      >>>MS Outlook fails to send a message. As SOON as the Send/Receive =

  button,
      >>>I get it back in the inbox with:
      >>
      >>
      >> Are you running Symantec AV software?  If so, uninstall it and =
try
      >> sending again.  If successful, you can reinstall SAV.
      >>



------=_NextPart_000_0388_01C56D31.3303CF80
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Password
prompts are =
triggered by=20
authentication demands from the server.  If you are getting =
prompted it is=20
because the server requested it or you configured Outlook to = prompt. =20
Enabling Outlook logging and/or capturing a network trace would go a = long way to=20
indicate why a prompt occurs.
 
Rich
 

  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:42a8fc91$1{at}w3.nls.net...On=20
  my system, it's SurgeMail, POP3/SMTP, and an IMAP account on our NBX =
phone=20
  system for voice mail, and a POP3 account to the server that Scott has =
for=20
  the other office (MailMax), which is located in Texas, so there are 3=20
  accounts right now.  But this happened prior to the addition =
of the=20
  POP3 account in Texas.  The popup is for the surgemail pop3=20
  account.  I've used the SMTP authentication both on and off, =
no=20
  change.  This comes and goes. It will stay for a day or so, =
then just=20
  go away for weeks/months.  The suspect machine (bosses laptop =
a=20
  Dell), Windows XPPro, fully patched.  No network connectivity =

  problems. I have the connection icon displayed in the task bar, =
and have=20
  no notification messages about loss of network connection.  =
And=20
  during this mail is sent and retrieved between popups.  His =
machine=20
  has been repeatedly rebooted, as has the mail server, and the switch=20
  between him and the mail server.--
Glenn =
M."Rich"=20
  <{at}> wrote in message news:42a794df{at}w3.nls.net...&nbs=
p; =20
  Account settings are a per-user.  This could be a difference, =
either by a=20
  settings change or disk/memory corruption.  It would be =
interesting=20
  if other users on the same machine or another MAPI profile under =
the same=20
  user have this issue.  
Password prompting is a =
per-use=20
  per-account setting.  It also can be triggered by the =
server. =20
  As one example, below is the setting for a Microsoft Exchange =
Server=20
  account in Outlook 2003.  Your intermittent behavior though =
sounds=20
  like it is the server rejecting the authentication and forcing the =
reauth=20
  for the session.   What I haven't
seen in this =
thread is the=20
  type of account, type of server, and authentication mechanism =
used. =20
  If using Windows integrated auth then whether these are domain =
accounts or=20
  not, if the user logs on to that domain account or uses saved =
passwords,=20
  and similar is probably also=20
 
relevant.Rich 
"Glenn Meadows" =
<gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:42a78d57$1{at}w3.nls.net...=
 =20
  But why would it work for some clients going to the same address from=20
  the  same network, and not others (I know Scott, and we've =
been=20
  struggling with  this for some
time).  I still =
have one=20
  or two Outlook XP installs where the login window pops =
up, =20
  asking for password, you click OK after entering it, and it goes=20
  away.  Then, on the next retrieve cycle, it's back.  =
Mail still=20
  sends and retrieves  properly, and nobody
else in the =
building=20
  has that problem.  I've moved to a 
different switch =
port,=20
  etc.  Then, when it goes away, it's gone for
weeks.  We =
even ran=20
  that laptop without AV for a couple of days.  -- =
 =20
  Glenn M.  "Rich" <{at}> wrote in
message news:42a76d60{at}w3.nls.net...&nbs=
p;   =20
  I'm surprised that a virus scanner could cause the error =
reported. =20
  I  believe that error indicates that none of the email =
accounts=20
  support the  recipient's address usually because it's an =
unsupported=20
  transport (not  SMTP).  =
Rich   =20
  "John Cuccia" <jcuccia{at}bigfoot.com>">mailto:jcuccia{at}bigfoot.com">jcuccia{at}bigfoot.com>
wrote =
in=20
  message  news:d4dea1d9dqj=
oijde9hnhvmd686k4n40k36{at}4ax.com...   =20
  Did you try sending mail with no virus scanner=20
  installed?    On Wed, 08
Jun 2005 12:02:45 =
-0400, Scott=20
  <scotty{at}spirit-wolf.com>=">mailto:scotty{at}spirit-wolf.com">scotty{at}spirit-wolf.com>=
   =20
  wrote:    >Replaced
it with AVG Anti-Virus; =
same=20
  problem(s)    =
>Scotty/SpiritWolf   =20
  >   
>    >John Cuccia=20
  wrote:    >> On Tue,
07 Jun 2005 18:00:10 =
-0400,=20
  Scott <scotty{at}spirit-wolf.com>=">mailto:scotty{at}spirit-wolf.com">scotty{at}spirit-wolf.com>=
   =20
  >> wrote:   
>>   =20
  >>    =
>>>Problem:   =20
  >>>   
>>>MS Outlook fails to =
send a=20
  message. As SOON as the Send/Receive
button,    =

  >>>I get it back in the inbox
with:   =20
  >>   
>>    >> =
Are you=20
  running Symantec AV software?  If so, uninstall it and=20
  try    >> sending
again.  If successful, =
you can=20
  reinstall SAV.   =20
>>

------=_NextPart_000_0388_01C56D31.3303CF80--

--- BBBS/NT v4.01 Flag-5