Closed Bug 316272 Opened 20 years ago Closed 17 years ago

The empty list is incorrectly imported from LDIF

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: dma_k, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051107 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051107 SeaMonkey/1.5a The examle of the empty list: dn: cn=Auto objectclass: top objectclass: groupOfNames cn: Auto Reproducible: Always Steps to Reproduce: 1. Create a new empty list 2. Export it into the LDIF format 3. Import it again Actual Results: The empty list is ignored and just skiped. Expected Results: A new empty list to be created.
Can you reproduce with SeaMonkey v2.0a1pre ?
Version: unspecified → Trunk
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070515 SeaMonkey/1.5a] (nightly) (W2Ksp4) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008052702 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) (In reply to comment #0) > The examle of the empty list: > > dn: cn=Auto > objectclass: top > objectclass: groupOfNames > cn: Auto What is that ? > Steps to Reproduce: > 1. Create a new empty list I create a new empty (mailing) list. (under Personal Address Book) > 2. Export it into the LDIF format This creates a 0-length file. ***** (1 month later) No reply from reporter. R.Incomplete Reopen if you can reproduce with SeaMonkey v2.0a1pre. (with more detailed steps)
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
> > dn: cn=Auto > > objectclass: top > > objectclass: groupOfNames > > cn: Auto > > What is that ? That is an example of empty maillist in LDIF format. > > 2. Export it into the LDIF format > > This creates a 0-length file. This is already an incorrect behaviour. Even empty maillists should be reflected in output LDIF file. Step 2 should give LDIF file like mentioned in the very beginning. I am not able to test against v2.0.
You need to log in before you can comment on or make changes to this bug.