> 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?
—>
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
>> 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
[...]
>> - 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
>
