| Summary | Add support for importing Pine distribution lists |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | selsky (at) columbia (dot) edu |
| Created | 08/03/2006 (7029 days ago) |
| Due | |
| Updated | 06/15/2007 (6713 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
State ⇒ Accepted
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?
handle this in a generic way.
moved to Turba anyway. It doesn't handle generic "data" like the
other drivers in the Data package.
for it _not_ to be.
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?
handle this in a generic way.
moved to Turba anyway. It doesn't handle generic "data" like the
other drivers in the Data package.
State ⇒ Feedback
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.
Priority ⇒ 1. Low
State ⇒ New
Queue ⇒ Horde Framework Packages
Summary ⇒ Add support for importing Pine distribution lists
Type ⇒ Enhancement
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)