Re: [hypermail] Majordomo-Hypermail

Jaysheel Mehd writes:
> Hi All,
>
> I am planning to integrate majordomo with hypermail for viewing the
> archives through the web. I have majordomo working fine. I have
> currently defined the archive of list through the wrapper.
>
> As mentioned in the config of archives fro Hypermail, I have defined the
> lists.h and makefile. I also compiled and installed after making
> changes. Now, I want to integrate it with majordomo. As mentioned in the
> README:
>
> "then make sure that the ftp mailbox directory is symlinked
> to ~majordomo/Archives/listname directory so that this scheme does
> not break majordomo. DO NOT HAVE MAJORDOMO DO ANY ARCHIVING."
>
> These statements seems contradictory to me, mostly I am missing some
> point here to integrate both the functionality. Also, as mentioned do I
> need to put the alias

Your choice. There is no need to have multiple copies of the archives unless that is what you what. The hypermail functionality normally archives the files in a web document root directory. You do not want the mailing list facility under that same facility. You may want to assure the INDEX and GET functionality supplied by majordomo still works. To make that happen. symlink the mailbox archive directory to where majordomo could retrieve the mailbox files archived by msg2archive.

> wuftpd: "|/usr/local/bin/wuftpdmail"
>
> I am not able to find the binary /usr/local/bin/wuftpdmail.
>
> Queries?? In a hanging situation right now!!!!!
>
> Thanks all in advance
> Jaysheel

That was an example of one way to do it. There are otherways supported today.

To use it, compile msg2archive with the specific info for that list. Then rename that file to something unique for that list and put it in the aliases file. The example was for the wu-ftpd mailing list, hence wuftpdmail.

Then just put that exploder address in the subscription list for majordomo. Run newalises and testit.

-- 
Kent Landfield             |  HYPERMAIL: http://www.hypermail.org/ 
Email: kent_at_hypermail.org  |  RFCS: http://www.faqs.org/rfcs/