379706 - export to ldif doesnt retain 'allow remote images' field

Status: RESOLVED WONTFIX

(MailNews Core :: Address Book, defect)

Description

[john russell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: version 2.0.0.0 (20070326)

when i export the address book to ldif format, there
is no entry for the 'allow remote images' selection
field .... can this not be added

what i am trying to do is to massage a massive address book so
that all entries send html (that is easy - field is there
 can be global changed with text editor)  AND
set the allow remote images in HTML box ----
this is the field that is not exported and reimporting 
defaults to false  RATTS!!!  
should not all fields of the address book card not be
exported / imported ??? 

Reproducible: Always

Steps to Reproduce:
1. export address book to ldif
2. look for field
3. oops!!!

Comment 2

[Joshua Cranmer [:jcranmer]]

(In reply to comment #0)
> should not all fields of the address book card not be
> exported / imported ??? 

There is no standardized way to represent the field internally known as AllowRemoteContent in external content, although I believe Evolution represents the data in vcard form via X-MOZILLA-HTML.

I am unable to find a duplicate, so moving and confirming.

Comment 3

[Dmitry]

I confirm the problem for TB 17. In particular:

* "Allow remote content" is not exported.
* "Prefers to receive messages formatted as..." is not exported.
* All fields on "Chat" tab are not exported, except AIM.
* Image on "Photo" tab is not exported.

So they all are lost (independently of format: ldif/csv/txt) and thus export/import mechanism cannot be used for backup/restore purposes.

Comment 4

[Magnus Melin [:mkmelin]]

Tb 17 is EOL a long time ago, you should upgrade to 24.

The next general release is TB 31 in a couple of months, and for that bug 457296 has removed remote content management from address books.

So -> WONTFIX

Comment 5

[Dmitry]

Unfortunately, v24 has a problem which I cannot leave with (bug#933171). Anyway export doesn't work properly in the properties I have listed, see similar bug#536053.

Comment 6

[石庭豐 (Seak, Teng-Fong)]

(In reply to Magnus Melin from comment #4)
> Tb 17 is EOL a long time ago, you should upgrade to 24.
> 
> The next general release is TB 31 in a couple of months,

TB 31 actually took more than merely a couple of months to be released.  But more importantly...

> and for that bug
> 457296 has removed remote content management from address books.

I don't see any removal of "remote content management from address books".  I had quickly gone through that bug 457296 but I don't see what "remote content management" means.

> 
> So -> WONTFIX

I suggest to reopen this bug.

Comment 7

[Joshua Cranmer [:jcranmer]]

(In reply to 石庭豐 (Seak, Teng-Fong) from comment #6)
> > and for that bug
> > 457296 has removed remote content management from address books.
> 
> I don't see any removal of "remote content management from address books". 
> I had quickly gone through that bug 457296 but I don't see what "remote
> content management" means.

The "remote content management" is the internal name for the feature you are describing ("allow remote images from this sender" in the UI). The backing store for that data is no longer the address book, but rather a separate database for generalized permission management.

I do agree with the decision to WONTFIX this bug.