>> Does this go in the right direction?
>
> Yes
Thank you once again, Benoit.
I will take the documentation in this direction, then.
Cheers,
=David
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For
Hi David,
On 23/05/2020 04:16, David Leangen wrote:
>
> Hi!
>
> Based on things that Benoit has been explaining to me (in threads such as
> [1], [2]), I have been thinking about the top-level description of James.
>
> [1] https://www.mail-archive.com/server-dev@james.apache.org/msg65858.html
Hi!
Based on things that Benoit has been explaining to me (in threads such as [1],
[2]), I have been thinking about the top-level description of James.
[1] https://www.mail-archive.com/server-dev@james.apache.org/msg65858.html
> Yet another bg topic.
:-)
> Mime4J is an effort to remove that dependency in James. There is still a
> lot of work to do to reach that goal (most notably in the mailet-container).
Is that what the DOM is for? I.e., is this supposed to be the MIME message you
are talking about?
—>
>> Thanks Benoit, very helpful! It does lead to more questions, though. :-)
>
> The contrary would have surprised me ;-)
Thanks again! There is a lot to digest here. All this information has been
really useful.
I will try to put my thoughts together by advancing with the documentation
before
On 22/05/2020 18:06, David Leangen wrote:
> Thanks Benoit, very helpful! It does lead to more questions, though. :-)
The contrary would have surprised me ;-)
I have been yet again quitte verbose once again, don't hesitate to raise
a warning if the signal/noise ratio gets to low...
Cheers,
>
On 22/05/2020 17:19, David Leangen wrote:
>>> Perhaps provide a “default” MailAdapter? In that case, then the factory
>>> could even just take an email and a SieveScript InputStream and apply the
>>> default MailAdapter. The method with the MailAdapter signature would only
>>> be needed for
Thanks Benoit, very helpful! It does lead to more questions, though. :-)
> - **mailet** are separated in an effort to serve as a specification for...
> - **mailbox** as presented below is a storage service for the server….
> - **protocols** is an effort to provide mail protocol utility for...
>
>> Perhaps provide a “default” MailAdapter? In that case, then the factory
>> could even just take an email and a SieveScript InputStream and apply the
>> default MailAdapter. The method with the MailAdapter signature would only be
>> needed for custom MailAdapters.
>
> JSIEVE (core) don't
I created https://issues.apache.org/jira/browse/JSIEVE-116 based on this
thread.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Benoit Tellier created JSIEVE-116:
-
Summary: Simplify JSieve API
Key: JSIEVE-116
URL: https://issues.apache.org/jira/browse/JSIEVE-116
Project: James jSieve
Issue Type: Improvement
[...]
>> - The SieveFactory takes a SieveScript inputstream, and a Mail adapter,
>> and returns a list of Action that results from the sieve script
>> execution against the supplied email.
>
> +1
>
> Perhaps provide a “default” MailAdapter? In that case, then the factory could
> even just take
Thanks for the comments.
>> So I gather than the email must be RFC882 compliant, which means that its
>> implementing class must also be RFC882 compliant. Further, the implementing
>> class must also be RFC5228 compliant. So the email object must effectively
>> be both RFC882 **AND** RFC5882
Hi David.
It looks like you struggled much with badly written javadoc...
> (I am assuming that “RFC32028” is actually RFC3028 [5], which should be
> updated to RFC5228 [6]).
That typo needs to be fixed.
> So I gather than the email must be RFC882 compliant, which means that its
>
Hello David,
> I know you are all probably very busy, but to allow my contribution to
be useful, it would be very nice to get comments on my journey so far.
If I don’t document the “right” thing and run out of time, it would be a
wasted opportunity. :-(
100% agree with that.
Don't hesitate if
David Leangen created JAMES-3193:
Summary: Update Developer Guide
Key: JAMES-3193
URL: https://issues.apache.org/jira/browse/JAMES-3193
Project: James Server
Issue Type: Task
16 matches
Mail list logo
