* This is the vopmailbeta mailing list *

My theory on this is that Vop/Modus are more lenient
about accepting messages with so-so headers.

I think if RFC compliance is forced you would see less,
an example is the date, this seems to be very lax.

On the other hand I can see that if you tighten the noose
and force compliance you might also cause greater problems
than we have now. 

Yes it would be true that the problem would exist in the
cheapo mail server that is sending non compliant headers
but try to explain that to your customer!

I think we are stuck with the least of two evils until 
Norton does something with their garbage software to prevent
its proxy mechanism from jamming on goofy messages.

John

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of David Ruggles
Sent: Tuesday, February 18, 2003 1:49 PM
To: [EMAIL PROTECTED]
Subject: [VOPmail Beta] Norton AV issues

* This is the vopmailbeta mailing list *


I have done some limited research on the Google, and have found the same
thing. It doesn't seem to limited to Vircom products, but it does seem
to
happen more often on them.

Thanks,
David Ruggles

CCNA MCSE (NT) CNA A+
Network Engineer, Safe Data, Inc
910-285-7200    [EMAIL PROTECTED]
010001110110111101100100011011000110111101110110011001010111001101111001
0110
111101110101
----- Original Message -----
From: "Network Operations" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 18, 2003 1:23 PM
Subject: [VOPmail Beta] Norton AV issues


> * This is the vopmailbeta mailing list *
>
>
> It does not happen only on Vircom Servers.
>
> I have had several instances where it has happened to
> customers on my linux/qmail servers also.
>
> Same symptoms, disable the Norton pop scanner and the problem
> goes away.
>
> I have more instances on my ModusMail server but I have a lot more
> customers on it also which might be why I have more trouble with it.
>
> John
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Jeff - MIS
Sciences
> Corporation
> Sent: Tuesday, February 18, 2003 1:18 PM
> To: [EMAIL PROTECTED]
> Subject: [VOPmail Beta] Norton AV issues
>
> * This is the vopmailbeta mailing list *
>
>
> This has been going on for several years and I, too, have very angry
> customers. Vircom has responded that it is a NAV/OE problem, but can
not
> explain why it only happens on Vircom servers.
>
> I do wish Vircom would state that either they ARE going to fix it or
NOT
> going to fix it instead of just ignoring this issue
>
> ATT VIRCOM: It only happens on VOP and Modus servers
>
> Jeff
>
>
> ----- Original Message -----
> From: "John Blue" <[EMAIL PROTECTED]>
> To: "David Ruggles" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 18, 2003 09:40
> Subject: [VOPmail Beta] Norton AV issues
>
>
> * This is the vopmailbeta mailing list *
>
>
>
> DR> That's what I was afraid of :( Do you know if there is any way to
> DR> figure out what is tripping Norton? I sure other people have
> DR> already thought of this, but we might be able to filter the
> DR> messages or something.
>
> Dont hold yer breath on this one, nobody seems to be in a hurry to
> figure it out .. I lost a customer because he just had to run Norton
> on his machine.  Nevermind that we already run NAVGW.
>
> After he left .. he had to throw it in my face that with his new ISP
> everything works like it is suppose to so we are a lot of wannabe
> losers.
>
> His email tag line had his ICQ number in it and since I knew that he
> ran 95a I whipped up a sweet little DoS script just for his little
> punk ass.  :)
>
>
> **
> To leave this list, send an email to [EMAIL PROTECTED]
> and put the word "LEAVE" in the BODY of the email.
>
>
> **
> To leave this list, send an email to [EMAIL PROTECTED]
> and put the word "LEAVE" in the BODY of the email.
>
>
> **
> To leave this list, send an email to [EMAIL PROTECTED]
> and put the word "LEAVE" in the BODY of the email.


**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.


**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.

Reply via email to