[
https://issues.apache.org/jira/browse/IMAP-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning updated IMAP-246:
-
Priority: Minor (was: Major)
Fix Version/s: (was: 0.2)
Issue Type: Improvement
: Niklas Therning
Assignee: Niklas Therning
Fix For: 0.2
If the client doesn't send anything within the configured read timeout the
connection will be closed. During IDLE I think there should be another timeout
which is typically configured to be a lot higher than the ord
[
https://issues.apache.org/jira/browse/IMAP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982080#action_12982080
]
Niklas Therning commented on IMAP-239:
--
An initial implementation has been checke
[
https://issues.apache.org/jira/browse/IMAP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved IMAP-239.
--
Resolution: Fixed
Fix Version/s: 0.2
> Implement I
[X] +1 Yes please release
/Niklas
On 12/27/2010 10:02 PM, Norman Maurer wrote:
Hi there,
as asked for on the ml I prepared to cut a bugfix release of mime4j (0.6.1)
So please review and cast your vote:
https://repository.apache.org/content/repositories/orgapachejames-052/
[ ] +1 Yes please
onse every 30 seconds or so so
the client doesn't timeout. This is what the Dovecot IMAP server does.
Every 30 seconds it sends back something like '* OK Still here' to the
client to prevent timeouts.
Let me know what you think.
/Niklas
On 12/15/2010 05:46 PM, Norman Maurer wrot
Author: niklas
Date: Wed Dec 15 16:00:25 2010
New Revision: 1049622
URL: http://svn.apache.org/viewvc?rev=1049622&view=rev
Log:
Added initial support for IDLE (IMAP-239).
Added:
james/imap/trunk/api/src/main/java/org/apache/james/imap/api/ContinuationReader.java
james/imap/t
Implement IDLE
--
Key: IMAP-239
URL: https://issues.apache.org/jira/browse/IMAP-239
Project: JAMES Imap
Issue Type: New Feature
Components: Protocol
Reporter: Niklas Therning
Assignee: Niklas
in JIRA? I think I have write access to
the Subversion repo (I'm a dormant Mime4j and MINA committer) so I think
I could create a branch if that's what you prefer.
/Niklas
-
To unsubscribe, e-mail: server-dev-uns
there
/Niklas
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
+1 (non-binding)
--
Niklas Therning
www.spamdrain.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/MIME4J-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632115#action_12632115
]
Niklas Therning commented on MIME4J-74:
---
Yes, in the HTTP context it certainl
: 0.4
Reporter: Niklas Therning
Priority: Minor
Fix For: 0.5
The package name under src/test/java doesn't match the one under src/main/java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue o
[
https://issues.apache.org/jira/browse/MIME4J-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-74.
---
Resolution: Fixed
> ArrayIndexOutOfBoundsException in BufferedLineReaderInputStream w
Author: niklas
Date: Wed Sep 17 05:08:43 2008
New Revision: 696267
URL: http://svn.apache.org/viewvc?rev=696267&view=rev
Log:
Resolved issue MIME4J-74
Modified:
james/mime4j/trunk/src/main/java/org/apache/james/mime4j/io/BufferedLineReaderInputStream.java
james/mime4j/trunk/src/
Project: JAMES Mime4j
Issue Type: Bug
Affects Versions: 0.4
Reporter: Niklas Therning
Assignee: Niklas Therning
Fix For: 0.5
The line
int[] shiftTable = new int[255];
should
int[] shiftTable = new int[256];
--
This message is
+1 (non-binding)
/Niklas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[X] +1 Release the packages as James Mime4j 0.4.
/Niklas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Stefano Bagnara wrote:
Niklas Therning ha scritto:
Stefano Bagnara wrote:
Robert Burrell Donkin ha scritto:
On Tue, Aug 5, 2008 at 6:16 PM, Bernd Fondermann
<[EMAIL PROTECTED]> wrote:
On Tue, Aug 5, 2008 at 18:52, Stefano Bagnara <[EMAIL PROTECTED]>
wrote:
IMHO this one
nately what I
thought was consensus a week ago now seems something invented by me ;-)
My questions to Niklas and Bernd are really to understand if
"refinements" is something that can be done on the refactored tree or
if the consensus is now too far from that and we should better revert
i
Bernd Fondermann wrote:
On Mon, Aug 4, 2008 at 13:51, Niklas Therning <[EMAIL PROTECTED]> wrote:
Hi,
I've done some benchmarking of the recent performance improvements in trunk
vs Mime4j 0.3. I must say that the result is very promising! :)
Please let me know if my b
Stefano Bagnara wrote:
Niklas Therning ha scritto:
Oleg Kalnichevski wrote:
Stefano Bagnara wrote:
Robert Burrell Donkin ha scritto:
what else needs to be done before we can ship?
I'm looking here:
https://issues.apache.org/jira/browse/MIME4J?r
uld very much appreciate if the 0.4 release could happen rather
sooner than later. It would be very unfortunate if we had to release
HttpClient 4.0-beta1 without the HttpMime module.
Oleg
I agree with Oleg. IMO these issues can be moved to 0.5.
/Niklas
-
I'm using Ubuntu 8.04 64-bit on a 2.4 GHz core duo Dell laptop.
[EMAIL PROTECTED]:~$ uname -a
Linux niklas-laptop 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC
2008 x86_64 GNU/Linux
[EMAIL PROTECTED]:~$ java -version
java version "1.6.0_06"
Java(TM) SE Runtime Environment
t me know if my benchmarking method is flawed in any way. I'm
attaching the source code of the test tool.
--
Niklas Therning
www.spamdrain.net
import java.io.BufferedInputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStream;
import
[
https://issues.apache.org/jira/browse/MIME4J-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-62.
---
Resolution: Fixed
> Unnecessary qp encoding of SPACE and TAB characters in CodecU
[
https://issues.apache.org/jira/browse/MIME4J-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning closed MIME4J-62.
-
> Unnecessary qp encoding of SPACE and TAB characters in CodecU
[
https://issues.apache.org/jira/browse/MIME4J-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615416#action_12615416
]
Niklas Therning commented on MIME4J-62:
---
Great work Robert! It seems to be wor
Author: niklas
Date: Mon Jul 21 13:41:27 2008
New Revision: 678554
URL: http://svn.apache.org/viewvc?rev=678554&view=rev
Log:
Removed the extra CRLF written by writeTo() when QP encoding is used.
Modified:
james/mime4j/trunk/src/main/java/org/apache/james/mime4j/mes
my response as a comment on the MIME4J-54 issue page.
/Niklas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/MIME4J-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615294#action_12615294
]
Niklas Therning commented on MIME4J-54:
---
IMO, boundaries should only be matche
[
https://issues.apache.org/jira/browse/MIME4J-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615289#action_12615289
]
Niklas Therning commented on MIME4J-62:
---
Stefano, the extra CRLF you see come
[
https://issues.apache.org/jira/browse/MIME4J-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615278#action_12615278
]
Niklas Therning commented on MIME4J-62:
---
It's not trivial to implement rule
to add your knowledge to that threads so we can close them ASAP.
My preference is to have tests that pass in trunk. I'd rather have the
test cases that prove a bug in JIRA. Once a bug has been fixed the test
case will of course be added to trunk to prove that it has been fixed.
/N
[
https://issues.apache.org/jira/browse/MIME4J-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-63.
---
Resolution: Fixed
A fix and test case has been committed.
> QuotedPrintable encoder fails
Author: niklas
Date: Mon Jul 21 03:36:57 2008
New Revision: 678387
URL: http://svn.apache.org/viewvc?rev=678387&view=rev
Log:
Resolved MIME4J-63: CodecUtil.encodeQuotedPrintableBinary() now handles 8bit
bytes as expected.
Modified:
james/mime4j/trunk/src/main/java/org/apache/james/mi
[
https://issues.apache.org/jira/browse/MIME4J-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning reassigned MIME4J-63:
-
Assignee: Niklas Therning
> QuotedPrintable encoder fails on 8bit by
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-59.
---
Resolution: Fixed
I've added the test message and committed a fix for this issue. Th
Author: niklas
Date: Mon Jul 21 03:20:00 2008
New Revision: 678383
URL: http://svn.apache.org/viewvc?rev=678383&view=rev
Log:
Resolved MIME4J-59: The TextBody instances created when parsing a message will
now handle the decoding/encoding of qp and base64 bodies automatically as it
was don
Author: niklas
Date: Mon Jul 21 03:15:41 2008
New Revision: 678382
URL: http://svn.apache.org/viewvc?rev=678382&view=rev
Log:
Saved txt files will now use the mime charset specified for the body part
instead of the Java default.
Modified:
james/mime4j/trunk/src/test/java/org/apache/j
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615190#action_12615190
]
Niklas Therning commented on MIME4J-59:
---
Hmmm, Stefano, I think you have attached
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning reassigned MIME4J-59:
-
Assignee: Niklas Therning
> Quoted-Printable encoded body no more deco
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615186#action_12615186
]
Niklas Therning commented on MIME4J-59:
---
Or maybe it should be
int nextUnsi
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615182#action_12615182
]
Niklas Therning commented on MIME4J-59:
---
I think
int nextUnsigned = next &a
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615179#action_12615179
]
Niklas Therning commented on MIME4J-59:
---
I just checked in a fix for
Affects Versions: 0.4
Reporter: Niklas Therning
Priority: Minor
Fix For: 0.4
ATM we always encode SPACE and TAB. The result is that the output of the
encoding is longer than necessary. According to the MIME RFC:
(3) (White Space) Octets with values of 9 and 32
[
https://issues.apache.org/jira/browse/MIME4J-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-61.
---
Resolution: Fixed
A fix has been comitted
> ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/MIME4J-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning reassigned MIME4J-61:
-
Assignee: Niklas Therning
> ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/MIME4J-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning closed MIME4J-61.
-
> ArrayIndexOutOfBoundsException in CodecUtil.encodeQuotedPrintableBinary for
> large
Author: niklas
Date: Mon Jul 21 02:23:31 2008
New Revision: 678373
URL: http://svn.apache.org/viewvc?rev=678373&view=rev
Log:
Fix for MIME4J-61: Large inputs will not cause ArrayIndexOutOfBoundsException
anymore when encoded using quoted printable.
Modified:
james/mime4j/trunk/src/main/
Project: Mime4j
Issue Type: Bug
Affects Versions: 0.4
Reporter: Niklas Therning
Fix For: 0.4
The exception occurs in write() when outputIndex = outBuffer.length. When this
is true the contents of the buffer should be flushed. But the current code
tries to
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615126#action_12615126
]
Niklas Therning commented on MIME4J-59:
---
I have a fix for this issue which seem
[
https://issues.apache.org/jira/browse/MIME4J-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615121#action_12615121
]
Niklas Therning commented on MIME4J-59:
---
This bug was introduced while fixing MI
[
https://issues.apache.org/jira/browse/MIME4J-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613434#action_12613434
]
Niklas Therning commented on MIME4J-52:
---
Stefano, wouldn't that mean that we
Stefano Bagnara wrote:
Niklas submitted this message as part of MIME4J-52
==
Content-Type: multipart/mixed; boundary="outer-boundary"
Outer preamble
--outer-boundary
Content-Type: text/plain
Foo
--outer-boundary
Content-Type: multipart/alternative; bound
[
https://issues.apache.org/jira/browse/MIME4J-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning updated MIME4J-52:
--
Attachment: 36387089_3.msg
> Infinite loop when nested multipart is missing end bound
: 0.4
Reporter: Niklas Therning
Fix For: 0.4
I'm attaching a message which causes Mime4j to loop indefinitely in non-strict
mode. The message contains badly formatted MIME. The inner multipart has no end
boundary. Mime4j 0.3 handled this situation without any pro
[
https://issues.apache.org/jira/browse/MIME4J-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-48.
---
Resolution: Fixed
Checked in the fix. I've also added the test message I attached as a
[
https://issues.apache.org/jira/browse/MIME4J-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning reassigned MIME4J-48:
-
Assignee: Niklas Therning
> NPE when parsing embedded quoted printable encoded mess
Author: niklas
Date: Fri Jul 11 01:58:23 2008
New Revision: 675871
URL: http://svn.apache.org/viewvc?rev=675871&view=rev
Log:
Resolved MIME4J-48: Messages containing qp or base64 encoded embedded messages
should now parse as expected.
Modified:
james/mime4j/trunk/src/main/java/org/ap
[
https://issues.apache.org/jira/browse/MIME4J-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning closed MIME4J-49.
-
Resolution: Cannot Reproduce
Assignee: Niklas Therning
Turns out the infinite loop was
[
https://issues.apache.org/jira/browse/MIME4J-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612803#action_12612803
]
Niklas Therning commented on MIME4J-49:
---
I'll add a test case for this
>
[
https://issues.apache.org/jira/browse/MIME4J-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612787#action_12612787
]
Niklas Therning commented on MIME4J-49:
---
This very simple patch seems to fix
[
https://issues.apache.org/jira/browse/MIME4J-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612780#action_12612780
]
Niklas Therning commented on MIME4J-48:
---
Hmmm, ok. But I thought the stream wra
: 0.4
Reporter: Niklas Therning
Fix For: 0.4
If a message or body part contains an empty header the parser will loop
indefinitely (when in non-strict mode). Seems like qmail sometimes sends out
failure notices which have body parts with empty headers.
--
This message
[
https://issues.apache.org/jira/browse/MIME4J-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612775#action_12612775
]
Niklas Therning commented on MIME4J-48:
---
After some debugging I've figured
[
https://issues.apache.org/jira/browse/MIME4J-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning updated MIME4J-48:
--
Attachment: 36442979.msg
If you replace =3DNextPart with NextPart this message will
: 0.4
Reporter: Niklas Therning
Fix For: 0.4
When trying to parse a message which contains an embedded quoted printable
message I received a NullPointerException:
Exception in thread "main" java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/MIME4J-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-47.
---
Resolution: Fixed
Fix Version/s: 0.4
Thanks Oleg, your patch has been applied
[
https://issues.apache.org/jira/browse/MIME4J-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning closed MIME4J-47.
-
> Nested multipart messages with non-empty epilogue cause indefinite l
Author: niklas
Date: Thu Jul 10 12:37:09 2008
New Revision: 675695
URL: http://svn.apache.org/viewvc?rev=675695&view=rev
Log:
Resolved MIME4J-47: Applied patch contributed by Oleg Kalnichevski.
Modified:
james/mime4j/trunk/src/main/java/org/apache/james/mime4j/MimeBoundaryInputStream.
[
https://issues.apache.org/jira/browse/MIME4J-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning reassigned MIME4J-47:
-
Assignee: Niklas Therning
> Nested multipart messages with non-empty epilogue ca
[
https://issues.apache.org/jira/browse/MIME4J-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning updated MIME4J-47:
--
Attachment: 36368753.msg
And here's the message
> Nested multipart messages with n
: Bug
Affects Versions: 0.4
Reporter: Niklas Therning
I'm attaching a very simple message which causes the current version of Mime4j
to loop indefinitely when the following app is run:
public static void main(String[] args) throws IOException {
String msg = "36
pos/asf/james/site/trunk/www/mime4j/index.html
Stefano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Looks good to me except that the News and Status page says that the next
rele
you are uncertain of
what line separator is used in the mail you're trying to parse or if
it's always just LF (\n). If you always have CRLF (\r\n) in your mails
you don't need to use it.
HTH
/Niklas
-
To unsu
time it is better
> for mime4j to increase its community/acceptance by helping other
> projects (e.g. commons-upload) to use mime4j. IMHO collecting users that
> depends on the library is the best thing to ensure that future design
> choices will satisfy anyone needs.
>
> At the
[
https://issues.apache.org/jira/browse/MIME4J-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529337
]
Niklas Therning commented on MIME4J-6:
--
The idea is to make the Message class and friends be able to do this so
[
https://issues.apache.org/jira/browse/MIME4J-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528701
]
Niklas Therning commented on MIME4J-6:
--
If the mail is read from disk Mime4j could scan it first to find the
Author: niklas
Date: Mon Jul 2 07:33:02 2007
New Revision: 552505
URL: http://svn.apache.org/viewvc?view=rev&rev=552505
Log:
Fixed a StringIndexOutOfBoundsException when parsing addresses with local parts
containing an empty quoted-string followed by a dot-atom.
Modified:
james/mi
x27;s been fixed
in trunk.
/Niklas
Rickard Ekeroth wrote:
>
> Hello Niklas!
>
> I don't know if this is the correct way to report what I think is a
> bug in Mime4J version 0.3...
>
> I think that the code in the static initializer of the class
> 'TempStorage'
[
https://issues.apache.org/jira/browse/MIME4J-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning closed MIME4J-17.
-
> Initialization of custom TempStorage doesn
[
https://issues.apache.org/jira/browse/MIME4J-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved MIME4J-17.
---
Resolution: Fixed
> Initialization of custom TempStorage doesn
Author: niklas
Date: Tue Jun 5 05:46:17 2007
New Revision: 544474
URL: http://svn.apache.org/viewvc?view=rev&rev=544474
Log:
Resolved issue MIME4J-17. Initialization of custom TempStorage using system
properties should now work.
Modified:
james/mime4j/trunk/src/main/java/org/apache/j
: 0.3
Reporter: Niklas Therning
Assignee: Niklas Therning
Fix For: 0.4
Rickard Ekeroth reported the following bug to the ML:
I think that the code in the static initializer of the class 'TempStorage' is
not correct when trying to find a custom class t
am in an undefined state for example when parsing
> is stopped with MimeStreamParser.stop(). Is this OK?
>
I think it would be ok. Actually, I'm not sure that the current code
leaves the stream in a defined state when stop() is called.
Norman Maurer wrote:
> Hi all,
>
> I finally found the time todo the releases for mime4j and james-project.
> I will try to add a small HOWTO later for the release stuff with maven.
>
> So please review and vote:
> http://people.apache.org/~norman/staging-repository/
>
[
https://issues.apache.org/jira/browse/MIME4J-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498619
]
Niklas Therning commented on MIME4J-5:
--
Jukka, please, go ahead and give it a try. I'm not working on
[
https://issues.apache.org/jira/browse/MIME4J-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495869
]
Niklas Therning commented on MIME4J-5:
--
Please move to 0.4. IMO, even if it gets fixed soon it will require a lot
Stefano Bagnara wrote:
> Niklas Therning ha scritto:
>
>> Noel J. Bergman wrote:
>>
>>>> RAT indicates that the following files are missing proper licensing
>>>>
>>>>
>>> headers
>>>
>>> They we
Noel J. Bergman wrote:
>> RAT indicates that the following files are missing proper licensing
>>
> headers
>
> They were part of the initial import by Joe Cheng, and appear to have been
> untouched since by anyone. Has anyone asked Joe or Niklas about them?
>
&g
the first official ASF release than later.
>
> I can take care of this in the next days if no one will precede me.
>
>
I'm fine with the package change. Better do it sooner than later.
--
Niklas Therning
www.spamdrain.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
>
> Well, when I landed to James mime4j was already there. So I just thought
> that legal issues have been solved more than 2 years ago when the
> sourcecode has been committed to ASF repository.
>
> Can anyone confirm this?
>
Hi Norman,
You're more than welcome to handle this. Thanks man!
/Niklas
Norman Maurer wrote:
> Hi Niklas,
>
> thx for taking care :-)
> Is it ok for you when i "manage" the release stuff ? If not just step in ;-)
>
> bye
> Norman
>
> Niklas Therning
the download URL
will be though.
/Niklas
Stefano Bagnara wrote:
> Hi Norman,
> first of all thank you for taking care of this, too.
>
> I guess the release version should probably be 0.3 (the last release
> on sourceforge is 0.2).
>
> Before tagging and voting we should change th
Author: niklas
Date: Thu Apr 26 05:22:06 2007
New Revision: 532724
URL: http://svn.apache.org/viewvc?view=rev&rev=532724
Log:
Removed all references to Sourceforge.
Added a note about mvn eclipse:eclipse not generating the .classpath properly
for the javacc generated sources.
Modi
gt;>> java.nio.charset.Charset.forName(charsetName);
>>> if (c == null) {
>>> -//TODO: Check what touse as default
>>> c = java.nio.charset.Charset.forName("ISO8859-1");
>>> }
>>>
&g
using
Message.writeTo(). When parsing to a Message object the default is to
use ISO8859-1 if the charset specified in the message is unknown or not
specified.
--
Niklas Therning
www.spamdrain.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, if possible please post the source of the message you are parsing.
That will help us fix the first problem.
Also, make sure you don't close() the OutputStream you are writing to
before your call to Message.writeTo().
/Niklas
Norman Maurer wrote:
> Can you show use the emai
Norman Maurer wrote:
> Niklas Therning schrieb:
>
>> Norman Maurer wrote:
>>
>>
>>> Hi guys,
>>>
>>> after using mime4j a little bit to implement some actions which should
>>> get taken for specific message parts I'm a
1 - 100 of 132 matches
Mail list logo
