You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Renen Watermeyer <re...@121.co.za> on 2011/04/14 22:33:45 UTC
code to contribute
Hello,
I have some code that we have made extensive use of over the last few
years. There's no rocket science to the code, and the code could
undoubtedly be improved. But, the mailets might ease other people's
adoption of James, they have been in production for a while, and, we
certainly the mailets useful!
There are three mailets:
1. The first POSTs the entire email to a configurable URL
2. The second pushes key email fields as query string parameters to a
configurable URL
3. The third classifies bounce notifications by parsing the content of the email
I can simply paste the code into an email to this list. Or, I could
setup a project on github. Or, I can contribute them to the James
project.
My suspicion is that, given that the code has dependencies on Apache
Commons, it might not be suitable for inclusion in the base James.
Never mind my doubts about the code quality. :-)
I think an opportunity would be missed if the code were simply pasted
into emails. But, a shared Github repository of mailets may be useful.
Or perhaps these are too trivial to warrant any of the approaches!
How should I proceed?
Renen.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: code to contribute
Posted by Eric Charles <er...@apache.org>.
Hi Renen,
Many tks for your contributions.
I quickly looked at the code and SerialiseToHTTP and HeadersToHTTP is
really good and comprehensive. I will commit them in james trunk.
I also looked at the ClassifyBounce mailet which uses the Classifier.
My only comment would be that the patterns used to classify the mails
are not configurable (we could imagine rely on the mailet coded
patterns, and add some additional patterns via configuration).
Anyway, this is also very good, and I will commit them (or will wait for
your new version if you tell me you want to update it).
Tks,
- Eric
On 15/04/2011 20:37, Renen Watermeyer wrote:
> Indeed, pleased to meet you.
>
> Done: Mailet / MAILET-39
>
> If you need me to clean them up or tweak them in some way or other, just shout!
>
> The email to HTTP mailets are what we made most use of as these
> mailets allowed us to tie our mail infrastructure to our web
> infrastructure, which, in turn, encapsulated pretty much everything we
> did.
>
> Equally, I won't be affronted if they are rejected!
>
> renen.
>
>
> On 15 April 2011 10:19, Eric Charles<er...@apache.org> wrote:
>> Hi,
>> Great to read you!
>>
>> If you agree to opensource with ASL2 license, simply open a JIRA on
>> https://issues.apache.org/jira/browse/MAILET and attach there a zip with
>> your code (select 'grant apache for source inclusion'). We will review and
>> talk with you to further see how it can be included in Apache James
>> repository (dependency on apache-commons is not blocker at all).
>>
>> If you want to give another license, we've got http://www.apache-extras.org
>> for such cases.
>>
>> Tks again,
>>
>> - Eric
>>
>>
>> On 14/04/2011 22:33, Renen Watermeyer wrote:
>>>
>>> Hello,
>>>
>>> I have some code that we have made extensive use of over the last few
>>> years. There's no rocket science to the code, and the code could
>>> undoubtedly be improved. But, the mailets might ease other people's
>>> adoption of James, they have been in production for a while, and, we
>>> certainly the mailets useful!
>>>
>>> There are three mailets:
>>>
>>> 1. The first POSTs the entire email to a configurable URL
>>> 2. The second pushes key email fields as query string parameters to a
>>> configurable URL
>>> 3. The third classifies bounce notifications by parsing the content
>>> of the email
>>>
>>> I can simply paste the code into an email to this list. Or, I could
>>> setup a project on github. Or, I can contribute them to the James
>>> project.
>>>
>>> My suspicion is that, given that the code has dependencies on Apache
>>> Commons, it might not be suitable for inclusion in the base James.
>>> Never mind my doubts about the code quality. :-)
>>>
>>> I think an opportunity would be missed if the code were simply pasted
>>> into emails. But, a shared Github repository of mailets may be useful.
>>>
>>> Or perhaps these are too trivial to warrant any of the approaches!
>>>
>>> How should I proceed?
>>>
>>> Renen.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: code to contribute
Posted by Eric Charles <er...@apache.org>.
Hi,
Great to read you!
If you agree to opensource with ASL2 license, simply open a JIRA on
https://issues.apache.org/jira/browse/MAILET and attach there a zip with
your code (select 'grant apache for source inclusion'). We will review
and talk with you to further see how it can be included in Apache James
repository (dependency on apache-commons is not blocker at all).
If you want to give another license, we've got
http://www.apache-extras.org for such cases.
Tks again,
- Eric
On 14/04/2011 22:33, Renen Watermeyer wrote:
> Hello,
>
> I have some code that we have made extensive use of over the last few
> years. There's no rocket science to the code, and the code could
> undoubtedly be improved. But, the mailets might ease other people's
> adoption of James, they have been in production for a while, and, we
> certainly the mailets useful!
>
> There are three mailets:
>
> 1. The first POSTs the entire email to a configurable URL
> 2. The second pushes key email fields as query string parameters to a
> configurable URL
> 3. The third classifies bounce notifications by parsing the content of the email
>
> I can simply paste the code into an email to this list. Or, I could
> setup a project on github. Or, I can contribute them to the James
> project.
>
> My suspicion is that, given that the code has dependencies on Apache
> Commons, it might not be suitable for inclusion in the base James.
> Never mind my doubts about the code quality. :-)
>
> I think an opportunity would be missed if the code were simply pasted
> into emails. But, a shared Github repository of mailets may be useful.
>
> Or perhaps these are too trivial to warrant any of the approaches!
>
> How should I proceed?
>
> Renen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Life after the Wild Card - please contact me?
Posted by Stephen Hulbert <st...@afra.co.za>.
Renen Watermeyer <renen <at> 121.co.za> writes:
>
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org