>Hey Joe (I guess?), > >thanks for participating. +1
I'm currently setting up a fresh VM and try to >do some testing myself - but it could very well be an overall issue that >james-3.4 is broken in a way it doesn't store any incoming mails at all, >no matter of the type of storage. > I think that is the case. *Definitely* no mail delivered anywhere on the system with maildir storage. And I say again although I am a james newbie, I've lots of real life email experience as sys admin with dovecot and exim and my own java based webmail stuff. I just reverted to the standard Derby storage config; I saw the console output that there was a successful connection to Derby. To rule out any oddness/incompatibility with client stuff, I then tested using only telnet. As discussed before - I talk smtp at port 25 and James reports accepting message there and also in it's logs it says the message is spooled. I then talk imap at port 143 (*** represents the password):- telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK JAMES IMAP4rev1 Server Server skaro is ready. a login a login david@localhost *** a OK LOGIN completed. a list "" "*" * LIST (\HasNoChildren) "." "INBOX" a OK LIST completed. a examine INBOX * FLAGS (\Answered \Deleted \Draft \Flagged \Seen) * 0 EXISTS * 0 RECENT So same as with maildir - the message does not reach the Derby INBOX I'm happy to do further testing, but as I said the docs seem out of date so I don't know where to look myself and I'm out of ideas at the moment. -- David Matthews [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
