Hi Eric, Thanks for your reply.
Yes, we want to change the default behaviour for local recipients. We dont want the emails to be stored in the database. What should be changed in the configuration file to achieve this? Thanks Naveen ________________________________________ From: Eric Charles [e...@apache.org] Sent: Saturday, January 05, 2013 9:19 AM To: James Users List Subject: Re: Apache James -Question On 04/01/2013 18:15, Naveen Gopi / Livecom wrote: > Hi Eric, > > Thanks a lot for you reply. Either of the two will work for us. > > -> We are not using IMAP, but POP3, and in POP3 the mail gets deleted after > its marked DELETED. But still the behaviour is how you have explained From http://www.ietf.org/rfc/rfc1939.txt, the DELE command: The POP3 server marks the message as deleted. Any future reference to the message-number associated with the message in a POP3 command generates an error. The POP3 server does not actually delete the message until the POP3 session enters the UPDATE state. > -> If we want spooling, what should be the mailet configuration? Should the > class be changed? > The default spooling configuration doesn't store the mail in the mailbox for non local recipients. It does for local recipients, which is the excepcted normal behaviour. If you want to change that default behavior, just describe what you want to achieve, and we'll be able to sketch a configuration. > Thanks > Naveen > ________________________________________ > From: Eric Charles [e...@apache.org] > Sent: Friday, January 04, 2013 5:55 PM > To: James Users List > Subject: Re: Apache James -Question > > When you setFlag(..DELETED), you only change the state of the persisted > mail, but don't says "remove it" > > You need to call e.g. the IMAP command EXPUNGE > > From http://www.ietf.org/rfc/rfc3501.txt: > The EXPUNGE command permanently removes all messages that have the > \Deleted flag set from the currently selected mailbox. Before > returning an OK to the client, an untagged EXPUNGE response is > sent for each message that is removed. > > > You are talking here about > > - direct JAVA API call (in that case, there are some methods called > delete()... that could call), > > > - spooling: if the mail is not for a user managed by James, it will be > not persisted. If you want to be sure it will never be persisted, you > can configure mailets to map your specific requirements. > > Thx, Eric > > > On 04/01/2013 17:30, Naveen Gopi / Livecom wrote: >> Hi Eric, >> >> I have marked the mail to be deleted through the JAVA API. Something like >> this message.setFlag(Flags.Flag.DELETED, true); >> >> When I accessed the derby database, and checked the JAMES_MAIL table, I can >> see that there are lots of mails which are flagged as DELETED but never >> removed from the database. >> select count(*) from JAMES_MAIL where MAIL_IS_DELETED=0; returns me >> around 1500. >> >> What I really want is I dont want to store the mails in the derby database. >> Is there any way to do this? My mailet looks like this, is there any >> configuration that I can do so that the no mails are store in my Derby >> database? >> >> <mailet match="All" class="RemoteDelivery"> >> <mail.smtp.localhost>beta.casengo.com</mail.smtp.localhost> >> <outgoingQueue>outgoing</outgoingQueue> >> ...... >> </mailet> >> >> Thanks >> Naveen >> >> >> ________________________________________ >> From: Eric Charles [e...@apache.org] >> Sent: Friday, January 04, 2013 5:18 PM >> To: James Users List >> Subject: Re: Apache James -Question >> >> Hi, >> >> What do you mean by marking the mail as deleted? >> Are you accessing via POP, IMAP or directy JAVA API? >> >> Also, Read https://kb.wisc.edu/cae/page.php?id=16718 for background on >> "deleted". It all depends on the client you use. >> >> Thx, >> >> Eric >> >> >> On 04/01/2013 16:40, Naveen Gopi / Livecom wrote: >>> Hi , >>> >>> Unfortunately we are having a small problem. We are using Apache Derby with >>> James and we can see that the database is growing really fast eating up lot >>> of disk space and making James a lot slower. >>> >>> The growing files are inside apache-james/var/store/derby/seg0. We have >>> made sure that after fetching we are marking the email as deleted. But we >>> still dont understand why the database is growing >>> >>> It will be great will anyone can throw some lights on this problem. Your >>> help will be highly appreciated. >>> >>> Thanks >>> Naveen >>> >> >> --------------------------------------------------------------------- >> 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 >> > > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- 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
