287460 - Can't define a direct and dialup account using AVG as a virus scanner

Status: RESOLVED EXPIRED

(Plugins Graveyard :: AVG AV, defect)

Description

[Bruce Prager]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

AVG requires that Thunderbird use 127.0.0.1 as the server name in order to route
the incoming mail thru AVG to thunderbird. If you have 2 accounts (1 direct, 1
dialup), the port numbers are different for each.  However, Thunderbird requires
that the server name and user name be unique.  It should require that the server
name + port name and user name be unique.  This would allow multiple accounts to
be defined and virus scanned.

Reproducible: Always

Steps to Reproduce:
1.Define 1 account connected direct, server name 127.0.0.1 port 5010  user test
2.Add a new account - 127.0.0.1 connected via dialup, port 5050 user test


Actual Results:  
Thunderbird will not allow you to add the account, making use of AVG and
Thunderbird impossible for more than 1 type of account.  This is true even if
the account is marked inactive

Expected Results:  
If the account is marked inactive, it should be ignored. Only when 2 accounts
are both active for downloading and have a conflict should it be a problem. 
This would allow TB to stay the same way it is, just check the active box under
servers.

Ideally, TB should look for unique server + port + user,  not server + user

Comment 1

[Mike Cowperthwaite]

(In reply to comment #0)
> AVG requires that Thunderbird use 127.0.0.1 as the server name in order to
> route the incoming mail thru AVG to thunderbird. 

Um... which version of AVG are you using?  I use AVG 7 (Win2K) with the 
"automatic" scanner, and this works for multiple POP accounts, with no changes 
to the TB configuration.  I haven't yet figured out how to get it to scan both 
POP and POPS accounts simultaneously, which is similar to your problem (a 
different port) but not the same.


> If you have 2 accounts (1 direct, 1 dialup), the port numbers are different
> for each.  

It is?  This is because AVG is requiring you to set up different ports?  Or is 
this some odd feature of your mail server?


> However, Thunderbird requires that the server name and user name be unique.
> It should require that the server name + port name and user name be unique.
> This would allow multiple accounts to be defined and virus scanned.

Personally, I think the problem is with AVG's poor modelling of mail accounts, 
and that this is not a TB bug.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.