| Summary | Add support for importing Pine distribution lists |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | Matt Selsky <selsky (at) columbia (dot) edu> |
| Created | 08/02/2006 (650 days ago) |
| Due | |
| Updated | 06/15/2007 (333 days ago) |
| Assigned | |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch |
State ⇒ Accepted
Works for me.> Hrm. How many address books are we going to search for the contacts?
Only the one you are importing to.
>> What do people consider the correct behavior with distribution lists
>> to be? Should we look up each email address in them, add found
>> contacts to a new contact list if we find them, and create new
>> contacts and add them to the list if we don't?
>
> Sounds right.
Hrm. How many address books are we going to search for the contacts?
>> This will probably need to be Turba-specific, right? Not sure we can
>> handle this in a generic way.
>
> Why does it need to be generic? The pine driver should probably be
> moved to Turba anyway. It doesn't handle generic "data" like the
> other drivers in the Data package.
It doesn't have to be generic, I was just making sure it makes sense for it _not_ to be.
> What do people consider the correct behavior with distribution lists
> to be? Should we look up each email address in them, add found
> contacts to a new contact list if we find them, and create new
> contacts and add them to the list if we don't?
Sounds right.
> This will probably need to be Turba-specific, right? Not sure we can
> handle this in a generic way.
Why does it need to be generic? The pine driver should probably be moved to Turba anyway. It doesn't handle generic "data" like the other drivers in the Data package.
State ⇒ Feedback
What do people consider the correct behavior with distribution lists to be? Should we look up each email address in them, add found contacts to a new contact list if we find them, and create new contacts and add them to the list if we don't?
This will probably need to be Turba-specific, right? Not sure we can handle this in a generic way.
Queue ⇒ Horde Framework Packages
Type ⇒ Enhancement
Summary ⇒ Add support for importing Pine distribution lists
Priority ⇒ 1. Low
State ⇒ New
See http://www.washington.edu/pine/tech-notes/low-level.html#addrbook for file format.
Basically,
'For a distribution list, the <address> is in the format:
"(" <address>, <address>, <address>, ... ")"'
We simply ignore distribution lists at the moment (around line 146 of Data/tsv.php)