Results 51 - 75 of about 466 results out of about 2303 pages. (0.87 seconds)
- DOC/What about setting a "Reply-To-" header for the list? . . . 1 match
- == 3.48. What about setting a "Reply-To:" header for the list? == Generally speaking, the Mailman developers consider this to be a bad idea, see [[http://www.unicom.com/pw/reply-
- DOC/What about performance? . . . 1 match
- #redirect DOC/4.11 What about performance?
- DOC/What about VERP? . . . 1 match
- #redirect DOC/4.12 What about VERP?
- DOC/What MTA features are required for use with Mailman 2.1.5? . . . 1 match
- == 5.12. What MTA features are required for use with Mailman 2.1.5? == Your MTA needs to be configured to support VERP addressing. If you don't know what VERP is, see [[../So what
- DOC/WANTED gid 0, GOT gid 12 (group mismatch error) . . . 1 match
- == 1.4. Failure to exec script. WANTED gid 0, GOT gid 12 (group mismatch error) == NOTE: This is the most common and frequent question asked on the Mailman support lists. See als
- DOC/Virtual domain hosting with Mailman? . . . 1 match
- #redirect DOC/4.47 Virtual domain hosting with Mailman?
- DOC/Understanding group mismatch errors - how mailman implements security . . . 1 match
- == 6.16. Understanding group mismatch errors - how mailman implements security == If you have ever seen a group mismatch error and would like to fix it, or are just wondering how
- DOC/Troubleshooting- No mail going out to lists members . . . 1 match
- #redirect DOC/4.78 Troubleshooting- No mail going out to lists members
- DOC/Troubleshooting- No mail going out to lists members . . . 1 match
- #redirect DOC/Troubleshooting- No mail going out to lists members
- DOC/Tracking down elusive subscriber bounces . . . 1 match
- == 3.24. Tracking down elusive subscriber bounces == Some bounce messages returned to Mailman lists as a result of the lists mailing out to its subscribers do not correlate with t
- DOC/There is no message threading in my web-archives . . . 1 match
- == 1.10. There is no message threading in my web-archives == Threaded mail readers like Pipermail don't assemble threads based on the 'Subject:' of the discussion - They use two s
- DOC/The admin web interface is not saving my changes and keeps asking me to re-enter my password -- what is wrong? . . . 1 match
- #redirect DOC/4.45 The admin web interface is not saving my changes and keeps asking me to re-enter my password -- what is wrong?
- DOC/Summary of the mailman bin commands . . . 1 match
- #redirect DOC/4.9 Summary of the mailman bin commands
- DOC/Some browsers do not appear to recognize the admin password for the list . . . 1 match
- == 3.67. Some browsers do not appear to recognize the admin password for the list == Firefox and Safari, and quite possibly other browsers, do not appear to recognize the password
- DOC/So what is this VERP stuff . . . 1 match
- == 2.2. So what is this VERP stuff == See also <[[../4.12 What about VERP?|4.12 What about VERP?]]> and <[[../What MTA features are required for use with Mailman 2.1.5?|What MTA f
- DOC/Setting up Web access using MM list passwords - for Apache . . . 1 match
- == 3.7. Setting up Web access using MM list passwords - for Apache == The Mailman database stores its user passwords in plain text and by default sends them out to the users once
- DOC/Securing Mailman's web GUI by using Secure HTTP-SSL . . . 1 match
- #redirect DOC/4.27 Securing Mailman's web GUI by using Secure HTTP-SSL (HTTPS)
- DOC/SELinux errors after upgrade - RedHat . . . 1 match
- In !RedHat Enterprise Linux you may experience some SELinux errors after a version upgrade. {{{ timestamp hostname setroubleshoot: SELinux is preventing mailmanctl (mailman_mail_t
- DOC/RHEL file changes after version 2.1.5-20 . . . 1 match
- This Document refers to the mailman rpm distributed by !RedHat and its sub communities (CentOS, Fedora, etc.) in the yum install/update process. As of mailman-2.1.5-21, mailman fi
- DOC/Processing old mbox archives with procmail-formail . . . 1 match
- == 3.36. Processing old mbox archives with procmail/formail == My mailman-2.1.4 breaks my old mbox archives when processing them into html(pipermail). As a result, some messages g
- DOC/One of my lists is not sending mail. . . . 1 match
- #redirect DOC/I can't access one of my lists via the web interface. One of my lists is not sending mail.
- DOC/My mailing list archives are messed up and have messages with bad timestamps and in the wrong date order! . . . 1 match
- #redirect DOC/My mailing list archives are messed up and have messages with bad timestamps and in the wrong date order
- DOC/My mailing list archives are messed up and have messages with bad timestamps and in the wrong date order . . . 1 match
- == 3.63. Help! My mailing list archives are messed up and have messages with bad timestamps and in the wrong date order! == Q: I'm seeing some messages in my archives that are sho
- DOC/My change to a source module is inneffective; When do I need to restart Mailman? . . . 1 match
- == My change to a source module is inneffective; When do I need to restart Mailman? == {{{#!wiki note This is specific in detail to Mailman 2.1, but similar considerations apply t
- DOC/Messages that are translated from HTML to plain text have a body like ""-root-8e8Ta4- Permission denied" . . . 1 match
- #redirect DOC/4.22 Messages that are translated from HTML to plain text have a body like ""-root-8e8Ta4- Permission denied"