All,
I am trying to use rc.local.s10.mhonarc from http://www.ha-schneider.de/software/smartlist/ to set up an archive for a mailing list.
I have renamed rc.local.s10.mhonarc to rc.local.s30 and added following line to rc.custom
RC_LOCAL_SUBMIT_30 = rc.local.s30
rc.local.s10 and rc.local.s20 are already in use and since I do not know how to merge the recipe in rc.local.s10.mhonarc with either of the two, I renamed it to rc.local.s30 and added a new line in rc.custom.
Could someone please help me understand as to how it all works.
Thanks Nishi
"NK" == Kapoor, Nishikant X Nishikant.X.Kapoor@xcelenergy.com writes:
NK> All, I am trying to use rc.local.s10.mhonarc from NK> http://www.ha-schneider.de/software/smartlist/ to set up NK> an archive for a mailing list. NK> I have renamed rc.local.s10.mhonarc to rc.local.s30 and NK> added following line to rc.custom
NK> RC_LOCAL_SUBMIT_30 = rc.local.s30
RC_LOCAL_SUBMIT_xx are included in rc.submit (look for "INCLUDERC=$RC_LOCAL_SUBMIT_xx"). RC_LOCAL_SUBMIT_30 is not used, so your setting has no effect.
NK> rc.local.s10 and rc.local.s20 are already in use and NK> since I do not know how to merge the recipe in NK> rc.local.s10.mhonarc with either of the two, I renamed it NK> to rc.local.s30 and added a new line in rc.custom.
I see. I have a problem like this in most of my lists. I used to just concatenate these files, but I now create a new rc.local.s10 (or whatever) which just includes the desired files, like this:
# ---------------- snip ---------------- INCLUDERC = ../.etc/rc.local.s10.fax INCLUDERC = rc.local.s10.mhonarc # ---------------- snip ----------------
I think this better in case of changes to one of them (at least, if the cahnge is to appear in all). Some of my rc.local.sxx files contain four or five INCLUDERC lines.
I have a lot of lists, and many of these rc.local files are used by several of them, so I have put them into .etc (see the "rc.local.s10.fax" above). It may be a better idea to create a new directory for them.
Hans-Albert
"HAS" == Hans-Albert Schneider Hans-Albert.Schneider@mchp.siemens.de writes:
"NK" == Kapoor, Nishikant X Nishikant.X.Kapoor@xcelenergy.com writes:
NK> All, I am trying to use rc.local.s10.mhonarc from NK> http://www.ha-schneider.de/software/smartlist/ to set up NK> an archive for a mailing list. I have renamed NK> rc.local.s10.mhonarc to rc.local.s30 and added following NK> line to rc.custom
NK> RC_LOCAL_SUBMIT_30 = rc.local.s30
HAS> RC_LOCAL_SUBMIT_xx are included in rc.submit (look for HAS> "INCLUDERC=$RC_LOCAL_SUBMIT_xx"). RC_LOCAL_SUBMIT_30 is HAS> not used, so your setting has no effect.
Sorry, I forgot to give you the overall picture:
After loading rc.init (global initializations) and rc.custom (per-list customization), $RC_LOCAL_SUBMIT_00 is processed. This means that *all* mails are seen by this file, even misdirected subscribe messages and other stuff you don't want to distribute. (Subscribe and unsubscribe mails should go to list-request@your.dom.ain, but it is a common mistake to send them to list@your.dom.ain.)
Then, some sanity checks are done: It may not be too large, may not come from a daemon (that might be a misdirected bounce message), may not look like an administrative request (misdirected un/subscribe etc), and may not bear the lists stamp (to avoid mail loops; see below).
If the mail passes all these tests and the sender may post to the list (the sender is on the accept list, or foreign_submit is off), the $RC_LOCAL_SUBMIT_10 gets its hands on the mail.
Next come some special purpose handling:
- If the list is moderated and the mail has not yet been approved by a moderator, it is forwarded to the moderators for approval. Finished.
- If desired, the sender is forcibly subscribed (unless on the reject list).
- If this list is digested, do digest processing. Finished.
Now the mail gets archived, and the header manipulated (e.g., "Received:" headers are removed (as are some others), list specific headers are added (including the anti-loop stamp mentioned above), and a dummy "Subject:" is added if missing).
Now comes $RC_LOCAL_SUBMIT_20, and immediately sfter that the message is distributed.
It is therefore important to think about which rc.local.* file is appropriate for which recipes you add. In case of MHonArc archiving the messages, it is mostly a matter of taste whether to call it in rc.local.s10 or rc.local.s20. However, if your list is moderated, you will prefer the latter (after approval); if it is digested, the former seems mandatory, since rc.local.s20 is never reached in this case (if I interpret rc.submit correctly).
Hans-Albert
smartlist@lists.rwth-aachen.de
-
Hans-Albert Schneider -
Kapoor, Nishikant X