Well, thats really strange , as all the config files are actually *.xml. They are located in the conf/ dir.
On 26 de febrero de 2014 20:48:43 CET, Jerry M <techst...@malcolms.com> wrote: >ok, I'll try it with the defaults. But I'm really curious that you are >saying all of the config files are *.xml. The docs all refer to them >that way as well. However, in the b4 build and the b5 build, all of the > >configuration files are name "*.conf". Is it just that the decision >was >made to now name them *.conf and everybody still just refers to them as > >*.xml? Or is there something more significant here? Do they have to >be >renamed to *.xml from *.conf as well as removing -template- from the >name? > > >On 2/26/2014 1:36 PM, Juan Larriba wrote: >> Jerry, >> >> James v3b5 just works out-of-the-box with the default settings. At >> first, try to not put your own config files and just rename >> imapserver-template.xml to imapserver.xml and smtpserver-template.xml > >> to smtpserver.xml. This will give you a handy default configuration >> that just works. >> >> If that's not the case, check your system for other kind of problems. > >> I.E: James v3b5 requires Java 1.7 to work. >> >> Regards, >> Juan >> >> El 2014-02-26 17:24, Jerry M escribió: >>> Hi, Juan, >>> >>> Thank for the link. I downloaded the latest b5 build and installed >>> it. I was hopeful. But unfortunately, b5 didn't fix a single >problem >>> that I had in b4. >>> >>> 1) The run.bat "fail 3 out of every 4 times" problem is still >present. >>> But I'll live with that for now. >>> >>> 2) I didn't yet try to see if the wrapper/service install problem is >>> fixed. That's not important now either >>> >>> 3) But the big one that has me completely dead in the water -- the >>> SMTP failure -- is still there. So zero progress with b5. >>> >>> I just copied my customized conf files from my b4 install. I didn't >>> really want to start over on all of that. And I've already gone >over >>> the conf files to see if I could find anything that might be causing >>> this. I figure if I started from scratch again on the confs, I just >>> end up with the same 'mistake' if indeed it was a mistake there. So >I >>> just copied what I had before. If you think that's a problem, tell >>> me. >>> >>> There has been a long chain of notes in this thread. So let me >>> summarize the problem again. >>> >>> -- IMAP works fine >>> -- Database works fine >>> -- SMTP fails with the following NullPointerException in a jmx class >>> every time I try to connect to SMTP (I'm using telnet from the same >>> machine to port 25) >>> >>> INFO 09:45:22,660 | james.smtpserver | Id='30915927' User='' >>> Connection established from 64.34.163.186 >>> DEBUG 09:45:22,660 | james.smtpserver | Id='30915927' User='' Unable >>> to process request >>> java.lang.NullPointerException >>> at >>> >org.apache.james.protocols.lib.jmx.ConnectHandlerStats.increment(ConnectHandlerStats.java:61) > >>> >>> at >>> >org.apache.james.protocols.lib.jmx.AbstractConnectHandlerResultJMXMonitor.onResponse(AbstractConnectHandlerResultJMXMonitor.java:71) > >>> >>> at >>> >org.apache.james.protocols.netty.BasicChannelUpstreamHandler.channelConnected(BasicChannelUpstreamHandler.java:102) > >>> >>> at >>> >org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.run(ChannelUpstreamEventRunnable.java:44) > >>> >>> at >>> >org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:312) > >>> >>> at >>> >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > >>> >>> at >>> >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > >>> >>> at java.lang.Thread.run(Thread.java:722) >>> INFO 09:45:22,676 | james.smtpserver | Id='30915927' User='' >>> Connection closed for 64.34.163.186 >>> >>> Other errors in the log that I've eliminated as being related: >>> >>> -- The malformed URL - invalid protocol "classpath" exceptions just >>> mean it can't find the XSDs which apparently aren't necessary since >>> they still aren't present. >>> >>> -- The "connect refused" exception is bounded by the following two >>> statements: >>> DEBUG 09:44:33,704 | >>> org.springframework.remoting.rmi.RmiRegistryFactoryBean | RMI >registry >>> access threw exception >>> ...... >>> INFO 09:44:33,719 | >>> org.springframework.remoting.rmi.RmiRegistryFactoryBean | Could not >>> detect RMI registry - creating new one >>> >>> This apparently says it tried to find a service for RMI... it >>> wasn't there... so it created one. The fact that the CLI works for >me >>> tells me that this was not really an error, rather just part of >>> startup processing. >>> >>> ------ Since it appears that none of the other exceptions are >critical >>> I only have the one exception above that gives any info as to why >SMTP >>> is failing. However, I noticed that the log entry for "unable to >>> process request" PRECEDES the exception. I guess I'll have to look >>> into the source file to see how close those two are. It could be >that >>> the SMTP failure has already occurred with no logging information >and >>> this exception has nothing to do with SMTP unable to process the >>> request. It sure would be nice if someone from development would >>> talk to me here. >>> >>> Jerry >>> >>> On 2/26/2014 1:18 AM, Juan Larriba wrote: >>>> Hi Jerry, >>>> >>>> you can find the version 3 beta 5 (wich fixes A LOT of bugs from >b4) >>>> in the snapshots repository: >>>> >>>> >http://repository.apache.org/content/repositories/snapshots/org/apache/james/james-server-app/3.0.0-beta5-SNAPSHOT/james-server-app-3.0.0-beta5-20140225.070129-369-app.zip > >>>> Please, could you test with this new version and tell us back if it > >>>> worked for you? >>>> >>>> >>>> El 2014-02-26 07:09, Jerry M escribió: >>>>> There are 10 errors during startup referencing *.xsd files with a >>>>> completely misleading message: MalformedURLException: unknown >>>>> protocol: classpath. But it appears the error is simply that the >XSDs >>>>> don't exist (at least not in the v3-beta4 build I downloaded). But >>>>> I'm assuming that these aren't critical errors. But still, if the >code >>>>> expects the XSDs, why aren't they shipped in the build? I also >get a >>>>> warning about the AMQPersistenceAdapter ReferenceStore is not >valid -- >>>>> recovering.... so I assume that isn't critical either. That's >with >>>>> all of the options in log4j set to DEBUG. These messages do not >show >>>>> up with the default log4j settings. >>>>> >>>>> I tried setting JAMES up as a service. I get error messages that >it >>>>> can't send a start command to the JVM (??). I looked that one up, >and >>>>> it's been an open bug with JAMES for a couple of years (??). This >>>>> confuses me, since I assume SOMEONE is running JAMES 3 as a >service >>>>> over the span of 2 years. Yet not me.... So I now just use the >>>>> run.bat command (BTW... It's on Windows Server 2008). About 3 out >of >>>>> 4 times when I do run.bat, JAMES immediately exits with >"Unexpected >>>>> exception parsing.... spring-server.xml". Restart a few more >times >>>>> and get the same error/abort each time. Then finally one time >>>>> randomly it works and starts up. Looked that error up as well. >>>>> Yup... been an open bug with JAMES for a couple of years. Also, >the >>>>> 'source' zip file for beta 3 has been basically empty (1 java >file) at >>>>> least for 6 months. The beta 5 daily build snapshot folder >doesn't >>>>> contain any bin.zip files (maybe they are somewhere else, but if >so, >>>>> there's no indication as to where). I really don't know if somehow >any >>>>> or all of these startup problems are indirectly causing the >JMX/SMTP >>>>> exceptions. But those are all startup with immediate abort >problems. >>>>> Once I can (finally) get it to start each time, there are no >critical >>>>> errors occurring that I can see during startup time. Just the >>>>> critical failure each time I send an SMTP request in. >>>>> >>>>> Critical bugs that have been open for 2 years; missing files in >the >>>>> build, empty source zip; missing bin zips in the beta 5 build >folders; >>>>> the lack of any presence of developers on this mail list.... all >of >>>>> this is making me wonder if JAMES has been totally abandoned. Is >>>>> anyone minding the store at JAMES? Or if you can explain where >the >>>>> real beta4 source zip and the beta5 bin zips can be found, that >would >>>>> be great. >>>>> >>>>> Thx. >>>>> >>>>> Jerry >>>>> . >>>>> On 2/25/2014 8:30 PM, Girivaraprasad Nambari wrote: >>>>>> Have you verified james-server.log and other logs just to see if >>>>>> any clues >>>>>> are logged while starting james? Any unusal activity there >>>>>> (WARN/ERROR)? >>>>>> >>>>>> >>>>>> On Tue, Feb 25, 2014 at 9:15 PM, Jerry M <techst...@malcolms.com> > >>>>>> wrote: >>>>>> >>>>>>> Giri, >>>>>>> >>>>>>> I have no problem adding users and other commands using the CLI. > >>>>>>> That >>>>>>> works fine. >>>>>>> >>>>>>> JAMES is running on my hosting company's leased server. I've set > >>>>>>> up an >>>>>>> IMAP mail account on Thunderbird on my laptop. IMAP works fine >>>>>>> from my >>>>>>> client. I can create folders on the IMAP database from my local >>>>>>> Thunderbird. I am trying to send from Thunderbird as well. It >>>>>>> fails as we >>>>>>> have been discussing. But Thunderbird does put the email note >>>>>>> I'm trying >>>>>>> to send into the IMAP 'sent' folder. So basically IMAP has zero > >>>>>>> problems >>>>>>> that I can see at this point. Just to reduce the possible >>>>>>> variables, I've >>>>>>> tried using telneting to the SMTP port from the server itself. > >>>>>>> As soon as >>>>>>> telnet tries to connect, I get an immediate "451 Unable to >>>>>>> process request" >>>>>>> which is the same message I see in the Wireshark TCP/IP trace >>>>>>> when I'm >>>>>>> trying to send from Thunderbird on my laptop,. And another >>>>>>> exception stack >>>>>>> trace appears in the log each time I try to telnet. >>>>>>> >>>>>>> Regarding JMX, I also was pretty sure that JMX was management. I > >>>>>>> assumed >>>>>>> it might be also used for monitoring. But if it's solely >>>>>>> management, that >>>>>>> just makes it more confusing why the SMTP server has the need to > >>>>>>> contact >>>>>>> JMX each time an SMTP request comes in. (And either it doesn't >>>>>>> do that on >>>>>>> IMAP requests, or it's working correctly on IMAP requests). But >>>>>>> the main >>>>>>> question is what JAMES is trying to do with JMX on an SMTP >>>>>>> request. I can >>>>>>> only assume that JAMES is trying to talk to JMX at that time >>>>>>> since the >>>>>>> exception with those JMX references is thrown each time an SMTP >>>>>>> request >>>>>>> starts. (???) >>>>>>> >>>>>>> Any ideas why JMX is involved in SMTP processing? >>>>>>> >>>>>>> Jerry >>>>>>> >>>>>>> >>>>>>> On 2/25/2014 7:27 PM, Girivaraprasad Nambari wrote: >>>>>>> >>>>>>>> *Disclaimer:* I am also new to James (fixing issues after >>>>>>>> frustrating days >>>>>>>> >>>>>>>> of research), so my answers may be wrong too. >>>>>>>> >>>>>>>> JMX is management API (not really monitoring API) but being >used >>>>>>>> heavily >>>>>>>> in >>>>>>>> monitoring applications. My understanding so far is, James >using >>>>>>>> this api >>>>>>>> while creating accounts etc., (I think same API is being >>>>>>>> executed while >>>>>>>> calling -adduser from jame-cli.bat). This is my guess. >>>>>>>> >>>>>>>> Were you able to adduser from james-cli.bat? Where is your >client & >>>>>>>> server? >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Giri >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Feb 25, 2014 at 8:15 PM, Jerry M >>>>>>>> <techst...@malcolms.com> wrote: >>>>>>>> >>>>>>>> Hi Giri, >>>>>>>>> I tried localhost and the IP. No difference. The firewall >has >>>>>>>>> been off >>>>>>>>> since yesterday. I tried rebooting. Again, no change. >>>>>>>>> >>>>>>>>> I haven't really programmed much with JMX. But it's a >>>>>>>>> management and >>>>>>>>> monitoring component, right? So why is the SMTP component >even >>>>>>>>> trying to >>>>>>>>> talk to JMX while it is servicing an inbound request? I'm just > >>>>>>>>> trying to >>>>>>>>> figure out what is going on in hopes that it might give me a >>>>>>>>> clue as to >>>>>>>>> what is wrong. >>>>>>>>> >>>>>>>>> Thx >>>>>>>>> >>>>>>>>> >>>>>>>>> On 2/25/2014 6:43 PM, Girivaraprasad Nambari wrote: >>>>>>>>> >>>>>>>>> May be try with localhost instead of IP. This is strongly >>>>>>>>> related to IP >>>>>>>>>> (or) port. >>>>>>>>>> >>>>>>>>>> If you haven't done yet, restart machine, stop firewall for >>>>>>>>>> during >>>>>>>>>> testing >>>>>>>>>> (I know you said firewall is not an issue, still I will try >by >>>>>>>>>> stopping >>>>>>>>>> firewall). >>>>>>>>>> >>>>>>>>>> Thank you, >>>>>>>>>> Giri >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tue, Feb 25, 2014 at 7:32 PM, Jerry M ><techst...@malcolms.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hi Phillip, >>>>>>>>>> >>>>>>>>>>> Thanks for the response and info. My jmx.properties file >has >>>>>>>>>>> jmx.address=127.0.0.1 port=9999 (unchanged from the default >>>>>>>>>>> template). >>>>>>>>>>> I >>>>>>>>>>> can run the james-cli with no problem. So it looks like the > >>>>>>>>>>> registry >>>>>>>>>>> is >>>>>>>>>>> happy with the host ip. >>>>>>>>>>> >>>>>>>>>>> It's interesting that IMAP works fine, but SMTP does not. I > >>>>>>>>>>> don't >>>>>>>>>>> really >>>>>>>>>>> know what all JAMES is doing with JMX. But I would expect >that >>>>>>>>>>> whatever >>>>>>>>>>> types of connections it's trying to do on SMTP that it would > >>>>>>>>>>> be doing >>>>>>>>>>> the >>>>>>>>>>> same on IMAP. Wouldn't it? >>>>>>>>>>> >>>>>>>>>>> Thanks again. But no luck with the fix that worked for you. >>>>>>>>>>> >>>>>>>>>>> Any idea if there are any JAMES developers that monitor this > >>>>>>>>>>> forum any >>>>>>>>>>> more? >>>>>>>>>>> >>>>>>>>>>> Jerry >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 2/25/2014 5:53 PM, Phillip Odam wrote: >>>>>>>>>>> >>>>>>>>>>> Hi Jerry >>>>>>>>>>> >>>>>>>>>>>> Your exception below looks similar to one I came across in >>>>>>>>>>>> the last >>>>>>>>>>>> day >>>>>>>>>>>> and resolved. >>>>>>>>>>>> >>>>>>>>>>>> # using the command ./james-cli.sh -h <private ip> -p 9999 >>>>>>>>>>>> listusers >>>>>>>>>>>> >>>>>>>>>>>> Error connecting to remote JMX agent! >>>>>>>>>>>> java.rmi.ConnectException: Connection refused to host: >>>>>>>>>>>> <public ip>; >>>>>>>>>>>> nested exception is: >>>>>>>>>>>> java.net.ConnectException: Connection timed out >>>>>>>>>>>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket( >>>>>>>>>>>> TCPEndpoint.java:619) >>>>>>>>>>>> at >sun.rmi.transport.tcp.TCPChannel.createConnection( >>>>>>>>>>>> TCPChannel.java:216) >>>>>>>>>>>> at sun.rmi.transport.tcp.TCPChannel.newConnection( >>>>>>>>>>>> TCPChannel.java:202) >>>>>>>>>>>> at >sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129) >>>>>>>>>>>> at >>>>>>>>>>>> javax.management.remote.rmi.RMIServerImpl_Stub.newClient( >>>>>>>>>>>> >>>>>>>>>>>> Unknown >>>>>>>>>>>> Source) >>>>>>>>>>>> >>>>>>>>>>>> The issue ended up being nothing to do with james, the RMI >>>>>>>>>>>> registry >>>>>>>>>>>> was >>>>>>>>>>>> doing a lookup on the machines hostname to determine the IP >to >>>>>>>>>>>> advertise >>>>>>>>>>>> for connecting to the JMX server. >>>>>>>>>>>> >>>>>>>>>>>> To resolve this all I needed to do was make the hostname of >the >>>>>>>>>>>> machine >>>>>>>>>>>> resolve to the private ip of the server (on the server >>>>>>>>>>>> itself) and not >>>>>>>>>>>> the >>>>>>>>>>>> public (since the public ip doesn't allow JMX connections >>>>>>>>>>>> coming in). >>>>>>>>>>>> Then >>>>>>>>>>>> a restart of james picked up the new IP and all resolved... > >>>>>>>>>>>> real head >>>>>>>>>>>> spinner tho as it took quite some time to realise just what > >>>>>>>>>>>> was going >>>>>>>>>>>> on. >>>>>>>>>>>> >>>>>>>>>>>> Hope this helps in your investigation. Feel free to ask for > >>>>>>>>>>>> more >>>>>>>>>>>> detail >>>>>>>>>>>> as I know I haven't gone into specifics here. >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> Phillip >>>>>>>>>>>> >>>>>>>>>>>> On 2/24/14, 10:30 PM, Jerry M wrote: >>>>>>>>>>>> >>>>>>>>>>>> After a very long day, I got James 3 installed and >almost >>>>>>>>>>>> up and >>>>>>>>>>>> >>>>>>>>>>>>> running. IMAP is working and the database tables were >>>>>>>>>>>>> created, etc. >>>>>>>>>>>>> But I >>>>>>>>>>>>> can't get anything to work on SMTP. With default log >>>>>>>>>>>>> levels, i got >>>>>>>>>>>>> these >>>>>>>>>>>>> log entries: >>>>>>>>>>>>> >>>>>>>>>>>>> INFO 21:12:13,150 | james.smtpserver | Id='9288089' >User='' >>>>>>>>>>>>> Connection >>>>>>>>>>>>> established from 99.55.143.34 >>>>>>>>>>>>> DEBUG 21:12:13,150 | james.smtpserver | Id='9288089' >>>>>>>>>>>>> User='' Unable >>>>>>>>>>>>> to >>>>>>>>>>>>> process request >>>>>>>>>>>>> INFO 21:12:13,166 | james.smtpserver | Id='9288089' >User='' >>>>>>>>>>>>> Connection >>>>>>>>>>>>> closed for 99.55.143.34 >>>>>>>>>>>>> >>>>>>>>>>>>> I turned on debug level in all of the logs. And it showed >an >>>>>>>>>>>>> exception >>>>>>>>>>>>> stack dump as well: >>>>>>>>>>>>> >>>>>>>>>>>>> java.rmi.ConnectException: Connection refused to host: >>>>>>>>>>>>> 64.34.163.186; >>>>>>>>>>>>> nested exception is: >>>>>>>>>>>>> java.net.ConnectException: Connection refused: >>>>>>>>>>>>> connect >>>>>>>>>>>>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket( >>>>>>>>>>>>> TCPEndpoint.java:619) >>>>>>>>>>>>> at >>>>>>>>>>>>> sun.rmi.transport.tcp.TCPChannel.createConnection( >>>>>>>>>>>>> TCPChannel.java:216) >>>>>>>>>>>>> at >sun.rmi.transport.tcp.TCPChannel.newConnection( >>>>>>>>>>>>> TCPChannel.java:202) >>>>>>>>>>>>> at >>>>>>>>>>>>> sun.rmi.server.UnicastRef.newCall(UnicastRef.java:340) >>>>>>>>>>>>> at >>>>>>>>>>>>> sun.rmi.registry.RegistryImpl_Stub.list(Unknown Source) >>>>>>>>>>>>> >>>>>>>>>>>>> I have reviewed all of my configuration settings. I'm >sure >>>>>>>>>>>>> I'm doing >>>>>>>>>>>>> something wrong. But this exception message tells me very > >>>>>>>>>>>>> little >>>>>>>>>>>>> other >>>>>>>>>>>>> than it is refused. I'm pretty sure it's not a firewall >>>>>>>>>>>>> issue. I >>>>>>>>>>>>> can get >>>>>>>>>>>>> through to port 25 as indicated that log entries appear. >>>>>>>>>>>>> It fails >>>>>>>>>>>>> when >>>>>>>>>>>>> running telnet from my local client as well as running >>>>>>>>>>>>> telnet on the >>>>>>>>>>>>> server. And since it appears to be at the TCPIP >connection >>>>>>>>>>>>> level, I >>>>>>>>>>>>> don't >>>>>>>>>>>>> think it has anything to do with SMTP authorization. >>>>>>>>>>>>> >>>>>>>>>>>>> I had an earlier post about mixing v2 and v3 instances on >>>>>>>>>>>>> the same >>>>>>>>>>>>> server. I am doing that. But v2 is configured to listen >>>>>>>>>>>>> only on one >>>>>>>>>>>>> IP >>>>>>>>>>>>> address, and v3 is configured to listen on a separate IP >>>>>>>>>>>>> address (as >>>>>>>>>>>>> far as >>>>>>>>>>>>> I can tell...) v2 is still running fine. I've checked to >>>>>>>>>>>>> configurations >>>>>>>>>>>>> of both. But that doesn't mean I didn't miss something. >>>>>>>>>>>>> >>>>>>>>>>>>> Can someone explain the problem or give me something else >i >>>>>>>>>>>>> can look >>>>>>>>>>>>> at >>>>>>>>>>>>> that might indicate the problem? >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks. >>>>>>>>>>>>> >>>>>>>>>>>>> Jerry >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >------------------------------------------------------------ >>>>>>>>>>>>> --------- >>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>> server-user-unsubscr...@james.apache.org >>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>> server-user-h...@james.apache.org >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >------------------------------------------------------------ >>>>>>>>>>>>> --------- >>>>>>>>>>>>> >>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>> server-user-unsubscr...@james.apache.org >>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>> server-user-h...@james.apache.org >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ----- >>>>>>>>>>>> No virus found in this message. >>>>>>>>>>>> Checked by AVG - www.avg.com >>>>>>>>>>>> Version: 2014.0.4335 / Virus Database: 3705/7124 - Release >>>>>>>>>>>> Date: >>>>>>>>>>>> 02/25/14 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >------------------------------------------------------------ >>>>>>>>>>>> --------- >>>>>>>>>>>> >>>>>>>>>>> To unsubscribe, e-mail: >server-user-unsubscr...@james.apache.org >>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>> server-user-h...@james.apache.org >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ----- >>>>>>>>>> No virus found in this message. >>>>>>>>>> Checked by AVG - www.avg.com >>>>>>>>>> Version: 2014.0.4335 / Virus Database: 3705/7124 - Release >Date: >>>>>>>>>> 02/25/14 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >--------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: >server-user-unsubscr...@james.apache.org >>>>>>>>> For additional commands, e-mail: >server-user-h...@james.apache.org >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> ----- >>>>>>>> No virus found in this message. >>>>>>>> Checked by AVG - www.avg.com >>>>>>>> Version: 2014.0.4335 / Virus Database: 3705/7124 - Release >Date: >>>>>>>> 02/25/14 >>>>>>>> >>>>>>> >>>>>>> >--------------------------------------------------------------------- >>>>>>> >>>>>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>>>>> For additional commands, e-mail: >server-user-h...@james.apache.org >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> No virus found in this message. >>>>>> Checked by AVG - www.avg.com >>>>>> Version: 2014.0.4335 / Virus Database: 3705/7124 - Release Date: >>>>>> 02/25/14 >>>>> >>>>> >>>>> >--------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>> >>>> >--------------------------------------------------------------------- >>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>> >>>> >>>> >>>> ----- >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com >>>> Version: 2014.0.4335 / Virus Database: 3705/7126 - Release Date: >>>> 02/26/14 >>>> >>>> >>> >>> >>> >--------------------------------------------------------------------- >>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>> For additional commands, e-mail: server-user-h...@james.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2014.0.4335 / Virus Database: 3705/7126 - Release Date: >02/26/14 >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >For additional commands, e-mail: server-user-h...@james.apache.org
