Re: m2 & experimental imap in trunk

On 7/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: Stefano Bagnara ha scritto: > robert burrell donkin ha scritto: >> On 7/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: >>> On 7/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: - many imap classes use tabs indentation instead of s

[jira] Commented: (JAMES-795) CLONE -If FetchMail cannot parse Received header, it cannot process the message even with

[ https://issues.apache.org/jira/browse/JAMES-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510381 ] sravan commented on JAMES-795: -- Seems this issue is not yet fixed. I could still replicate this issue. I was able to do a

[jira] Created: (JAMES-795) CLONE -If FetchMail cannot parse Received header, it cannot process the message even with

CLONE -If FetchMail cannot parse Received header, it cannot process the message even with --- Key: JAMES-795 URL: https://issues.apach

Re: JDK 1.5 for the "next-major" ?

On 7/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: i'm agnostic my plan had been to allow switching over to java5 on a the module level since this retains the possibility of a release containing dual configurations. this would mean factoring out modules from core before starting to intr

Re: JMX, trunk and experiments!

If I recall correctly, the problem with James under Java5 is that MX4J is not an option here, since Phoenix messes things up (classloader problems as far as I remember). This is mentioned nowhere in the docs, and since Java 5 is common on most desktops these days, this is also the version most

Re: JMX, trunk and experiments!

If I recall correctly, the problem with James under Java5 is that MX4J is not an option here, since Phoenix messes things up (classloader problems as far as I remember). Built-in JMX server works as described. At least, I got it running. Can you please report what exactly is the problem you are

Re: JMX, trunk and experiments!

Ahmed Mohombe wrote: While IMAP does define sufficient defaults (mostly the port) JMX has many configuration options (built-in JMX server vs. third party, authentication vs. no authenticaion, credentials, IP-bindings, ports, protocols...). You are the developers of JAMES so you *can* define JM

Re: IMAP and MIME

Bernd Fondermann ha scritto: > robert burrell donkin wrote: >> [...] >> should all media types and sub types be capitalized? > > +0 (i.e. I have no clue) > > Bernd Idem, Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] F

Re: JMX, trunk and experiments!

Bernd is the man for JMX on JAMES ;-) , btw if I remember correctly to enable JMX you have to play with the phoenix's kernel.xml file, so it is a bit different from other JAMES Server configurations. Here is an interesting guide by Bernd: http://wiki.apache.org/james/ConfigureJmx Yes, I know that

Re: JMX, trunk and experiments!

While IMAP does define sufficient defaults (mostly the port) JMX has many configuration options (built-in JMX server vs. third party, authentication vs. no authenticaion, credentials, IP-bindings, ports, protocols...). You are the developers of JAMES so you *can* define JMX defaults too (in the

Re: IMAP and MIME

robert burrell donkin wrote: AIUI MIME definitions for Content-Type media type and subtype specify case insensitivity. Most email messages in the wild now use lower case. IMAP uses MIME types when FETCHing information about messages. IMAP4rev1