|
|
|
date: Fri, 14 Oct 2005 12:46:04 -0700,
group: microsoft.public.exchange2000.misc
back
Re: Help with POPing errors due to messsages with suspect files
Well, there are all sorts of reasons why we're poping this particular
(rather than using an exchange account); it's got to do with who and how
some of the mail is 'processed' (as in answered).
On an unrelated post, a responder had suggested mixing accounts (POP and
exchange) on the same machine was asking for trouble (which I've done for
years on my own machine without any difficulties), so I disabled the
exchange account in this case as it's not actually used So, I don't think
that mixing accounts is the problem (and like I said, I've done it for years
without problems).
The AV seems to be working well (without problems) on regular exchange
accounts connected to the same server.
--
Dab
Cut off: yourhead to respond
"Brian Tillman" wrote in message
news:Ot7lckP0FHA.164@TK2MSFTNGP10.phx.gbl...
> Dab wrote:
>
>> I'm having difficulty POPing mail from an Exchange 2000 server (using
>> an Outlook 2003 client). Generally, everything works fine, however,
>> occasionally, a message that is later confirmed to contain a virus,
>> causes POPing to grind to a halt. Messages received after the
>> suspect message will not download to the client!
>
> Why are you connecting via POP?
>
>> Both the server and the client are running Symantec anti virus
>> plugins. What gives? Thanks for any help.
>
> Whether or not the client is running an AV program won't enter into it and
> apparently the server's AV isn't working well.
> --
> Brian Tillman
date: Fri, 14 Oct 2005 15:36:55 -0700
author: Dab
Re: Help with POPing errors due to messsages with suspect files
In news:uAT6I$Q0FHA.908@tk2msftngp13.phx.gbl,
Dab typed:
> Well, there are all sorts of reasons why we're poping this particular
> (rather than using an exchange account); it's got to do with who and
> how some of the mail is 'processed' (as in answered).
I am sure there's another way to attack this.....
>
> On an unrelated post, a responder had suggested mixing accounts (POP
> and exchange) on the same machine was asking for trouble (which I've
> done for years on my own machine without any difficulties), so I
> disabled the exchange account in this case as it's not actually used So, I
> don't think that mixing accounts is the problem (and like I
> said, I've done it for years without problems).
That was probably me :)
If you were using OL2000 or prior, you were using an unsupported config and
were simply lucky it worked. It's supported to mix account types in OL2002
and up, but I do not recommend it.
>
> The AV seems to be working well (without problems) on regular exchange
> accounts connected to the same server.
Then the virus-infected messages shouldn't be in the mailbox to begin with.
By allowing non-Exchange mail traffic into your server, you can't possibly
scan it centrally and prevent bad stuff from hitting the mail store at all.
Yet another reason to keep things simple!
>
>
> "Brian Tillman" wrote in message
> news:Ot7lckP0FHA.164@TK2MSFTNGP10.phx.gbl...
>> Dab wrote:
>>
>>> I'm having difficulty POPing mail from an Exchange 2000 server
>>> (using an Outlook 2003 client). Generally, everything works fine,
>>> however, occasionally, a message that is later confirmed to contain
>>> a virus, causes POPing to grind to a halt. Messages received after
>>> the suspect message will not download to the client!
>>
>> Why are you connecting via POP?
>>
>>> Both the server and the client are running Symantec anti virus
>>> plugins. What gives? Thanks for any help.
>>
>> Whether or not the client is running an AV program won't enter into
>> it and apparently the server's AV isn't working well.
>> --
>> Brian Tillman
date: Mon, 17 Oct 2005 11:47:34 -0400
author: Lanwench [MVP - Exchange]
Re: Help with POPing errors due to messsages with suspect files
Hi again Larry:
> If you were using OL2000 or prior, you were using an unsupported config
> and were simply lucky it worked. It's supported to mix account types in
> OL2002 and up, but I do not recommend it.
Yes, like I've stated, mixing POP and Exchange accounts in the same outlook
client has worked, and continues to work flawlessly and since the features
to do exactly this are built into Outlook, I'm still not unclear as to why
it's not a good idea- but that discussion is for a different thread. In
any case, in this discussion thread, there is no mixing of accounts, so,
mixing accounts is not an issue - the problem is with POPing mail from an
Exchange server.
Just as an update..... I've used a third party client to POP the mail and
have verified that the problem is still there so the issue definitely lies
with POPing mail from the Exchange server.
> Then the virus-infected messages shouldn't be in the mailbox to begin
> with. By allowing non-Exchange mail traffic into your server, you can't
> possibly scan it centrally and prevent bad stuff from hitting the mail
> store at all. Yet another reason to keep things simple!
Well, what ever is happening with the Exchange POP server, it's not catching
the virus (if that's what it really is). The POPed mail is not downloaded
to an exchange account, however it is, of course originating from an
exchange account because that's where it's being POPed from, but.. the mail
being delivered to that Exchange account is absolutely the same as all the
mail that's delivered to all the other Exchange accounts on the system - and
there aren't problems any where else - only with POP accounts. So, I'm not
mixing non-exchange mail as you suggest.
I'm all for keeping things simple, but, they simply have to do what I want
in order to be useful :). Thanks anyway.
--
Dab
Cut off: yourhead to respond
"Lanwench [MVP - Exchange]"
wrote in message
news:%23H%237CNz0FHA.464@TK2MSFTNGP15.phx.gbl...
>
>
> In news:uAT6I$Q0FHA.908@tk2msftngp13.phx.gbl,
> Dab typed:
>> Well, there are all sorts of reasons why we're poping this particular
>> (rather than using an exchange account); it's got to do with who and
>> how some of the mail is 'processed' (as in answered).
>
> I am sure there's another way to attack this.....
>>
>> On an unrelated post, a responder had suggested mixing accounts (POP
>> and exchange) on the same machine was asking for trouble (which I've
>> done for years on my own machine without any difficulties), so I
>> disabled the exchange account in this case as it's not actually used So,
>> I don't think that mixing accounts is the problem (and like I
>> said, I've done it for years without problems).
>
> That was probably me :)
> If you were using OL2000 or prior, you were using an unsupported config
> and were simply lucky it worked. It's supported to mix account types in
> OL2002 and up, but I do not recommend it.
>>
>> The AV seems to be working well (without problems) on regular exchange
>> accounts connected to the same server.
>
> Then the virus-infected messages shouldn't be in the mailbox to begin
> with. By allowing non-Exchange mail traffic into your server, you can't
> possibly scan it centrally and prevent bad stuff from hitting the mail
> store at all. Yet another reason to keep things simple!
>>
>>
>> "Brian Tillman" wrote in message
>> news:Ot7lckP0FHA.164@TK2MSFTNGP10.phx.gbl...
>>> Dab wrote:
>>>
>>>> I'm having difficulty POPing mail from an Exchange 2000 server
>>>> (using an Outlook 2003 client). Generally, everything works fine,
>>>> however, occasionally, a message that is later confirmed to contain
>>>> a virus, causes POPing to grind to a halt. Messages received after
>>>> the suspect message will not download to the client!
>>>
>>> Why are you connecting via POP?
>>>
>>>> Both the server and the client are running Symantec anti virus
>>>> plugins. What gives? Thanks for any help.
>>>
>>> Whether or not the client is running an AV program won't enter into
>>> it and apparently the server's AV isn't working well.
>>> --
>>> Brian Tillman
>
>
date: Tue, 18 Oct 2005 12:38:26 -0700
author: Dab
Re: Help with POPing errors due to messsages with suspect files
In news:u6YkDuB1FHA.3856@tk2msftngp13.phx.gbl,
Dab typed:
> Hi again Larry:
>
>> If you were using OL2000 or prior, you were using an unsupported
>> config and were simply lucky it worked. It's supported to mix
>> account types in OL2002 and up, but I do not recommend it.
>
> Yes, like I've stated, mixing POP and Exchange accounts in the same
> outlook client has worked, and continues to work flawlessly and since
> the features to do exactly this are built into Outlook, I'm still not
> unclear as to why it's not a good idea- but that discussion is for a
> different thread.
I'm going to shut up now. :)
> In any case, in this discussion thread, there is
> no mixing of accounts, so, mixing accounts is not an issue - the
> problem is with POPing mail from an Exchange server.
Gotcha.
>
> Just as an update..... I've used a third party client to POP the mail
> and have verified that the problem is still there so the issue
> definitely lies with POPing mail from the Exchange server.
>
>> Then the virus-infected messages shouldn't be in the mailbox to begin
>> with. By allowing non-Exchange mail traffic into your server, you
>> can't possibly scan it centrally and prevent bad stuff from hitting
>> the mail store at all. Yet another reason to keep things simple!
>
> Well, what ever is happening with the Exchange POP server, it's not
> catching the virus (if that's what it really is). The POPed mail is
> not downloaded to an exchange account, however it is, of course
> originating from an exchange account because that's where it's being
> POPed from, but.. the mail being delivered to that Exchange account
> is absolutely the same as all the mail that's delivered to all the
> other Exchange accounts on the system - and there aren't problems any
> where else - only with POP accounts. So, I'm not mixing non-exchange
> mail as you suggest.
I see....
>
> I'm all for keeping things simple, but, they simply have to do what I
> want in order to be useful :). Thanks anyway.
Sorry I can't help further.
>
> "Lanwench [MVP - Exchange]"
> wrote in
> message news:%23H%237CNz0FHA.464@TK2MSFTNGP15.phx.gbl...
>>
>>
>> In news:uAT6I$Q0FHA.908@tk2msftngp13.phx.gbl,
>> Dab typed:
>>> Well, there are all sorts of reasons why we're poping this
>>> particular (rather than using an exchange account); it's got to do
>>> with who and how some of the mail is 'processed' (as in answered).
>>
>> I am sure there's another way to attack this.....
>>>
>>> On an unrelated post, a responder had suggested mixing accounts (POP
>>> and exchange) on the same machine was asking for trouble (which I've
>>> done for years on my own machine without any difficulties), so I
>>> disabled the exchange account in this case as it's not actually
>>> used So, I don't think that mixing accounts is the problem (and
>>> like I said, I've done it for years without problems).
>>
>> That was probably me :)
>> If you were using OL2000 or prior, you were using an unsupported
>> config and were simply lucky it worked. It's supported to mix
>> account types in OL2002 and up, but I do not recommend it.
>>>
>>> The AV seems to be working well (without problems) on regular
>>> exchange accounts connected to the same server.
>>
>> Then the virus-infected messages shouldn't be in the mailbox to begin
>> with. By allowing non-Exchange mail traffic into your server, you
>> can't possibly scan it centrally and prevent bad stuff from hitting
>> the mail store at all. Yet another reason to keep things simple!
>>>
>>>
>>> "Brian Tillman" wrote in message
>>> news:Ot7lckP0FHA.164@TK2MSFTNGP10.phx.gbl...
>>>> Dab wrote:
>>>>
>>>>> I'm having difficulty POPing mail from an Exchange 2000 server
>>>>> (using an Outlook 2003 client). Generally, everything works fine,
>>>>> however, occasionally, a message that is later confirmed to
>>>>> contain a virus, causes POPing to grind to a halt. Messages
>>>>> received after the suspect message will not download to the
>>>>> client!
>>>>
>>>> Why are you connecting via POP?
>>>>
>>>>> Both the server and the client are running Symantec anti virus
>>>>> plugins. What gives? Thanks for any help.
>>>>
>>>> Whether or not the client is running an AV program won't enter into
>>>> it and apparently the server's AV isn't working well.
>>>> --
>>>> Brian Tillman
date: Tue, 18 Oct 2005 22:08:36 -0400
author: Lanwench [MVP - Exchange]
|
|
