[prev in list] [next in list] [prev in thread] [next in thread]
List: james-user
Subject: RE: create an archive of a list - can't make it work
From: "Danny Angus" <danny () apache ! org>
Date: 2003-04-29 9:33:43
[Download RAW message or body]
Try putting file:/// instead of file:// in the repository location spec. for absolute path cf relative.
d.
> -----Original Message-----
> From: Jerome Lacoste @ BBC [mailto:lacostejbbc@altern.org]
> Sent: 29 April 2003 10:01
> To: James Users List
> Subject: Re: create an archive of a list - can't make it work
>
>
> finally found out why it wasn't working. James was considering that
> /usr/local/src/james-2.1.2/apps/james was the root of the file system.
>
> Thus /var/mail/list-name was in fact
> /usr/local/src/james-2.1.2/apps/james/var/mail/list-name
>
> A little bit confusing to me, and not very nice when it comes to upgrade
> james.
> It doesn't seem like I made a configuration error to end up in that state.
> I can probably get around this by using links that points back to the
> real root.
>
> Comments?
>
> Jerome
>
>
> Danny Angus wrote:
>
> >Hmm, I tried exactly the same today and it *did* work, but I
> used jdbc and a different matcher.
> >Hope that helps you narrow it down.
> >
> >
> >
> >>-----Original Message-----
> >>From: Jerome Lacoste @ BBC [mailto:lacostejbbc@altern.org]
> >>Sent: 01 April 2003 17:59
> >>To: James Users List
> >>Subject: Re: create an archive of a list - can't make it work
> >>
> >>
> >>Noel J. Bergman wrote:
> >>
> >>
> >>
> >>>>I would like to archive a James mailing list.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>As Nicola pointed out on the Wiki in response to someone else,
> you can do
> >>>this by setting up something like:
> >>>
> >>> <mailet match="RecipientIs=list-name@domain.tld"
> >>> class="ToRepository">
> >>> <repositoryPath>file://var/mail/list-name/</repositoryPath>
> >>> <passThrough> true </passThrough>
> >>> </mailet>
> >>>
> >>>
> >>>
> >>I am trying to set up this archive, but I am apparently failing
> to do so.
> >>I have tried many things, and I am now stuck.
> >>
> >>Here's my full log.:
> >>
> >>1- Added the following block at the beginning of the transport protocol.
> >>
> >> <!-- create an archive of all mails sent to mylist -->
> >> <mailet match="RecipientIs=mylist@mydomain"
> >> class="ToRepository">
> >> <repositoryPath>file://var/mail/mylist/</repositoryPath>
> >> <passThrough> true </passThrough>
> >> </mailet>
> >>
> >> restarted james & sent a message to mylist@mydomain list:
> >>
> >>nothing happened. In the logs, I see that the mailet seems to be
> >>correctly initialized:
> >>
> >>mailstore-2003-04-01-17-52.log:01/04/03 17:52:06 INFO mailstore: added
> >>repository: file://var/mail/mylist/MAIL->org.
> >>apache.james.mailrepository.AvalonMailRepository
> >>mailstore-2003-04-01-18-06.log:01/04/03 18:06:33 INFO mailstore: added
> >>repository: file://var/mail/mylist/MAIL->org.
> >>apache.james.mailrepository.AvalonMailRepository
> >>
> >>but nothing else (e.g. nothing in mailet log saying that the mail was
> >>processed).
> >>
> >>2- Thinking that the program doesn't manage to create /var/mail/mylist,
> >>I tried to manualy create /var/mail/mylist as root
> >>drwxr-sr-x 2 root mail 4096 Apr 1 18:05 mylist/
> >>- restarted james
> >>- sent a message to mylist@mydomain list:
> >>
> >>nothing happened still.
> >>So I turned logging to DEBUG level for the smtpserver mailet and the
> >>mailstore categories, but I couldn't find anything suspicious.
> >>
> >>
> >>3- moved the archive mailet into root processor, in the middle of the
> >>ones that creates the list:
> >> <!-- mylist list -->
> >> <mailet match="CommandForListserv=mylist@mydomain"
> >> class="AvalonListservManager">
> >> <repositoryName>mylist</repositoryName>
> >> </mailet>
> >>
> >> <!-- create an archive of all mails sent to mylist -->
> >> <mailet match="RecipientIs=mylist@mydomain"
> >> class="ToRepository">
> >> <repositoryPath>file://var/mail/mylist/</repositoryPath>
> >> <passThrough> true </passThrough>
> >> </mailet>
> >>
> >> <mailet match="RecipientIs=mylist@mydomain"
> >> class="AvalonListserv">
> >> <membersonly>true</membersonly>
> >> <attachmentsallowed>true</attachmentsallowed>
> >> <replytolist>true</replytolist>
> >> <repositoryName>mylist</repositoryName>
> >> <subjectprefix>[mylist]</subjectprefix>
> >> </mailet>
> >>
> >>restarted james & sent mail to list
> >>
> >>This had a consequence as the following appeared in the logs:
> >>mailet-2003-04-01-18-26.log:01/04/03 18:26:32 INFO James.Mailet:
> >>ToRepository: Storing mail Mail1049214391804-1 in file
> >>://var/mail/mylist/
> >>mailet-2003-04-01-18-28.log:01/04/03 18:28:39 INFO James.Mailet:
> >>ToRepository: Storing mail Mail1049214518879-1 in file
> >>://var/mail/mylist/
> >>
> >>as if something was finally happening. But no files shows in the
> >>/var/mail/mylist/
> >>
> >>4. So I deleted the directory I had manually created (/var/mail/mylist)
> >>and restarted james and sent another mail. Same thing.
> >>
> >>5- I then tried to change the output path to something like
> >>/opt/mail/mylist/ then /opt/mail/mylist (without the trailing /) where
> >>/opt/mail/ is a directory with full permissions for everyone.
> >>Still no luck.
> >>
> >>Logs seems OK though:
> >>mailet-2003-04-01-18-49.log:01/04/03 18:50:27 INFO James.Mailet:
> >>ToRepository: Storing mail Mail1049215826671-1 in file
> >>://opt/mail/mylist/
> >>mailet-2003-04-01-18-51.log:01/04/03 18:51:45 INFO James.Mailet:
> >>ToRepository: Storing mail Mail1049215902469-1 in file
> >>://opt/mail/mylist
> >>
> >>but still not archived...
> >>It seems like this mailet silently fails at some point. The
> DEBUG didn't
> >>enable much in the mailet log file as only INFO message appeared there.
> >>
> >>I am a little bit stuck... Idea anyone?
> >>And BTW why is it worse to have the mailet in the transport processor,
> >>where nothing happens at all, than in the root transport?
> >>
> >>Cheers,
> >>
> >>Jerome
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: james-user-help@jakarta.apache.org
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: james-user-help@jakarta.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic