On Sunday 10 June 2007, Sam Varshavchik wrote: > Milan Obuch writes: ... > > >> Having said that, the URL in confirmation requests is taken directly > >> from the URL setting of the mailing list. If the confirmation URL is > >> wrong, fix the mailing list's URL setting. > > > > Well, then maybe we need some doc note stating that local part of mailing > > list address, last slash delimited part of both URL and internal filename > > should be equal... if that's the intention. > > Yes it is. >
OK. > > I would like to have internal list > > directory name different, but if that's not possible, I can live with > > that. I just need to know. > > That's not possible. If you review the docs again, there is a big honking > note in there that says that all mailing lists should have a unique last > path component. webmlm will not start if you put two directories in LISTS > with the same last pathname component. webmlm handles multiple lists, and > it uses the first component in the URL, that follows the part that resolves > to the cgi-bin script, to figure out which list the URL refers to. > > This can only work if all lists have unique last path components. > Then a slight change in docs would be good, in place of For example, if the couriermlm mailing list directory is /var/lists/devel-list, its URL will be “http://servername/cgi-bin/webmlm/devel-list”. better version will be For example, if the couriermlm mailing list directory is /var/lists/devel-list, its URL *MUST* be “http://servername/cgi-bin/webmlm/devel-list”. > > Hm, it works without this call, but not with it. I will try to ask on > > FreeBSD mailing list for more, no idea here yet. > > man 2 mknod tells me for EINVAL (which was the reported error code) > > Creating anything else than a block or character special file (or a > > whiteout) is not supported. > > So this looks like i could not leave this call uncommented. > > Yes, it works, because it assumes that webmlmd will be able to start and > create the socket for real. That's fine and good, except if there was a > permission problem on the directory that, when started for real, would > prevent webmlmd from creating the socket. > OK, understand. My gut feeling is this is necessary in more complicated scenarios with multiple webmlmd running under various UIDs - with simple installation running all daemons under common UID this is enforcable with install script. > >> > I can use OS > >> > specific patch to handle this, but I would like to ask... > >> > >> How exactly to you go about creating a filesystem socket node on > >> FreeBSD? > > > > Looking at source I think actual creation is done in start_daemon() > > function on cgidaemond.c file with socket() call. The same function is > > used in sqwebmaild, and there is no mknod() call. > > So, there's no way to do it except for a real socket() call. I'll change > that. Thanks. I will test the interface a bit more and report back troubles or ask more question if need arises. Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it, use milan in address instead. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
