From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9) Gecko/20020311 BuildID: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9) Gecko/20020311 1.I cannot delete address from book - if exist add should be remove. 2.It is impossible to use universal network path in Windows such as \\PORTO\MyMail\dnsaddress to storage mail folder. I can see subject of mails, but not text inside. If I mount it as drive G:\MyMail\dnsaddress, all is OK, but drives are not as shure as path. P.S. PLEASE ADD DISTRIBUTION LIST IN ADDRESS BOOK FOR PRIVATE USE (I DON'T HAVE LDAP Server)- I HAVE NO POSSIBILITIES TO DO THIS IT IS SIMPLE, VERY HELPFULL AND EXIST IN MANY OTHER MAIL PROGRAMS (IN THIS POINT I USE PINE TO SEND MAILS). Micke Reproducible: Always Expected Results: DISTRIBUTION LIST IN ADDRESS BOOK
*** Bug 137721 has been marked as a duplicate of this bug. ***
1. Please clarify what you mean in your first statement "I cannot delete address from book". Are you trying to delete an address book? You should be able to delete an address book except for the Personal Address Book and the Collected Address Book. 2. The second issue to use the universal network path in Windows is an Enhancement Request. If the first issue still exists then please log it in a separate bug. I will change the summary of this bug to track the second issue. Changing summary from "No delete option, no local network posibilities" to "[RFE]Address Book to support a universal network path in windows"
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420