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 Timothy Prepscius <ti...@gmail.com> on 2012/06/09 21:16:31 UTC
copy-forward based on user
Greetings again.
James is being very awesome. I am quite pleased.
During beta testing, I am going to allow users to add a "copy-forward" parameter to their info.
So... I need to make James copy-send every mail it receives to the user's specified copy-send address.
So I was thinking I would create a new mailet (or modify one that already exists).
I was thinking of deriving off of "Forward" and then doing a DB lookup in getRecipients.
But now I'm thinking this functionality probably exists already.
Any hints as to where I should look for an example--- or should I implement this?
Thanks!
-tim
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: copy-forward based on user
Posted by Timothy Prepscius <ti...@gmail.com>.
Thanks!
-tim
On Jun 10, 2012, at 4:35 AM, Eric Charles wrote:
> Hi Tim,
>
> Mailet can do it (there is no such mailet atm, but you could develop it), but Sieve filters may be a better fit for this (see copy extension http://www.ietf.org/rfc/rfc3894.txt)
>
> But the jSieve integration with server is still to be done (https://issues.apache.org/jira/browse/JAMES-1373).
>
> The advantage of jSieve is that it will be manageable/configurable by the end user.
>
> (The existing RewriteRecipientTable will not help because it does not copy)
>
> Thx, Eric
>
>
> On 06/09/2012 09:16 PM, Timothy Prepscius wrote:
>> Greetings again.
>>
>> James is being very awesome. I am quite pleased.
>>
>> During beta testing, I am going to allow users to add a "copy-forward" parameter to their info.
>> So... I need to make James copy-send every mail it receives to the user's specified copy-send address.
>>
>>
>> So I was thinking I would create a new mailet (or modify one that already exists).
>> I was thinking of deriving off of "Forward" and then doing a DB lookup in getRecipients.
>>
>>
>> But now I'm thinking this functionality probably exists already.
>>
>>
>> Any hints as to where I should look for an example--- or should I implement this?
>>
>>
>> Thanks!
>>
>> -tim
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
> --
> eric | http://about.echarles.net | @echarles
>
> ---------------------------------------------------------------------
> 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: copy-forward based on user
Posted by Eric Charles <er...@apache.org>.
Hi Tim,
Mailet can do it (there is no such mailet atm, but you could develop
it), but Sieve filters may be a better fit for this (see copy extension
http://www.ietf.org/rfc/rfc3894.txt)
But the jSieve integration with server is still to be done
(https://issues.apache.org/jira/browse/JAMES-1373).
The advantage of jSieve is that it will be manageable/configurable by
the end user.
(The existing RewriteRecipientTable will not help because it does not copy)
Thx, Eric
On 06/09/2012 09:16 PM, Timothy Prepscius wrote:
> Greetings again.
>
> James is being very awesome. I am quite pleased.
>
> During beta testing, I am going to allow users to add a "copy-forward" parameter to their info.
> So... I need to make James copy-send every mail it receives to the user's specified copy-send address.
>
>
> So I was thinking I would create a new mailet (or modify one that already exists).
> I was thinking of deriving off of "Forward" and then doing a DB lookup in getRecipients.
>
>
> But now I'm thinking this functionality probably exists already.
>
>
> Any hints as to where I should look for an example--- or should I implement this?
>
>
> Thanks!
>
> -tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org