Global _mailinglist_archives_list_schema ($list)

Fully implement

Global _mailinglist_config_form_validate ($form, &$form_state)

validate mailinglist_base

Global _mailinglist_mailbox_process ($list, $file, $offset)

Unquote >From lines.

we can add code to compare "From " line to message here and fix stuff.

Global _mailinglist_pagecallback ()

get node id of our introduction.

File mailinglist.module

Themeing Functions Message. MessageSummary. MessageSummaryList.

Content Type Archived Message?

Possible define a FieldType for Messages? as a way to link to Themeing.

Global mailinglist_archive_ctools_plugin_directory ($owner, $plugin_type)

Condition to only return directories that we might actually be using.

Global mailinglist_archive_message_add ($msg, $list)

Add Year/Month/Day/Hour fields for stats These should be in the timeframe of the Web site, not GMT as the message time so that the Hour reflect the real effective hour. Maybe add a TZ entry for the list? (thus it could be a zone with dst processing or it could be GMT)

Hack to handle some bad dates

Global mailinglist_ctools_plugin_directory ($owner, $plugin_type)

Condition to only return directories that we might actually be using.

Global mailinglist_help ($path, $arg)

expand to meet help text standards: http://drupal.org/node/632280

Global mailinglist_members_ctools_plugin_directory ($owner, $plugin_type)

Condition to only return directories that we might actually be using.

mailinglist/operation

Global mailinglist_members_mailinglist_list_created ($list)

Should this be converted to a "standard" function?

Global mailinglist_members_mailinglist_list_delete ($list)

Should this be converted to a "standard" function?

Global mailinglist_members_mailinglist_message ($msg, $list)

mark sender as seen

Global mailinglist_members_modules_enabled ($modules)

should only do this for list with members enabled, and redo when members is enabled on a list.

Global mailinglist_members_scan ($list)

should this be seperate queue/cron job?

Global mailinglist_members_subscribe ($list, $email, $time=FALSE)

record subscription

Global mailinglist_members_unseen ($list, $email, $time=FALSE)

make sure this really applies, especially if we ever call this when time isn't 'now'

Global mailinglist_members_unsubscribe ($list, $email, $time=FALSE)

record unsubscription

Global mailinglist_message_delete ($node)

implement mailinglist_message_delete

Global mailinglist_message_form ($node, &$form_state)

implement mailinglist_message_form

Global mailinglist_message_insert ($node)

implement mailinglist_message_insert

Global mailinglist_message_load ($nodes)

implement mailinglist_message_load

Global mailinglist_message_rfc2047 ($string)

should insure that the string is bounded by atom boundries.

Global mailinglist_message_update ($node)

implement mailinglist_message_update

Global MailinglistArchiveOperation::form (&$form, &$form_state, $list)

Build Archives Page

Achives parse data range.

add navagation menu

Archives Search

Achives parse data range.

add navagation menu

Archives Search

Global MailinglistExportable::log_file ($str, $parms=array(), $level=self::LOG_INFO)

Global MailinglistExportable::log_screen ($str, $parms=array(), $level=self::LOG_NOTICE)

Need to do substitution into $str

Global MailinglistExportUI::edit_form (&$form, &$form_state)

Need to decide how to handle this: When building the form, we have in $form_state['item'] the value of the object for this form as read from the database to build up the form. The issue is that this does NOT reflect changes made in the form along the way until we get through Submit. The big issue is that if we change what type of object we want, we NEED to change the object to that time, so as to build the form for the needed values but the object in the form_state will not really be 'valid' as fields needed by the type (and provided by the form) may not be present. We also have a quandry on taking other values from the input, if we take them at form building time, they haven't (and can't) be validated (can't because we don't have form info to do the validation). Is it better to be missing some values, and others be stale, or to have more (but likely not all) values but from an unvalidated source.

Should we do this? (see above), maybe just copy 'object_type'

why doesn't this get copied?

see if we can normally cache, and only disable cache if changing object type.

Should we do this? (see above), maybe just copy 'object_type'

why doesn't this get copied?

see if we can normally cache, and only disable cache if changing object type.

Global MailinglistExportUI::edit_form_validate (&$form, &$form_state)