tag:lazyatom.lighthouseapp.com,2007-02-28:/projects/92-rhubarb/eventslazyatom / Rhubarb Events2007-02-28T18:56:55Ztag:lazyatom.lighthouseapp.com,2007-02-28:Event/6665692008-05-25T17:04:08+01:002008-05-25T17:04:08+01:00Murray SteeleNew Rhubarb Project MemberMurray Steele has been given access to the Rhubarb Project.tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41232007-03-25T16:39:53+01:002007-03-25T16:39:53+01:00James AdamRhubarb: Lists should have many members [#3]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41222007-03-25T16:39:21+01:002007-03-25T16:39:30+01:00James AdamRhubarb: Lists should have a nice long name for public display [#4]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41212007-03-25T16:39:02+01:002007-03-25T16:39:02+01:00James AdamRhubarb: Lists should have a short name for subject line display [#5]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41202007-03-25T16:38:42+01:002007-03-25T16:38:41+01:00James AdamRhubarb: Lists should have a domain and an account name [#6]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41192007-03-25T16:38:13+01:002007-03-25T16:38:12+01:00James AdamRhubarb: Incoming Mails should be rejected if they are not from a member [#17]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41182007-03-25T16:38:05+01:002007-03-25T16:38:12+01:00James AdamRhubarb: Incoming Mails should be rejected if they are not from a member [#17]<div><p>
If a membership cannot be loaded, the mail is rejected.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41172007-03-25T16:37:24+01:002007-03-25T16:37:23+01:00James AdamRhubarb: Incoming Mails should have a List determined by the to: or cc: header [#8]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
<div><p>
The list is determined by the "recipients" method, added to TMail
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/41162007-03-25T16:36:28+01:002007-03-25T16:36:27+01:00James AdamRhubarb: Memberships should associate a person with a list [#18]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22262007-03-08T20:04:48+00:002007-03-08T20:04:48+00:00James AdamRhubarb: Memberships should specify which address mails to its list should appear from [#20]tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22242007-03-08T20:04:16+00:002007-03-08T20:04:15+00:00James AdamRhubarb: Memberships should specify the address to which mails from its list are sent [#19]tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22232007-03-08T20:03:35+00:002007-03-25T16:36:27+01:00James AdamRhubarb: Memberships should associate a person with a list [#18]tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22222007-03-08T19:54:03+00:002007-03-25T16:38:41+01:00James AdamRhubarb: Lists should have a domain and an account name [#6]<li>Title changed from <em class="change">“Lists should have an address”</em> to <em class="change">“Lists should have a domain and an account name”</em></li>
<div><p>
It will then respond to emails send TO: <account_name>@<domain>
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22212007-03-08T19:50:09+00:002007-03-08T19:50:09+00:00James AdamRhubarb: Initial account model [#7]<div><p>
Lots of these go on the Membership...
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22202007-03-08T19:40:15+00:002007-03-08T19:40:15+00:00James Adam[Message] Rhubarb: Which Ruby mail library to use?<div><p>It seems like they're much the same, except that TMail's nomenclature seems foreign. Perhaps it matches the RFC better.</p><p>We have selected TMail, since it comes with ActionMailer and so may be available without doing any extra work.</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/22192007-03-08T18:49:22+00:002007-03-08T18:49:22+00:00James AdamRhubarb: Base rhubarb application should be created [#2]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
<div><p>
Now available at:
</p><p>
<a href="http://svn.deletetheinternet.org/rhubarb/trunk">http://svn.deletetheinternet.org...</a>
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12472007-02-28T19:15:50+00:002007-03-25T16:38:12+01:00James AdamRhubarb: Incoming Mails should be rejected if they are not from a member [#17]<div><p>
If none of the member accounts for a list have the from: address of a mail's sender, this mail came from some stranger and should be avoided, lest it try to show us its puppys.
</p><p>
I WILL NOT GO WITH YOU IN YOUR VAN, MISTER!
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12452007-02-28T19:13:01+00:002007-02-28T19:21:23+00:00James AdamRhubarb: Outgoing Mails should appear from the designated "sent from" address of the sender's account [#16]<div><p>
This is a property that should also probably appear on the Membership association model
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12442007-02-28T19:08:03+00:002007-02-28T19:21:54+00:00James AdamRhubarb: Outgoing Mails should be sent to all Members of the List [#13]<div><p>
Whether or not the mail is actually sent should depend on the nature of the membership - mails may be disabled.
</p><p>
I would suggest the logic goes something like:
</p>
<ul><li>
for every membership of the list
</li><li>
get every "reciepient" address from each of those memberships. (there may be memberships which have no recipient address; they don't get any mails from this list)
</li><li>
send to all those addresses.
</li></ul></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12422007-02-28T19:06:44+00:002007-02-28T19:22:22+00:00Murray SteeleRhubarb: Outgoing Mails should have [list-name] in the subject line [#14]<li>Milestone set to <em class="change">“<span class="milestone" data-id="39">0.1.0 - F*cknut Reborn</span>”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12412007-02-28T19:06:30+00:002007-02-28T19:22:50+00:00Murray SteeleRhubarb: Outgoing Mails should have all RE: or FW: type text reduced to a single instance [#15]<div><p>
Outgoing Mails subject lines should be manipulated such that there is only one re: (or RE: or Re: etc...) and it appears at the start of the mail.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12392007-02-28T19:05:29+00:002007-02-28T19:22:22+00:00Murray SteeleRhubarb: Outgoing Mails should have [list-name] in the subject line [#14]<div><p>
The subject line of all Outgoing Mails should be manipulated such that there is one [list-name] construct in it. Either at the start if it is a new message to the list, or immediately after any re: or fw: indicators.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12382007-02-28T19:03:30+00:002007-02-28T19:21:54+00:00Murray SteeleRhubarb: Outgoing Mails should be sent to all Members of the List [#13]<div><p>
All Users who are a Member of the List should have the mail sent to them using their chosen send-to address.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12372007-02-28T19:03:17+00:002007-03-25T16:39:53+01:00James AdamRhubarb: Lists should have many members [#3]<div><p>
A list should be related to a number of accounts through a Memberships model.
</p><p>
The membership should store information about the user's relationship to this list, i.e. whether or not they want to receive email, which address of their account should mail be sent to (i.e. work vs. home), and so on.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12362007-02-28T19:02:25+00:002007-02-28T19:24:29+00:00Murray SteeleRhubarb: Outgoing Mails should have approptiate list-XXX: headers set [#12]<div><p>
When an Incoming Mail is transformed into an Outgoing Mail we shold apply the standard set of mailing list list-XXX: headers. These are fairly standard, and probably written up in some impenetrable rfc somewhere.
</p><p>
What we currently provide is:
</p><p>
List-Url: <list-web-url>
</p><p>
List-Archive: <list-archive-web-url>
</p><p>
List-Owner: <list-admin-mailto-url>
</p><p>
List-Help: <list-help-web-url>
</p><p>
List-Post: <list-post-mailto-url>
</p><p>
List: list-name
</p><p>
Note that as 0.1.0 won't have a web accessible front-end, some of the headers may not be useful.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12352007-02-28T19:01:06+00:002007-02-28T19:01:06+00:00James AdamRhubarb: Create script for accepting emails via procmail [#1]<li>Assigned user set to <em class="change">“James Adam”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12332007-02-28T19:00:35+00:002007-02-28T19:01:06+00:00James AdamRhubarb: Create script for accepting emails via procmail [#1]<div><p>
This script's responsibility is to create a Mail object which can the be passed to a separate class to actually handle the mail.
</p><p>
This mail should be the raw Mail object of the selected mail library, since we won't know at this point what the list is, the account of the sending user, and so on.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12322007-02-28T18:58:50+00:002007-02-28T19:23:51+00:00Murray SteeleRhubarb: Outgoing Mails should have the reply-to: header set to the list address [#11]<div><p>
As part of the process of turning an Incoming Mail into an Outgoing Mail we need to replace any reply-to: header that it has with the address of the list. The intention is that in your mail client you reply to the list, not the original sender.
</p></div>tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12302007-02-28T18:57:03+00:002007-02-28T18:57:02+00:00Murray SteeleRhubarb: Incoming Mails should be archived into a database [#10]<li>Milestone set to <em class="change">“<span class="milestone" data-id="39">0.1.0 - F*cknut Reborn</span>”</em></li>
tag:lazyatom.lighthouseapp.com,2007-02-28:Event/12292007-02-28T18:56:55+00:002007-02-28T18:57:02+00:00Murray SteeleRhubarb: Incoming Mails should be archived into a database [#10]<div><p>
We should archive the complete message as sent. We may also want to tear the message apart and store bits separatly for:
</p>
<ul><li>
ease of access to mails
</li><li>
nice web display
</li><li>
simple searching
</li></ul>
<p>
How this should be structured and what goes where needs thought. E.g. do we replicated the whole mail in the db (with mime-encoded attachments?), or do we replicated only the attachment stripped mail?
</p></div>