[tslug] Re: Mailman config problem, the sequel
Title: [tslug] Re: Mailman config problem, the sequel Chad (Mohler): I can not speak as to the justification for keeping or removing the current configuration that we use at ITS as this is not my area; however, I can tell you that we gladly will add aliases to the central mail hub so that mail for "alias"@truman.edu is delivered to "alias"@"yourmachine".truman.edu Just simply contact the Help Desk (by phone, email, or walk-in) and Gwen can add your entry(ies) to the central alias file. Or, if you prefer, just simply send me (or Gwen) an email with all the aliases you need, and we will glady configure this for you. Chad (Tatro) From: [EMAIL PROTECTED] on behalf of Jon BeckSent: Sat 3/13/2004 12:36 PMTo: [EMAIL PROTECTED]Subject: [tslug] Re: Mailman config problem, the sequel > Mailman seems to work a-OK now, except for one odd problem: any> listserv-related message that the moodle server sends gets the "To:"> return address wrong if the recipient has a truman.edu address- the> return address incorrectly ends in "truman.edu," rather than in> "moodle.truman.edu."This, alas, is not a problem of your configuration or one that you canfix. The problem is that every message that goes through Truman'scentral mail servers gets its headers re-written if they end in.truman.edu. Anyone with a .truman.edu address that gets this messagefrom tslug will notict that the Reply-to: header is set to[EMAIL PROTECTED] instead of the correct [EMAIL PROTECTED]Way back in the old days, when we first connected internet-capablepersonal computers to the fledgling smtp server on campus, this policymade sense. The reason was that those early PCs would send out mailfrom a fully qualified hostname, e.g., [EMAIL PROTECTED], but hadno incoming smtp server that could get a reply. Rewriting the headersto point to a central incoming server that had an alias lookup featuremade it possible for replies to go to an address where they could bereceived.The policy still stands, despite the argument that nowadays manypeople have boxes capable of running incoming smtp servers and validreasons for doing so. Your moodle server is a perfect example.--Jon Beck, PhD mailto:[EMAIL PROTECTED]Assoc Professor, Computer Science 2162 Violette HallTruman State University 660.785.7233Kirksville, MO 63501 http://vh216202.truman.edu/-To get off this list, send email to [EMAIL PROTECTED]with Subject: unsubscribe-
[tslug] Re: Mailman config problem, the sequel
> Mailman seems to work a-OK now, except for one odd problem: any > listserv-related message that the moodle server sends gets the "To:" > return address wrong if the recipient has a truman.edu address- the > return address incorrectly ends in "truman.edu," rather than in > "moodle.truman.edu." This, alas, is not a problem of your configuration or one that you can fix. The problem is that every message that goes through Truman's central mail servers gets its headers re-written if they end in .truman.edu. Anyone with a .truman.edu address that gets this message from tslug will notict that the Reply-to: header is set to [EMAIL PROTECTED] instead of the correct [EMAIL PROTECTED] Way back in the old days, when we first connected internet-capable personal computers to the fledgling smtp server on campus, this policy made sense. The reason was that those early PCs would send out mail from a fully qualified hostname, e.g., [EMAIL PROTECTED], but had no incoming smtp server that could get a reply. Rewriting the headers to point to a central incoming server that had an alias lookup feature made it possible for replies to go to an address where they could be received. The policy still stands, despite the argument that nowadays many people have boxes capable of running incoming smtp servers and valid reasons for doing so. Your moodle server is a perfect example. -- Jon Beck, PhD mailto:[EMAIL PROTECTED] Assoc Professor, Computer Science 2162 Violette Hall Truman State University 660.785.7233 Kirksville, MO 63501 http://vh216202.truman.edu/ - To get off this list, send email to [EMAIL PROTECTED] with Subject: unsubscribe -
[tslug] Re: "Mailman config problem, the sequel"
Dear Chad, I live outside the truman.edu "world" in any sense. I received your email concerning the fact that you have solved most of the Mailman configuration problems, except for the poser you posed. Your email reached me with an "appendage" -- not an attachment, but rather, appended text-in-a-printed-box: "This message has been 'sanitized'. This means that potentially dangerous content has been rewritten or removed. The following log describes which actions were taken." The log, of course, makes no particular sense to me. Since the Mailman program and I-don't-know-what-else in the truman.edu domain appears in question, I don't know how to send you back your message, intact, so you can see how it came through to me. So I've tried the tactic of sending this email both to your personal address ([EMAIL PROTECTED]) and to the [tslug] listserv. If I can support, or assist, you in any other way, please let me know. My contact information should appear at the bottom of this email, as a "signature". If it doesn't, you could email me or call me at 627-2519. Andy C. A. HilgartnerPhone: 660-627-2519 2413 North East Street FAX:660-627-2930 (voice contact first, please) Kirksville MO 63501 Website: www.hilgart.org
