This page lists files in the current directory. You can view content, get download/execute commands for Wget, Curl, or PowerShell, or filter the list using wildcards (e.g., `*.sh`).
wget 'https://lists2.roe3.org/mdrone/doc/listservs-and-members.txt'Area-V-PD
Anna Dyson <adyson@roe41.org>
Annette Hartlieb <ahartlieb@roe3.org>
Julie Wollerman <juliewollerman@roe3.org>
Kelly West <kwest@sccroe50.org>
MD <mdrone@gmail.com>
Mary Beth McCormick <mmccormick@roe45.net>
Michelle Mueller <mmueller@roe40.com>
Matt Weld <mweld@roe3.org>
Ryan Wamser <rwamser@roe40.com>
area-v-reg-supts
Annette Hartlieb <ahartlieb@roe3.org>
Chris Diddlebock <cdiddlebock@roe45.net>
Chad Hoesman <choesman@roe40.com>
Julie Wollerman <juliewollerman@roe3.org>
Kelton Davis <kdavis@roe45.net>
Kelton Davis <kdavis@roe45.org>
MD <mdrone@gmail.com>
Mark Eichenlaub <meichenlaub@sccroe50.org>
Michelle Mueller <mmueller@roe40.com>
Matt Weld <mweld@roe3.org>
Robert Werden <rwwerden@co.madison.il.us>
Staci Oliver <soliver@sccroe50.org>
Tricia Blackard <tcblackard@co.madison.il.us>
bookkeepers
Annette Hartlieb <ahartlieb@roe3.org>
Ashley Matthews <amatthews@vandals203.org>
Alice Newlin <anewlin@tcusd3.org>
Aimee Shelton <ashelton@hillsboroschools.net>
Amy Zimmerman <azimmerman@vandals203.org>
Ellen Broom <broome@effingham.k12.il.us>
Ellen Broom <broome@unit40.org>
Cinde Carroll <ccarroll@stelmo.org>
Donna Horath <dhorath@southcentralschools.org>
Donna Kroening <dkroenin@altamontschools.org>
Donna Lemon <dlemon@panhandleschools.com>
Dena Petroline <dpetroline@bccu2.org>
Dawn Rosborough <drosborough@roe3.org>
Deanna Tarter <dtarter@nptsped.com>
Della Witter <dwitter@litchfieldpanthers.org>
Emily Laesch <elaesch@bccu2.org>
Ginny Keen <gkeen@southcentralschools.org>
Kristin Harvey <harveyk@unit40.org>
Heather McCleary <hmccleary@bccu2.org>
Heather Phillips <hphillips@panaschools.com>
Iliana Cuellar <icuellar@tcusd3.org>
Jennifer Christer <jennifer.christer@panaschools.com>
Julie Flach <jflach@dieterichschools.org>
Jenny Hoeske <jhoeske@roe3.org>
Julie LeBeane <jlebeane@tcusd3.org>
Jennifer Mitchell <jmitchell@bccu2.org>
JoAnn Bumgardner <joann@ramseycusd.org>
Jacy Schaub <jschaub@bcusd201.com>
Julie Wollerman <juliewollerman@roe3.org>
Jill Wright <jwright@roe3.org>
Krystal Goebel <kgoebel@dieterichschools.org>
Kathy Harris <kharris@southforkschools.com>
Kim Miller <kmiller@beechercity.org>
Krystal Mulvaney <kmulvaney@southforkschools.com>
Norma Koester <koestern@ttown.k12.il.us>
Kerry Sims <ksims@ecusd4.com>
Kim Weaver <kweaver@neogacusd3.net>
Laura Butler <lbutler@hillsboroschools.net>
Lela Ferrill <lferrill@ga.mohawks.net>
Sarah Lin <lins@ttown.k12.il.us>
Liz Holcomb <liz.holcomb@midstatespec.org>
MD <mdrone@gmail.com>
Kim Mihlbachler <mihlbachlerk@unit40.org>
Michele Wade <mwade@bccu2.org>
Nicole Blodgett <nblodgett@panaschool.com>
Myra Pruemer <pruemerm@ttown.k12.il.us>
Paula Wright <pwright@roe3.org>
Regina Johnson <rjohnson@mgschools.com>
Rita Kman <rkman@rccu1.net>
Sheryl Busse <sbusse@southcentralschools.org>
Stacy Glasscock <sglasscock@ecusd4.com>
Sharon Langen <sharonlangen@nokomis.k12.il.us>
Susan Janz <sjanz@altamontschools.org>
Shay Jones <sjones@roe3.org>
Staci Carroll <slcarroll@okaw.us>
Susan Sullivan <susansullivan@nokomis.k12.il.us>
Tammy Hadley <thadley@tcusd3.org>
Tammy Nordyke <tnordyke@vandals203.org>
Teresa Redman <tredman@cowdenherrick.org>
Wendy Dulakis <wdulakis@tcusd3.org>
Penny Wiedman <wiedmanp@unit40.org>
Sandy Wieneke <wienekes@unit40.org>
counselors
April Durbin <adurbin@tcusd3.org>
Amber Kidd <akidd@roe3.org>
Ashley Kreke <akreke@dieterichschools.org>
Amy Ruckman <aruckman@altamontschools.org>
Ashley Whitehead <awhitehead@tcusd3.org>
Beth Kern <bekern@vandals203.org>
Bonnie Sowarsh <bsowarsh@panaschools.com>
Darci Harrison <darciharrison@nokomis.k12.il.us>
Dawn Mullholland <dmulholland@bccu2.org>
Elizabeth Finn <efinn@bccu2.org>
Emily Nelson <enelson@roe3.org>
Gail Hardiek <ghardiek@bcusd201.com>
Shannon Hinkle <hinkles@unit40.org>
Jennifer Cearlock <jallen@ramseycusd.org>
Jennifer Anderson <janderson@hillsboroschools.net>
Jennifer Ippolito <jippolito@southforkschools.com>
Jennifer Mesnard <jmesnard@bccu2.org>
Jeb Odam <jodam@tcusd3.org>
Julie Wollerman <juliewollerman@roe3.org>
Kelly Capriotti <kcapriotti@tcusd3.org>
Kari Hagy <khagy@vandals203.org>
Kiley Halbrook <khalbrook@mohawks.net>
Kim Major <kmajor@vandals203.org>
Kaci Reiss <kreiss@roe3.org>
Ashley Kreke <krekea@ttown.k12.il.us>
Karen Ritchie <kritchie@maps-k12.com>
Kate Wagahoff <kwagahoff@roe3.org>
Laura Benhoff <lbenhoff@roe3.org>
Lauren Fowler <lfowler@dieterichschools.org>
Lacy Glenn <lglenn@tcusd3.org>
Lisa DeWerff <lisadewerff@nokomis.k12.il.us>
MD <mdrone@gmail.com>
Amy Miller <millera@unit40.org>
Morgan Stremming <mstremming@stelmo.org>
Jennifer Patton <pattonj@unit40.org>
Priscilla Maxwell <pmaxwell@panaschools.com>
Tara Raddatz <raddatzt@unit40.org>
Cheryl Scanlan <scanlanc@unit40.org>
Steve Dannaman <sdannaman@bccu2.org>
Tammy Bloemer <tbloemer@dieterichschools.org>
Tammy Keller <tkeller@beechercity.org>
Tim Morford <tmorford@hillsboroschools.net>
Vanessa Wright <vwright@beechercity.org>
Emily Icenogle <eicenogle@panaschools.com>
curr-coop
Andrew Beckham <abeckham@roe3.org>
Anita Brown <abrown@tcusd3.org>
afavre@litchfieldpanthers.org
Annette Hartlieb <ahartlieb@roe3.org>
ahaston@panaschools.com
ahopper@panhandleschools.com
Amy Jackson <ajackson@bccu2.org>
Amber Kidd <akidd@roe3.org>
astritzel@hillsboroschools.net
bakerk@unit40.org
Brian Deadmon <bdeadmond@beechercity.org>
Chelle Beck <beckc@unit40.org>
beckg@ttown.k12.il.us
bgarrard@stelmo.org
blipe@hillsboroschools.net
Casey Adam <cadam@panaschools.com>
Cassie Bowman <cbowman@mgschools.com>
Doug Hill <dhill@altamontschools.org>
dreesp@ttown.k12.il.us
dvangiesen@hillsboroschools.net
David Weller <dweller@bccu2.org>
Eric Bruder <ebruder@tcusd3.org>
Eric Swingler <eswingler@bccu2.org>
foxje@unit40.org
Gary Brauns <gbrauns@bccu2.org>
gedwards@ramseycusd.org
hdstrom@panaschools.com
Heaven Harris <hharris@ramseycusd.org>
Hope McBrain <hmcbrain@hillsboroschools.net>
jbenefiel@dieterichschools.org
Joey Daniken <jdaniken@vandals203.org>
jhealy@stelmo.org
jjohnson@tcusd3.org
Jodi Mammoser <jmammose@dieterich.k12.il.us>
jmasten@panhandleschools.com
Jamie Michel <jmichel@vandals203.org>
jmiller@tcusd3.org
Jason Rakers <jrakers@bccu2.org>
Jeremy Rinkel <jrinkel@vandals203.org>
Jerry Tkachuk <jtkachuk@altamontschools.org>
Julie Wollerman <juliewollerman@roe3.org>
Joe Vanzo <jvanzo@roe3.org>
jwebb@panhandleschools.com
jwise@tcusd3.org
jwooters@bcusd201.com
Kris Biggs <kbiggs@altamontschools.org>
Karen Hanfland <khanfland@beechercity.org>
Kara Harris <kharris@bccu2.org>
Kelly Hopwood <khopwood@vandals203.org>
Karen Kuntzman <kkuntzman@tcusd3.org>
Kelly Millburg <kmillburg@panaschools.com>
kschuster@panhandleschools.com
Laura Benhoff <lbenhoff@roe3.org>
lpuzey@tcusd3.org
martenc@unit40.org
MD <mdrone@gmail.com>
Meg File <mfile@bccu2.org>
mgutierrez@hillsboroschools.net
Megan Hanlon <mhanlon@ga.mohawks.net>
Matt Hutchinson <mhutchison@tcusd3.org>
mreeves@hillsboroschools.net
Michelle Rogers <mrogers@southforkschools.com>
mson@bcusd201.com
niebrugg@unit40.org
pbueker@altamontschools.org
Paul Donahue <pdonahue@panaschools.com>
pheyen@hillsboroschools.net
pullent@unit40.org
rachellemcdowell@nokomis.k12.il.us
Kurt Roberts <robertsk@unit40.org>
rtepen@litchfieldpanthers.org
schuette@unit40.org
schwerma@unit40.org
Steve Groll <sgroll@southforkschools.com>
shannagan@stelmo.org
sheehana@ttown.k12.il.us
Scott Kocher <skocher@dieterichschools.org>
tportz@ramseycusd.org
zfrailey@hillsboroschools.net
district-supts
Annette Hartlieb <ahartlieb@roe3.org>
Aaron Hopper <ahopper@panhandleschools.com>
Bill Fritcher <bfritcher@neogacusd3.net>
Bobby Koontz <bkoontz@mgschools.com>
Brad Skertich <bskertich@piasabirds.net>
Ben Theilen <btheilen@ecusd4.com>
Brad Turner <bturner@nashville-k12.org>
Casey Adam <cadam@altamontschools.org>
Chris Clark <cclark@southforkschools.com>
Chris Doughtery <cdougherty@tcusd3.org>
Cary Jackson <cjackson@dieterichschools.org>
Chuck Lane <clane@centraliahs.org>
Dave Meister <dmeister@ga.mohawks.net>
Mark Doan <doanm@unit40.org>
David Powell <dpowell@hillsboroschools.net>
Gregg Fuerstenau <gfuerstenau@litchfieldpanthers.org>
Jason Bauer <jbauer@panaschools.com>
Jeff Strieker <jeffstrieker@gmail.com>
Jennifer Garrison <jgarrison@vandals203.org>
Julie Healy <jhealy@stelmo.org>
Julie Wollerman <juliewollerman@roe3.org>
Kerry Herdes <kherdes@southcentralschools.org>
Kelley Suey <ksuey@nptsped.com>
MD <mdrone@gmail.com>
Mike Gauch <mgauch@harrisburg3.org>
Melissa Ritter <mritter@ramseycusd.org>
Michael Shackelford <mshack@bcusd201.com>
Phil Lark <plark@beechercity.org>
Scott Doerr <scottdoerr@nokomis.k12.il.us>
Steve Phillips <sphillips@rome2.net>
Seth Schuler <sschuler@cowdenherrick.org>
Matt Sturgeon <sturgeonm@ttown.k12.il.us>
Wes Olson <wolson@bccu2.org>
ecrta
aaaschimm@gmail.com
arugala76@hotmail.com
barbrunde@yahoo.com
beckyparker1960@yahoo.com
bev.kopplin3@gmail.com
bhartke@mmtcnet.com
bkhammer@frontiernet.net
bklange2@gmail.com
bkopplin@consolidated.net
blbeck@mchsi.com
blissc@consolidated.net
bloemerj1@frontier.net
bloemerj1@frontiernet.net
bobjlee@frontiernet.net
borries@frontiernet.net
borriesm@hotmail.com
budde54@hotmail.com
camptime1@hotmail.com
carpenter4@consolidated.net
Cathy Freimuth <cfreimuth55@gmail.com>
cgcohorst@mmtcnet.com
chrismette07@gmail.com
cindyhoene@gmail.com
clading@mchsi.com
clbaker@consolidated.net
clmargerum@mchsi.com
cniehausacusd@gmail.com
crisbierman@yahoo.com
csappington60@gmail.com
dadmac5959@live.com
debra.gregory58@gmail.com
deytchison@icloud.com
dibaker@frontiernet.net
djsebright@gmail.com
dkeller55@yahoo.com
dkkutcher@frontiernet.net
dl.lewis@mchsi.com
dmjday1@gmail.com
dmogdon@gmail.com
dnbrum@hotmail.com
dustmary@yahoo.com
ejbwise@hotmail.com
ejshouse@gmail.com
epdtennis@consolidated.net
esbcdj@gmail.com
fnseaman@yahoo.com
fruchtlj@u40gw.effingham.k12.il.us
golfers2@consolidated.net
gregoryhsmith11@gmail.com
habing6@frontiernet.net
hearts1595@gmail.com
Lisa Hoekstra <hook2@mchsi.com>
horsenaround2@mchsi.com
irontriathlete7@yahoo.com
jam837@consolidated.net
jaz6605@hotmail.com
jenks44@consolidated.net
jewb@effingham.net
jhoeske@roe3.org
jjarmstrong@frontiernet.net
jlabell45@gmail.com
jsmjennings@gmail.com
kaymcmahon18@gmail.com
kcprobst@consolidated.net
kellogg_chuck@yahoo.com
kentprobst79@gmail.com
kevinperkins@frontiernet.net
kgreen1946@hotmail.com
kgreen@consolidated.net
kmschmitz1987@gmail.com
kpattena@dieterich.k12.il.us
Karen Flach <kvflach@consolidated.net>
l.arney@mchsi.com
lambertc21@yahoo.com
lbcarie@consolidated.net
ldarney84@gmail.com
linda@mmtcnet.com
lindak959@gmail.com
lverdeyen12@gmail.com
lysaha@frontiernet.net
madonnatsmith@gmail.com
manueldean9@gmail.com
manueldean@hotmail.com
Bill McClain <mcclain4849@gmail.com>
mdrone@gmail.com
mickeyp@mchsi.com
mjwebb@mediacom.net
mjwebbc@consolidated.net
mommac61@hotmail.com
mpwgcw@consolidated.net
mrs_b_abc@yahoo.com
msnizzy@gmail.com
musicmaker@consolidated.net
norma-bob@hotmail.com
norton1961@hotmail.com
owen_62401@hotmail.com
owenda51@gmail.com
pdteach46@yahoo.com
r.bothwell@mchsi.com
raabell40@gmail.com
raabell@mchsi.com
rbk@consolidated.net
rbushue@mmtcnet.com
rclading1963@yahoo.com
rhint@mmtcnet.com
rjhenderson@mchsi.com
rlshanks62@gmail.com
robbmar@frontiernet.net
rodgersd@live.com
roedlm76@gmail.com
roedlm@frontiernet.net
rrmilleville@gmail.com
rwaymoth@yahoo.com
sbpeno@gmail.com
schrader@frontiernet.net
schroeder@frontiernet.net
sharonileen@yahoo.com
slackdog1197@gmail.com
smithenryj@yahoo.com
smithjs3@gmail.com
snags@mmtcnet.com
stevefritcher1@gmail.com
susangreen@consolidated.net
swisher_93@hotmail.com
tasheehan@frontiernet.net
tegeler1@consolidated.net
tjbrandt@consolidated.net
tollivm@frontiernet.net
twied6@consolidated.net
walk_alan@frontiernet.net
walk_ellen@frontiernet.net
walldonna555@gmail.com
wallsdonna555@gmail.com
west@mmtcnet.com
willenborg@consolidated.net
winterspj@frontier.net
wootongs@gmail.com
wormhoudt@mchsi.com
fs-directors
Amy Christian <achristian@panaschools.com>
Alyssa Kruenegel <akruenegel@bcusd201.com>
Denise Anderson <anderson@effingham.k12.il.us>
Denise Anderson <anderson@unit40.org>
Alyssa Tompkins <atompkins@bcusd201.com>
Christian Pasley <cpasley@stelmo.org>
Colleen Reams <creams@vandals203.org>
Christine Thomas <cthomas@ecusd4.com>
Elisha Love <elove@panhandleschools.com>
felechia Williams <fwilliams@ramseycusd.org>
Gayloa Robertson <grobertson@beechercity.org>
Julie Elam <juelam@mgschools.com>
Julie Wollerman <juliewollerman@roe3.org>
Kristen Gregory <kgregory@hillsboroschools.net>
Kari McElroy <kmcelroy@beechercity.org>
Norma Koester <koestern@ttown.k12.il.us>
MD <mdrone@gmail.com>
Mary Jahraus <mjahraus@southcentralschools.org>
Peggy Anderson <panderson@hillsboroschools.net>
Teresa Ragsdale <tragsdale@stelmo.org>
librarians
aalbanese@piasabirds.net
Annette Hartlieb <ahartlieb@roe3.org>
amiller@hillsboroschools.net
askinner@panaschool.com
bhammer@beechercity.org
dscherzer@panaschools.com
flackj@unit40.org
jtracey@ecusd4.com
Julie Wollerman <juliewollerman@roe3.org>
kharris@bccu2.org
lharlow@panaschools.com
MD <mdrone@gmail.com>
mgoebel@ga.mohawks.net
mjefferson@bccu2.org
mlzeeb@mgschools.com
mrichars@dieterichschools.org
nicea@ttown.k12.il.us
sclaycomb@bcusd201.com
seller@ramseycusd.org
tcothern@panaschools.com
maint-directors
Andy Carter <acarter@ramseycusd.org>
Annette Hartlieb <ahartlieb@roe3.org>
Alan Whitt <awhitt@altamontschools.org>
Brad Koonce <bkoonce@bcusd201.com>
Bob Witter <bwitter@litchfieldpanthers.org>
Charles Fritscher <cfritscher@dieterichschools.org>
Dawn Doty <ddoty@beechercity.org>
David Northway <dnorthway@beechercity.org>
Denny Vincent <dvincent@panhandleschools.com>
Fred Butler <fbutler@hillsboroschools.net>
Jason Huber <huberj@ttown.k12.il.us>
Josh Bogart <jbogart@vandals203.org>
Jim Kelmel <jkelmel@ga.mohawks.net>
Jeff Stauder <jstauder@panaschools.com>
Julie Wollerman <juliewollerman@roe3.org>
Johnathan Verbiski <jverbiski@southforkschools.com>
Jason Wagahoff <jwagahoff@panhandleschools.com>
John Limes <limesj@unit40.org>
MD <mdrone@gmail.com>
Monte Epley <monteepley@nokomis.k12.il.us>
Mike Wilhite <mwilhite@bccu2.org>
Randy Dugan <rdugan@mgschools.com>
Roger Mitchell <rmitchell@stelmo.org>
Warren Schmidt <schmidtr@unit40.org>
Bryan Seidel <seidelb@unit40.org>
Jarred Simmons <simmonsja@unit40.org>
Steve Walters <swalters@tcusd3.org>
Steve Waltrip <swaltrip@bcusd201.com>
Todd Thoele <thoelet@unit40.org>
Todd Steele <tsteele@panhandleschools.com>
principals
Angie Sheehan <a.sheehan@sheff.org>
Andrew Beckham <abeckham@roe3.org>
Anita Brown <abrown@tcusd3.org>
Adam Favre <afavre@litchfieldpanthers.org>
Ashley Francis <afrancis@ecusd4.com>
Annette Hartlieb <ahartlieb@roe3.org>
Adam Haston <ahaston@panaschools.com>
Aaron Hopper <ahopper@panhandleschools.com>
Amy Jackson <ajackson@bccu2.org>
Amber Kidd <akidd@roe3.org>
Angela Armour <angie.armour@midstatespec.org>
Angela Reeter <areeter@roe3.org>
Kelsey Baker <bakerk@unit40.org>
Bill Carpenter <bcarpenter@bccu2.org>
Brian Deadmond <bdeadmond@beechercity.org>
Greg Beck <beckg@ttown.k12.il.us>
Becky Eddy <beddy@ramseycusd.org>
Brian Garrard <bgarrard@stelmo.org>
Bryan Holliday <bholliday@vandals203.org>
Brian Kern <bkern@vandals203.org>
Blake Lipe <blipe@hillsboroschools.net>
Bobbi Hartman <bobbi.hartman@midstatespec.org>
Brand Buske <brandy.buske@midstatespec.org>
Casey Adam <cadam@panaschools.com>
Casie Bowman <cbowman@mgschools.com>
Cody Rincker <crincker@stanthony.com>
Cheri Wysong <cwysong@panaschools.com>
Dana Bivens <dbivens@vandals203.org>
Doug Hill <dhill@altamontschools.org>
Dave Meister <dmeister@ga.mohawks.net>
Pat Drees <dreesp@ttown.k12.il.us>
Donald VanGiesen <dvangiesen@hillsboroschools.net>
David Weller <dweller@bccu2.org>
Eric Bruder <ebruder@tcusd3.org>
Eric Swingler <eswingler@bccu2.org>
Jennifer Fox <foxje@unit40.org>
Gary Brauns <gbrauns@bccu2.org>
Ginger Edwards <gedwards@ramseycusd.org>
Greta Krueger <gkrueger@vandals203.org>
Sherry Harmon <harmons@ttown.k12.il.us>
Heath Strom <hdstrom@panaschools.com>
Hope McBrain <hmcbrain@hillsboroschools.net>
Jana Masten <janamasten@nokomis.k12.il.us>
Josh Benefiel <jbenefiel@dieterichschools.org>
Juletta Ellis <jellis@litchfieldpanthers.org>
Julie Healy <jhealy@stelmo.org>
Justin Johnson <jjohnson@tcusd3.org>
Jessica Miller <jmiller@tcusd3.org>
Jason Rakers <jrakers@bccu2.org>
Jerry Tkachuk <jtkachuk@altamontschools.org>
Julie Wollerman <juliewollerman@roe3.org>
Joe Webb <jwebb@panhandleschools.com>
Jennifer Wise <jwise@tcusd3.org>
Jeff Wooters <jwooters@bcusd201.com>
Kris Biggs <kbiggs@altamontschools.org>
Kevin McDonald <kevinmcdonald@nokomis.k12.il.us>
Kevin Reedy <kevinreedy@nokomis.k12.il.us>
Karen Hanfland <khanfland@beechercity.org>
Kara Harris <kharris@bccu2.org>
Karen Kuntzman <kkuntzman@tcusd3.org>
Kevin McDonald <kmcdonald@panaschools.com>
Kelly Millburg <kmillburg@panaschools.com>
Ken Schuster <kschuster@panhandleschools.com>
Kelly Suey <ksuey@nptsped.com>
Laura Benhoff <lbenhoff@roe3.org>
Lisa Mayhall <lmayhall@panaschools.com>
Lakin Puzey <lpuzey@tcusd3.org>
Lyn Becker <lyn.becker@midstatespec.org>
Cheri Marten <martenc@unit40.org>
MD <mdrone@gmail.com>
Marci Gutierrez <mgutierrez@hillsboroschools.net>
Megan Hanlon <mhanlon@ga.mohawks.net>
Matt Hutchison <mhutchison@tcusd3.org>
Michelle Reeves <mreeves@hillsboroschools.net>
Michelle Reiss <mreiss@tcusd3.org>
Michelle Rogers <mrogers@southforkschools.com>
Martin Son <mson@bcusd201.com>
Amy Niebrugge <niebrugg@unit40.org>
Peggy Bueker <pbueker@altamontschools.org>
Patricia Heyen <pheyen@hillsboroschools.net>
Matt Houser <principal@fbcafalcons.org>
Tony Pullen <pullent@unit40.org>
Rachelle McDowell <rachellemcdowell@nokomis.k12.il.us>
Kurt Roberts <robertsk@unit40.org>
Robin Flach <robiflach@alisrockets.com>
Randy Protz <rprotz@vandals203.org>
Russ Tepen <rtepen@litchfieldpanthers.org>
Todd Schuette <schuette@effingham.k12.il.us>
Todd Schuette <schuette@unit40.org>
Charlie Schwerman <schwerma@unit40.org>
Stephen Groll <sgroll@southforkschools.com>
Suzanne Grundy <sgrundy@slsk8.org>
Sean Hannagan <shannagan@stelmo.org>
Scott Kocher <skocher@dieterichschools.org>
Stacy Mesnard <smesnard@vandals203.org>
Travis Portz <tportz@ramseycusd.org>
Tiffany Zobrist <tzobrist@mgschools.com>
Larry Urban <urban@vandaliachristianacademy.com>
Zach Frailey <zfrailey@hillsboroschools.net>
roe3staff
Andrew Beckham <abeckham@roe3.org>
Annette <ahartlieb@roe3.org>
Amber Kidd <akidd@roe3.org>
Annette McClintock <amcclintock@roe3.org>
Angela Reeter <areeter@roe3.org>
Andrea Rhodes <arhodes@roe3.org>
Beth Darling <bdarling@roe3.org>
Cathy Jones <cjones@roe3.org>
Callie Smith <csmith@roe3.org>
Caroline Vanderkelen <cvanderkelen@roe3.org>
Dawn DeClerck <ddeclerck@roe3.org>
Dean Keller <dkeller@roe3.org>
Dawn Rosborough <drosborough@roe3.org>
Emily Nelson <enelson@roe3.org>
Jordan Emery <jemery@roe3.org>
Jenny Hoeske <jhoeske@roe3.org>
Julie Morell <jmorell@roe3.org>
Julie <juliewollerman@roe3.org>
Joe Vanzo <jvanzo@roe3.org>
Jen Vitale <jvitale@roe3.org>
Jill Wright <jwright@roe3.org>
Katalyn Bourgeois <kbourgeois@roe3.org>
Kaitlyn Cook <kcook@roe3.org>
Kaci Reiss <kreiss@roe3.org>
Katie Tate <ktate@roe3.org>
Kate Wagahoff <kwagahoff@roe3.org>
Laura Benhoff <lbenhoff@roe3.org>
Lesley Keel <lkeel@roe3.org>
Liz Scioneaux <lscioneaux@roe3.org>
Mary Adams <madams@roe3.org>
Melissa Davidson <mdavidson@roe3.org>
MD <mdrone@gmail.com>
Megan Goodman <mgoodman@roe3.org>
Madison Jones <mjones@roe3.org>
Meredith Yard <myard@roe3.org>
Natalie Hall <nhall@roe3.org>
Paula White <pwhite@roe3.org>
Paula Wright <pwright@roe3.org>
Rachel Koester <rkoester@roe3.org>
Savannah Holthaus <sholthaus@roe3.org>
Sarah Huckstead <shuckstead@roe3.org>
Shay Jones <sjones@roe3.org>
Steve Long <slong@roe3.org>
Sadie Ruholl <sruholl@roe3.org>
Sondra Templeton <stempleton@roe3.org>
Tyler Charlesworth <tcharlesworth@roe3.org>
Theresa Coker <tcoker@roe3.org>
Teresa Eilers <teilers@roe3.org>
Valerie Sanguinetti <vsanguinetti@roe3.org>
Whitney Voyles <wvoyles@roe3.org>
school-nurses
Ali Luckett <aluckett@hillsboroschools.net>
Ashley Miller <amiller@bccu2.org>
Bobbi Lowe <blowe@hillsboroschools.net>
Brittany White <bwhite@vandals203.org>
Carissa Bohannon <cbohannon@bccu2.org>
Chrissy Matthews <cmatthews@mgschools.com>
Heather Owens <howens@tcusd3.org>
Heather Rodden <hrodden@southforkschools.com>
Joy Lewis <jlewis@vandals203.org>
Jenny Moats <jmoats@tcusd3.org>
Julie Wollerman <juliewollerman@roe3.org>
Kendra Kirby <kkirby@litchfieldpanthers.org>
Lisa Kiefer <lisakiefer@nokomis.k12.il.us>
MD <mdrone@gmail.com>
Nikki Lipe <nlipe@hillsboroschools.net>
Natalie Morrison <nmorrison@stelmo.org>
Donna Pierson <piersond@unit40.org>
Susie McClure <smcclure@tcusd3.org>
Sandy Pauley <spauley@panaschools.com>
Shannon Zerrusen <szerrusen@bcusd201.com>
Teresa Hays <thays@litchfieldpanthers.org>
Tracy Hulsey <thulsey@southcentralschools.org>
Julie Zeigler <zeiglerj@ttown.k12.il.us>
secretaries
Annette Hartlieb <ahartlieb@roe3.org>
Angela Holcomb <aholcomb@hillsboroschools.net>
Ashley Towler <atowler@stelmo.org>
Amy Zimmerman <azimmerman@vandals203.org>
Linda Baker <bakerli@unit40.org>
Becky Casey <bcasey@ramseycusd.org>
Brenda Higgins <bhiggins@ecusd4.com>
Betsey Homa <bhoma@hillsboroschools.net>
Deb Blankenship <blankens@unit40.org>
Bev Lipe <blipe@panhandleschools.com>
Beth O?Brien <bobrien@tcusd3.org>
Brandy Chausse <brandychausse@nokomis.k12.il.us>
Brittany Rigdon <brigdon@bcusd201.com>
Ellen Broom <broome@unit40.org>
Barb Winkler <bwinkler@hillsboroschools.net>
Cheryl Bishop <cbishop@litchfieldpanthers.org>
Cassandra Cook <ccook@ramseycusd.org>
Cheryl Covington <ccovington@tcusd3.org>
Cheyenne Elam <celam@bccu2.org>
Sharon Chesnut <chesnuts@unit40.org>
Chris Huber <chuber@litchfieldpanthers.org>
Christine Ransdell <cransdell@tcusd3.org>
Dawn Rosborough <dawn@roe3.org>
Donna Dothager <ddothager@vandals203.org>
Dawn Germann <dgermann@panhandleschools.com>
Donna Kroening <dkroenin@altamontschools.org>
Donna Lemon <dlemon@panhandleschools.com>
Dawn Rosborough <drosborough@roe3.org>
Emily Laesch <elaesch@bccu2.org>
Heather Hartman <hartmanh@unit40.org>
Heather Greenwood <hgreenwood@hillsboroschools.net>
Cathy Hille <hillec@unit40.org>
Jenny Hoeske <jhoeske@roe3.org>
Julie Moreland <jmoreland@ramseycusd.org>
Joann Baumgartner <joann@ramseycusd.org>
Jacy Schaub <jschaub@bcusd201.com>
Julie Wollerman <juliewollerman@roe3.org>
Jill Wright <jwright@roe3.org>
Kris Adamson <kadamson@litchfieldpanthers.org>
Kathy Foster <kathyfoster@nokomis.k12.il.us>
Karen Black <kblack@vandals203.org>
Kim Casey <kcasey@zionlutheranlitchfield.com>
Kim Cook <kim.cook@visionwayschool.org>
Kris Jones <kjones@litchfieldpanthers.org>
Kelly Kenny <kkenny@hillsboroschools.net>
Kim Miller <kmiller@beechercity.org>
Kerry Sims <ksims@ecusd4.com>
Laura Butler <lbutler@hillsboroschools.net>
Lori Cortelloni <lcortelloni@vandals203.org>
Laura Pesko <lpesko@hillsboroschools.net>
Leslie Wendling <lwendli2@altamontschools.org>
Sharon Macklin <macklins@unit40.org>
Monica Boyer <mboyer@stauntonschools.org>
MD <mdrone@gmail.com>
Molly Kirk <mkirk@vandals203.org>
Michelle Morrissey <morrisse@unit40.org>
Meredith Yard <myard@panhandleschools.com>
Nikki Tedrick <ntedrick@altamontschools.org>
okaw1@vandals203.org
Penny Critcheloe <pcritcheloe@vandals203.org>
Pam Thacker <pthacker@hillsboroschools.net>
Pam Workman <pworkman.bcgs@gmail.com>
Paula Wright <pwright@roe3.org>
Robyn Foster <robyn.foster@panaschools.com>
Robin Osborn <rosborn@hillsboroschools.net>
Sue Harnish <s.harnish@sheff.org>
Stephanie Althoff <salthoff@tcusd3.org>
Sandy Branham <sbranham@vandals203.org>
Stephanie Crosley <scrosley@stauntonschools.org>
Stacy Glasscock <sglasscock@ecusd4.com>
Shawn Hogue <shogue@lcusd12.org>
Shawn Hogue <shogue@litchfieldpanthers.org>
Sarah Huckstead <shuckstead@roe3.org>
Susan Janz <sjanz@altamontschools.org>
Shay Jones <sjones@roe3.org>
Staci Carroll <slcarroll@okaw.us>
Staci Carroll <slcarroll@vandals203.org>
Spring Huston <springhuston@nokomis.k12.il.us>
Shannon Sloan <ssloan@beechercity.org>
Shelly Thomason <sthomason@bcusd201.com>
Tina Ambrose <tambrose@panaschools.com>
Tammy Waggoner <tammywaggoner@nokomis.k12.il.us>
Terri Davison <tdavison@vandals203.org>
Tammy Hanner <thanner@hillsboroschools.net>
Tabytha?Jack <tjack@southforkschools.com>
Tammy Joliff <tjolliff@mgschools.com>
Tammy Nordyke <tnordyke@vandals203.org>
Erica Warner <warnere@unit40.org>
Jodi Waymoth <waymothj@unit40.org>
Cathy White <whitec@unit40.org>
Penny Wiedman <wiedmanp@unit40.org>
tech
Annette Hartlieb <ahartlieb@roe3.org>
Amber Kidd <akidd@roe3.org>
Cassandra Carpenter <carpenterc@ttown.k12.il.us>
Chris Kuntzman <ckuntzman@litchfieldpanthers.org>
CJ Meyer <cmeyer@bccu2.org>
CJ Schmidt <cschmidt@vandals203.org>
Kirk Hammer <hammerk@effingham.k12.il.us>
Holly Kelly <hkelly@ltcillinois.org>
Jesse Foiles <jesse@southforkschools.com>
Julie Lay <jlay@vandals203.org>
Jessica Miller <jmiller@tcusd3.org>
Julie Wollerman <juliewollerman@roe3.org>
Kent Kistler <klkistler@vandals203.org>
Laura Rench <lrench@hillsboroschools.net>
Kevin McKenna <mckennak@effingham.k12.il.us>
Mark Corbus <mcorbus@bccu2.org>
MD <mdrone@gmail.com>
Meg File <mfile@bccu2.org>
Michael Reiss <mreiss@ramseycusd.org>
Matt Weld <mweld@roe3.org>
Bob Straub <rstraub@panhandleschools.com>
Douglas Runde <runded@ttown.k12.il.us>
Rob Schottman <schottma@effingham.k12.il.us>
Steve Long <slong@roe3.org>
Shawn Perkins <sperkins@hillsboroschools.net>
Scott Savage <ssavage@panaschools.com>
Tyler Charlesworth <tcharlesworth@roe3.org>
transportation
Adam Gregg <agregg@hillsboroschools.net>
Alan Monical <amonical@southcentralschools.org>
Brenda Higgins <bhiggins@ecusd4.com>
Bryan Kimbro <bkimbro@ramseycusd.org>
Bob Witter <bwitter@litchfieldpanthers.org>
Chris Clark <cclark@southforkschools.com>
Deb Hunter <dhunter@bcusd201.com>
Donnie Tull <dtull@beechercity.org>
Kristen Harvey <harveyk@effingham.k12.il.us>
Kristin Harvey <harveyk@unit40.org>
Jim Kelmel <jkelmel@ga.mohawks.net>
Jeff Stauder <jstauder@panaschools.com>
Julie Wollerman <juliewollerman@roe3.org>
Jason Wagahoff <jwagahoff@panhandleschools.com>
Brian Koester <koesterbrian@ttown.k12.il.us>
MD <mdrone@gmail.com>
Mark Holland <mholland@altamontschools.org>
Monte Epley <monteepley@nokomis.k12.il.us>
Phil Lark <plark@beechercity.org>
Randy Dugan <rdugan@mgschools.com>
Roger Mitchell <rmitchell@stelmo.org>
Sarah Huckstead <shuckstead@roe3.org>
Sean Traylor <straylor@bccu2.org>
Whitney Smith <wsmith@vandals203.org>
wil
Annette Hartlieb <ahartlieb@roe3.org>
Amber Kidd <akidd@roe3.org>
Amanda D Marshall <amarshall@ccs135.com>
Annie Gray <annie.gray@sandoval501.org>
Angela Reeter <areeter@roe3.org>
Brittany Boldt <bboldt@roe13.org>
Melanie Becker <becker@salem111.com>
Belinda Hill <bhill@gcs130.org>
Kelly Conklin <conklink@salemhigh.com>
Diane Robertson <drobertson@iasaedu.org>
Dee Ann Schnautz <dschnautz@mtv80.org>
Dana Diane Waggoner <dwaggoner@farrington99.org>
Jennifer Filyaw <filyawj@wesclin.org>
"Dr. Leslie Foppe" <foppe@salem111.com>
Greta Krueger <gkrueger@vandals203.org>
Jennifer Garrison <jgarrison@vandals203.org>
Jill Griffin <jgriffin@bethalto.org>
Jera Pieper <jpieper@fjsped.org>
Jill Rogers <jrogers@martinsville.k12.il.us>
Julie Wollerman <juliewollerman@roe3.org>
Kristin Ing <king@ewinggradeschool.org>
Laura Benhoff <lbenhoff@roe3.org>
Lisa Schuenke <lisa.schuenke@jersey100.org>
"Dr. Lori James-Gross" <ljgross@up140.org>
MD <mdrone@gmail.com>
Melissa M Ritter <mritter@ramseycusd.org>
Nicole Henson <nhenson@blufordschools.org>
"Natalie M. Page" <npage@sv196.org>
Nancy Werden <nwerden@stauntonschools.org>
Paige Maginel <pmaginel@dongolaschool.com>
Sandra Kabat <skabat@woodlawnschools.org>
Sarah Mellott <smellott@rome2.net>
Stacy A Mesnard <smesnard@vandals203.org>
Sherry Harmon <srharmon@bcusd201.com>
Tommi Ryan <tryan@sgd178.org>
wget 'https://lists2.roe3.org/mdrone/doc/mailman-admin.pdf'wget 'https://lists2.roe3.org/mdrone/doc/mailman-admin.txt' #GNU mailman - list Administration Manual Contents About this
document... About this document...
Previous Page Up one Level Next Page GNU Mailman - List Administration
Manual
__________________________________________________________________
GNU Mailman - List Administration Manual
Barry A. Warsaw
Release 2.1
January 11, 2020
Front Matter
Abstract:
This document describes the list administrator's interface for GNU
Mailman 2.1. It contains information a list owner would need to
configure their list, either through the web interface or through
email. It also covers the moderator's interface for approving held
messages and subscription notices, and the web interface for creating
new mailing lists. In general, it does not cover the command line
interface to Mailman, installing Mailman, or interacting with Mailman
from the point of view of the user. That information is covered in
other manuals.
Contents
*
+ 1 Introduction to GNU Mailman
o 1.1 A List's Email Addresses
o 1.2 Administrative Roles
o 1.3 A List's Web Pages
o 1.4 Basic Architectural Overview
+ 2 The List Configuration Pages
o 2.1 The General Options Category
o 2.2 The Passwords Category
o 2.3 The Language Options Category
o 2.4 The Membership Management Category
o 2.5 The Non-digest Options Category
o 2.6 The Digest Options Category
o 2.7 The Privacy Options Category
o 2.8 The Bounce Processing Category
o 2.9 The Archiving Options Category
o 2.10 The Mail/News Gateway Category
o 2.11 The Auto-responder Category
o 2.12 The Content Filtering Category
o 2.13 The Topics Category
+ 3 Membership Management
+ 4 Tending to Pending Moderator Requests
+ 5 Editing the Public HTML Pages
+ 6 Deleting the Mailing List
+ 1 This is an Appendix
1 Introduction to GNU Mailman
GNU Mailman is software that lets you manage electronic mailing lists.
It supports a wide range of mailing list types, such as general
discussion lists and announce-only lists. Mailman has extensive
features for controlling the privacy of your lists, distributing your
list as personalized postings or digests, gatewaying postings to and
from Usenet, and providing automatic bounce detection. Mailman provides
a built-in archiver, multiple natural languages, as well as advanced
content and topic filtering.
Mailman provides several interfaces to its functionality. Most list
administrators will primarily use the web interface to customize their
lists. There is also a limited email command interface to the
administrative functions, as well as a command line interface if you
have shell access on the Mailman server. This document does not cover
the command line interface; see the GNU Mailman site administrator's
manual for more details.
1.1 A List's Email Addresses
Every mailing list has a set of email addresses that messages can be
sent to. There's always one address for posting messages to the list,
one address that bounces will be sent to, and addresses for processing
email commands. For example, for a mailing list called
mylist@example.com, you'd find these addresses:
* mylist@example.com - this is the email address people should use
for new postings to the list.
* mylist-join@example.com - by sending a message to this address, a
new member can request subscription to the list. Both the Subject:
header and body of such a message are ignored. Note that
mylist-subscribe@example.com is an alias for the -join address.
* mylist-leave@example.com - by sending a message to this address, a
member can request unsubscription from the list. As with the -join
address, the Subject: header and body of the message is ignored.
Note that mylist-unsubscribe@example.com is an alias for the -leave
address.
* mylist-owner@example.com - This address reaches the list owner and
list moderators directly.
* mylist-request@example.com - This address reaches a mail robot
which processes email commands that can be used to set member
subscription options, as well as process other commands.
* mylist-bounces@example.com - This address receives bounces from
members whose addresses have become either temporarily or
permanently inactive. The -bounces address is also a mail robot
that processes bounces and automatically disables or removes
members as configured in the bounce processing settings. Any bounce
messages that are either unrecognized, or do not seem to contain
member addresses, are forwarded to the list administrators.
* mylist-confirm@example.com - This address is another email robot,
which processes confirmation messages for subscription and
unsubscription requests.
There's also an -admin address which also reaches the list
administrators, but this address only exists for compatibility with
older versions of Mailman.
1.2 Administrative Roles
There are two primary administrative roles for each mailing list, a
list owner and a list moderator. A list owner is allowed to change
various settings of the list, such as the privacy and archiving
policies, the content filtering settings, etc. The list owner is also
allowed to subscribe or invite members, unsubscribe members, and change
any member's subscription options.
The list moderator on the other hand, is only allowed to approve or
reject postings and subscription requests. The list moderator can also
do things like clear a member's moderation flag, or add an address to a
list of approved non-member posters.
Normally, the list owner and list moderator are the same person. In
fact, the list owner can always do all the tasks a list moderator can
do. Access to both the owner's configuration pages, and the moderation
pages are protected by the same password. However, if the list owner
wants to delegate posting and subscription approval authority to other
people, a separate list moderator password can be set, giving
moderators access to the approval pages, but not the configuration
pages. In this setup, list owners can still moderate the list, of
course.
In the sections that follow, we'll often use the terms list owner and
list administrator interchangably, meaning both roles. When necessary,
we'll distinguish the list moderator explicitly.
1.3 A List's Web Pages
Every mailing list is also accessible by a number of web pages. Note
that the exact urls are configurable by the site administrator, so they
may be different than what's described below. We'll describe the most
common default configuration, but check with your site administrator or
hosting service for details.
Mailman provides a set of web pages that list members use to get
information about the list, or manage their membership options. There
are also list archive pages, for browsing an online web-based archive
of the list traffic. These are described in more detail in the GNU
Mailman user's manual.
Mailman also provides a set of pages for configuring an individual
list, as well as a set of pages for disposing of posting and
subscription requests.
For a mailing list called mylist hosted at the domain
lists.example.com, you would typically access the administrative pages
by going to http://lists.example.com/mailman/admin/mylist. The first
time you visit this page, you will be presented with a login page,
asking for the list owner's password. When you enter the password,
Mailman will store a session cookie in your browser, so you don't have
to re-authenticate for every action you want to take. This cookie is
stored only until you exit your browser.
To access the administrative requests page, you'd visit
http://lists.example.com/mailman/admindb/mylist (note the admindb url
as opposed to the admin url). Again, the first time you visit this
page, you'll be presented with a login page, on which you can enter
either the list moderator password or the list owner password. Again, a
session cookie is dropped in your browser. Note also that if you've
previously logged in as the list owner, you do not need to re-login to
access the administrative requests page.
1.4 Basic Architectural Overview
This section will outline the basic architecture of GNU Mailman, such
as how messages are processed by the sytem. Without going into lots of
detail, this information will help you understand how the configuration
options control Mailman's functionality.
When mail enters the system from your mail server, it is dropped into
one of several Mailman queues depending on the address the message was
sent to. For example, if your system has a mailing list named mylist
and your domain is example.com, people can post messages to your list
by sending them to mylist@example.com. These messages will be dropped
into the incoming queue, which is also colloquially called the
moderate-and-munge queue. The incoming queue is where most of the
approval process occurs, and it's also where the message is prepared
for sending out to the list membership.
There are separate queues for the built-in archiver, the bounce
processor, the email command processor, as well as the outgoing email
and news queues. There's also a queue for messages generated by the
Mailman system. Each of these queues typically has one queue runner (or
``qrunner'') that processes messages in the queue. The qrunners are
idle when there are no messages to process.
Every message in the queues is represented by two files, a message file
and a metadata file. Both of these files share the same base name,
which is a combination of a unique hash and the Unix time that the
message was received. The metadata file has a suffix of .db and the
message file has a suffix of either .msg if stored in plain text, or
.pck if stored in a more efficient internal representation^1.
As a message moves through the incoming queue, it performs various
checks on the message, such as whether it matches one of the moderation
criteria, or contains disallowed MIME types. Once a message is approved
for sending to the list membership, the message is prepared for sending
by deleting, adding, or changing message headers, adding footers, etc.
Messages in the incoming queue may also be stored for appending to
digests.
2 The List Configuration Pages
After logging into the list configuration pages, you'll see the
configuration options for the list, grouped in categories. All the
administrative pages have some common elements. In the upper section,
you'll see two columns labeled ``Configuration Categories''. Some
categories have sub-categories which are only visible when you click on
the category link. The first page you see after logging in will be the
``General Options'' category. The specific option settings for each
category are described below.
On the right side of the top section, you'll see a column labeled
``Other Administrative Activities''. Here you'll find some other things
you can do to your list, as well as convenient links to the list
information page and the list archives. Note the big ``Logout'' link;
use this if you're finished configuring your list and don't want to
leave the session cookie active in your browser.
Below this common header, you'll find a list of this category's
configuration variables, arranged in two columns. In the left column is
a brief description of the option, which also contains a ``details''
link. For many of the variables, more details are available describing
the semantics of the various available settings, or information on the
interaction between this setting and other list options. Clicking on
the details link brings up a page which contains only the information
for that option, as well as a button for submitting your setting, and a
link back to the category page.
On the right side of the two-column section, you'll see the variable's
current value. Some variables may present a limited set of values, via
radio button or check box arrays. Other variables may present text
entry boxes of one or multiple lines. Most variables control settings
for the operation of the list, but others perform immediate actions
(these are clearly labeled).
At the bottom of the page, you'll find a ``Submit'' button and a footer
with some more useful links and a few logos. Hitting the submit button
commits your list settings, after they've been validated. Any invalid
values will be ignored and an error message will be displayed at the
top of the resulting page. The results page will always be the category
page that you submitted.
2.1 The General Options Category
The General Options category is where you can set a variety of
variables that affect basic behavior and public information. In the
descriptions that follow, the variable name is given first, along with
an overview and a description of what that variable controls.
2.1.1 General list personality
These variables, grouped under the general list personality section,
control some public information about the mailing list.
real_name
Every mailing list has both a posting name and a real name. The
posting name shows up in urls and in email addresses, e.g. the
mylist in mylist@example.com. The posting name is always
presented in lower case, with alphanumeric characters and no
spaces. The list's real name is used in some public information
and email responses, such as in the general list overview. The
real name can differ from the posting name by case only. For
example, if the posting name is mylist, the real name can be
MyList.
owner
This variable contains a list of email addresses, one address
per line, of the list owners. These addresses are used whenever
the list owners need to be contacted, either by the system or by
end users. Often, these addresses are used in combination with
the moderator addresses (see below).
moderator
This variable contains a list of email addresses, one address
per line, of the list moderators. These addresses are often used
in combination with the owner addresses. For example, when you
email mylist-owner@example.com, both the owner and moderator
addresses will receive a copy of the message.
description
In the general list overview page, which shows you every
available mailing list, each list is displayed with a short
description. The contents of this variable is that description.
Note that in emails from the mailing list, this description is
also used in the comment section of the To: address. This text
should be relatively short and no longer than one line.
info
This variable contains a longer description of the mailing list.
It is included at the top of the list's information page, and it
can contain HTML. However, blank lines will be automatically
converted into paragraph breaks. Preview your HTML though,
because unclosed or invalid HTML can prevent display of parts of
the list information page.
subject_prefix
This is a string that will be prepended to the Subject: header
of any message posted to the list. For example, if a message is
posted to the list with a Subject: like:
Subject: This is a message
and the subject_prefix is [My List] (note the trailing space!),
then the message will be received like so:
Subject: [My List] This is a message
If you leave subject_prefix empty, no prefix will be added to
the Subject:. Mailman is careful not to add a prefix when the
header already has one, as is the case in replies for example.
The prefix can also contain characters in the list's preferred
language. In this case, because of the vagaries of the email
standards, you may or may not want to add a trailing space.
from_is_list
This applies to all non-digest messages sent by the list. For
settings that apply only to messages whose From: domain
publishes a DMARC p=reject or p=quarantine policy, see the
dmarc_moderation_action description in section 2.7.
If set to Munge From, it replaces the From: header address with
the list's posting address to mitigate issues stemming from the
original From: domain's DMARC or similar policies and puts the
original From: address in a Reply-To: header.
If set to Wrap Message it wraps the original message as a MIME
subpart of an outer message with From: and Reply-To: headers as
above.
anonymous_list
This variable allows you to turn on some simple anonymizing
features of Mailman. When you set this option to Yes, Mailman
will remove or replace the From:, Sender:, and Reply-To: fields
of any message posted to the list.
Note that this option is simply an aid for anonymization, it
doesn't guarantee it. For example, a poster's identity could be
evident in their signature, or in other mail headers, or even in
the style of the content of the message. There's little Mailman
can do about this kind of identity leakage.
2.1.2 Reply-To header munging
This section controls what happens to the Reply-To: headers of messages
posted through your list.
Beware! Reply-To: munging is considered a religious issue and the
policies you set here can ignite some of the most heated off-topic
flame wars on your mailing lists. We'll try to stay as agnostic as
possible, but our biases may still peak through.
Reply-To: is a header that is commonly used to redirect replies to
messages. Exactly what happens when your users reply to such a message
depends on the mail readers your users use, and what functions they
provide. Usually, there is both a ``reply to sender'' button and a
``reply to all'' button. If people use these buttons correctly, you
will probably never need to munge Reply-To:, so the default values
should be fine.
Since an informed decision is always best, here are links to two
articles that discuss the opposing viewpoints in great detail:
* Reply-To Munging Considered Harmful
* Reply-To Munging Considered Useful
The three options in this section work together to provide enough
flexibility to do whatever Reply-To: munging you might (misguidingly :)
feel you need to do.
first_strip_reply_to
This variable controls whether any Reply-To: header already
present in the posted message should get removed before any
other munging occurs. Stripping this header will be done
regardless of whether or not Mailman will add its own Reply-To:
header to the message.
If this option is set to No, then any existing Reply-To: header
will be retained in the posted message. If Mailman adds its own
header, it will contain addresses which are the union of the
original header and the Mailman added addresses. The mail
standards specify that a message may only have one Reply-To:
header, but that that header may contain multiple addresses.
reply_goes_to_list
This variable controls whether Mailman will add its own
Reply-To: header, and if so, what the value of that header will
be (not counting original header stripping - see above).
When you set this variable to Poster, no additional Reply-To:
header will be added by Mailman. This setting is strongly
recommended.
When you set this variable to This list, a Reply-To: header
pointing back to your list's posting address will be added.
When you set this variable to Explicit address, the value of the
variable reply_to_address (see below) will be added. Note that
this is one situation where Reply-To: munging may have a
legitimate purpose. Say you have two lists at your site, an
announce list and a discussion list. The announce list might
allow postings only from a small number of approved users; the
general list membership probably can't post to this list. But
you want to allow comments on announcements to be posted to the
general discussion list by any list member. In this case, you
can set the Reply-To: header for the announce list to point to
the discussion list's posting address.
reply_to_address
This is the address that will be added in the Reply-To: header
if reply_goes_to_list is set to Explicit address.
2.1.3 Umbrella list settings
TBD. Note that umbrella lists are deprecated and will be replaced with
a better mechanism for Mailman 3.0.
2.1.4 Notifications
Mailman sends notifications to the list administrators or list members
under a number of different circumstances. Most of these notifications
can be configured in this section, but see the Bounce Processing and
Auto-responder categories for other notifications that Mailman can
send.
send_reminders
By default Mailman sends all list members a monthly password
reminder. This notice serves two purposes. First, it reminds
people about all the lists they may be subscribed to on this
domain, including the lists where their subscription may be
disabled. Second, it reminds people about their passwords for
these lists, as well as the url for their personal options
pages, so that they can more easily configure their subscription
options.
Some people get annoyed with these monthly reminders, and they
can disable the reminders via their subscription options page.
For some lists, the monthly reminders aren't appropriate for any
of the members, so you can disable them list-wide by setting the
send_reminders variable to No.
welcome_msg
When new members are subscribed to the list, either by their own
action, or the action of a list administrator, a welcome message
can be sent to them. The welcome message contains some common
boilerplate information, such as the name of the list,
instructions for posting to the list, and the member's
subscription password. You can add additional information to the
welcome message by typing the text into the welcome_msg text
box. Note that because this text is sent as part of an email, it
should not contain HTML.
send_welcome_msg
This flag controls whether or not the welcome message is sent to
new subscribers.
goodbye_msg
Like the welcome_msg, a ``goodbye'' message can be sent to
members when they unsubscribe from the list. Unlike the welcome
message, there's no boilerplate for the goodbye message. Enter
the entire goodbye message you'd like unsubscribing members to
receive into the goodbye_msg text box.
send_goodbye_msg
This flag controls whether or not the goodbye message is sent to
unsubscribing members.
admin_immed_notify
List moderators get notifications of pending administrative
actions, such as subscription or unsubscription requests that
require moderator approval, or posted messages that are being
held for moderator approval. List moderators will always get a
daily summary of such pending requests, but they can also get
immediate notifications when such a request is made. The
admin_immed_notify variable controls whether these immediate
notifications are sent or not. It's generally a good idea to
leave this set to Yes.
admin_notify_mchanges
This variable controls whether the list administrators should
get notifications when members join or leave the list.
respond_to_post_requests
This variable controls whether the original sender of a posting
gets a notice when their message is held for moderator approval.
2.1.5 Additional settings
This section contains some miscellaneous settings for your mailing
list.
emergency
When this option is enabled, all list traffic is emergency
moderated, i.e. held for moderation. Turn this option on when
your list is experiencing a flamewar and you want a cooling off
period.
new_member_options
Each member has a set of subscription options which they can use
to control how they receive messages and otherwise interact with
the list. While the members can change these settings by logging
into their personal options page, you might want to set the
default for a number of the member options. You can do that with
this variable, but see also the other categories for other
member defaults you can set.
This variable presents a set of checkboxes which control the
defaults for some of the member options. Conceal the member's
address specifies whether or not the address is displayed in the
list roster. Acknowledge the member's posting controls whether
or not Mailman sends an acknowledgement to a member when they
post a message to the list. Do not send a copy of a member's own
post specifies whether a member posting to the list will get a
copy of their own posting. Filter out duplicate messages to list
members (if possible) specifies whether members who are
explicitly listed as a recipient of a message (e.g. via the Cc:
header) will also get a copy from Mailman.
Of course, members can always override these defaults by making
changes on their membership options page.
administrivia
This option specifies whether Mailman will search posted
messages for admimistrivia, in other words, email commands which
usually should be posted to the -request address for the list.
Setting this to Yes helps prevent such things as unsubscribe
messages getting erroneously posted to the list.
If a message seems to contain administrivia, it is held for
moderator approval.
max_message_size
This option specifies a maximum message size, in kilobytes, over
which the message will be held for moderator approval.
host_name
This option specifies the host name part of email addresses used
by this list. For example, this is the example.com part of the
posting address mylist@example.com.
It's generally not a good idea to change this value, since its
default value is specified when the mailing list is created.
Changing this to an incorrect value could make it difficult to
contact your mailing list. Also note that the url used to visit
the list's pages is not configurable through the web interface.
This is because if you messed it up, you'd have to have the site
administrator fix it.
include_rfc2369_headers
RFC 2369 is an internet standard that describes a bunch of
headers that mailing list managers should add to messages to
make it easier for people to interact with the list. Mail
reading programs which support this standard may provide buttons
for easy access to the list's archives, or for subscribing and
unsubscribing to the list. It's generally a good idea to enable
these headers as it provides for an improved user experience.
These headers are often called the List-* headers.
However, not all mail readers are standards compliant yet, and
if you have a large number of members who are using
non-compliant mail readers, they may be annoyed at these
headers. You should first try to educate your members as to why
these headers exist, and how to hide them in their mail clients.
As a last resort you can disable these headers, but this is not
recommended.
include_list_post_header
The List-Post: header is one of the headers recommended by RFC
2369. However for some announce-only mailing lists, only a very
select group of people are allowed to post to the list; the
general membership is usually not allowed to post to such lists.
For lists of this nature, the List-Post: header is misleading.
Select No to disable the inclusion of this header. (This does
not affect the inclusion of the other List-* headers.)
2.2 The Passwords Category
As mentioned above, there are two primary administrative roles for
mailing lists. In this category you can specify the password for these
roles.
The list owner has total control over the configuration of their
mailing list (within some bounds as specified by the site
administrator). Note that on this page, for historical reasons, the
list owner role is described here as the list administrator. You can
set the list owner's password by entering it in the password field on
the left. You must type it twice for confirmation. Note that if you
forget this password, the only way for you to get back into your list's
administrative pages is to ask the site administrator to reset it for
you (there's no password reminders for list owners).
If you want to delegate list moderation to someone else, you can enter
a different moderator password in the field on the right (typed twice
for confirmation). Note that if you aren't going to delegate
moderation, and the same people are going to both configure the list
and moderate postings to the list, don't enter anything into the
moderator password fields. If you do enter a separate moderator
password, be sure to fill in the moderator variable in the General
options category page.
2.3 The Language Options Category
Mailman is multilingual and internationalized, meaning you can set up
your list so that members can interact with it in any of a number of
natural languages. Of course, Mailman won't translate list postings. :)
However, if your site administrator has enabled its support, you can
set your list up to support any of about two dozen languages, such as
German, Italian, Japanese, or Spanish. Your list members can then
choose any of your supported languages as their preferred language for
interacting with the list. Such things as their member options page
will be displayed in this language. Each mailing list also has its own
preferred language which is the language the list supports if no other
language context is known.
These variables control the language settings for your mailing list:
preferred_language
This is the list's preferred language, which is the language
that the list administrative pages will be displayed in. Also
any messages sent to the list owners by Mailman will be sent in
this language. This option is presented as a drop-down list
containing the languages enabled in the available_languages
variable.
available_languages
This set of checkboxes contains all the natural languages that
your site administrator has made available to your mailing
lists. Select any language that you'd either like your members
to be able to view the list in, or that you'd like to be able to
use in your list's preferred_language variable.
encode_ascii_prefixes
If your mailing list's preferred language uses a non-ASCII
character set and the subject_prefix contains non-ASCII
characters, the prefix will always be encoded according to the
relevant standards. However, if your subject prefix contains
only ASCII characters, you may want to set this option to Never
to disable prefix encoding. This can make the subject headers
slightly more readable for users with mail readers that don't
properly handle non-ASCII encodings.
Note however, that if your mailing list receives both encoded
and unencoded subject headers, you might want to choose As
needed. Using this setting, Mailman will not encode ASCII
prefixes when the rest of the header contains only ASCII
characters, but if the original header contains non-ASCII
characters, it will encode the prefix. This avoids an ambiguity
in the standards which could cause some mail readers to display
extra, or missing spaces between the prefix and the original
header.
2.4 The Membership Management Category
The Membership Management category is unlike the other administrative
categories. It doesn't contain configuration variables or list
settings. Instead, it presents a number of pages that allow you to
manage the membership of your list. This includes pages for subscribing
and unsubscribing members, and for searching for members, and for
changing various member-specific settings.
More details on membership management are described in the Membership
Management section.
2.5 The Non-digest Options Category
Mailman delivers messages to users via two modes. List members can
elect to receive postings in bundles called digests one or a few times
a day, or they can receive messages immediately whenever the message is
posted to the list. This latter delivery mode is also called non-digest
delivery. There are two administrative categories available for
separately controlling digest and non-digest delivery. You can even
disable one or the other forms of delivery (but not both).
Both kinds of delivery can have list-specific headers and footers added
to them which can contain other useful information you want your list
members to see. For example, you can include instructions for
unsubscribing, or a url to the lists digest, or any other information.
Non-digest deliveries can also be personalized which means certain
parts of the message can contain information tailored to the member
receiving the message. For example, the To: header will contain the
address of the member when deliveries are personalized. Footers and
headers can contain personalized information as well, such as a link to
the individual user's options page.
In addition, personalized messages will contain extra information that
Mailman can use to unambiguously track bounces from members.
Ordinarily, Mailman does some pattern recognition on bounce messages to
determine list members whose addresses are no longer valid, but because
of the vagaries of mail systems, and the countless forwards people can
put in place, it's often the case that bounce messages don't contain
any useful information in them. Personalized messages avoid this
problem by encoding information in certain headers that unambiguously
identify the recipient of a message. If that message bounces, Mailman
will know exactly which member it was intended for.
Note that because personalization requires extra system resources, it
must be enabled by the site administrator before you can choose it.
Here are the variables which control non-digest delivery:
nondigestable
This option controls whether members can receive immediate
delivery or not. If not, they will be forced to receive messages
in digests. You can't disable non-digest delivery if digests are
already disabled.
personalize
This option turns on message personalization.
msg_header
This text box lets you enter information that will be included
in the header of every non-digest message sent through the list.
See below for more information on what can go in the headers and
footers. If you leave this text box empty, no header will be
added.
msg_footer
Just like with the header, you can add a footer to every
message. The same rules apply to footers as apply to headers.
Headers and footers can contain any text you want. For non-English
lists, the headers and footers can contain any character in the
character set of the list's preferred language. The headers and footers
can also contain substitution variables which Mailman will fill in with
information taken from the mailing list. These substitutions are in
Python string interpolation format, where something like %(list_name)s
is substituted with he name of the mailing list. Note that the trailing
"s" is required^2.
For example, a footer containing the following text:
This is the \%(list_name)s mailing list
Description: \%(description)s
might get attached to postings like so:
This is the Example mailing list
Description: An example of Mailman mailing lists
Here is the list of substitution variables available for your headers
and footers:
real_name
This is the value of the real_name configuration variable in the
General options category.
list_name
This is the canonical name of the mailing list. In other words
it's the posting address of the list^3.
host_name
This is the domain name part of the email address for this list.
web_page_url
This is the base url for contacting the list via the web. It can
be appended with listinfo/%(list_name)s to yield the general
list information page for the mailing list.
description
The brief description of the mailing list.
info
This is the full description of the mailing list.
cgiext
This is the extension added to CGI scripts. It might be the
empty string, .cgi, or something else depending on how your site
is configured.
Note that real_name, host_name, description, and info substitution
variables take their values from the list configuration variables of
the same name.
When personalization is enabled, the following substitution variables
are also available:
user_address
The address of the recipient of the message, coerced to lower
case.
user_delivered_to
The case-preserved address that the user subscribed to the
mailing list with^4.
user_password
The user's password, in clear text.
user_name
The user's full name.
user_optionsurl
The url to the user's personal options page.
2.6 The Digest Options Category
Digest delivery is a way to bundle many articles together into one
package, which can be delivered once per day (if there were any posted
articles), or whenever the package is bigger than a specified limit.
Some users may prefer this style of delivery for higher traffic lists
since they will receive fewer messages.
Mailman supports two standard digest formats, and if digests are
enabled, users can select which of the two formats they receive. One is
MIME digests, where each message is an attachment inside a
multipart/digest. This format also contains a summary table of
contents, and of course the an optional header and footer, and it
retains most of the headers of the original messages.
The second type is called ``plaintext'' digests because they are
readable in mail readers that don't support MIME. Actually, they adhere
to the RFC 1153 digest standard. They retain some, but not all of the
original messages, but can also include a summary and headers and
footers.
Like non-digest delivery, you can enable or disable digest delivery,
but you cannot disable both types of delivery. You can specify
different headers and footers for digest and non-digest deliveries. You
cannot personalize digest deliveries.
As list administrator, you may want to send an urgent message to all
list members, bypassing the normal digest bundling. To do this, send
the message with a Urgent: header, where the value of the header is the
list administrator's password. Non-digest members will receive the
message like normal, but digest members will receive the message
immediately^5.
Here are the variables which control digest delivery:
digestable
The option controls whether members can receive digest
deliveries or not. If not, they will be forced to receive
immediate deliveries. You can't disable digests if non-digests
are already disabled.
digest_is_default
Controls which style of delivery is the default for new members.
You can choose Regular (non-digest) or Digest delivery.
mime_is_default_digest
If a member is allowed to choose digests, this variable controls
which is the default digest style they will receive. Plain
digests are RFC 1153 format as described above.
digest_size_threshold
Normally, digest members get at least one message per day, if
there have been any messages posted to the list. However, for
high volume lists, you may want to send out digests when the
size has reached a certain threshold, otherwise, the one digest
they receive could be huge. This variable controls the size
threshold by specifying the maximum digest size in kilobytes.
Note that this threshold isn't exact. Set this variable to zero
to specify that there is no size threshold, in which case no
more than one digest will be sent out per day, but ensure that
digest_send_periodic is Yes in this case or no digests will be
sent.
digest_send_periodic
This variable actually controls whether or not a digest is sent
daily when the size threshold has not yet been met. If set to
No, then digests will only be sent when they are bigger than
digest_size_threshold.
digest_header
This text box lets you enter information that will be included
in the header of every digest message sent through the list. The
same information can go in this header as can go in the
msg_header, except for the personalization variables.
digest_footer
Just like with the header, you can add a footer to every
message. The same rules apply to digest footers as apply to
digest headers.
digest_volume_frequency
Each digest is numbered with a volume and an issue. This
variable controls how often a new digest volume is sent. When
the digest volume number is incremented, the issue number is
reset to 1.
_new_volume
This is an action variable, which forces an increment of the
volume number as soon as you submit the form.
_send_digest_now
This is another action variable. Select Yes, submit the form,
and the current digest is packaged up and sent to digest
members, regardless of size (well, there has to be at least one
message in the digest).
2.7 The Privacy Options Category
The Privacy category lets you control how much of the list's
information is public, as well as who can send messages to your list.
It also contains some spam detection filters. Note that this section is
not used to control whether your list's archives are public or private;
for that, use the category.
There are four sub-categories:
* Subscription rules - i.e. the rules for joining and leaving your
mailing list
* Sender filters - the rules for who may post messages to your list
* Recipient filters - moderation rules based on the recipient of the
message
* Spam filters - some regular expression based rules for header
matching
The sender, recipient, and spam filtering rules are part of the general
list moderation features of Mailman. When a message is posted to the
list, it is matched against a number of criteria, the outcome of which
determines whether the message is reflected to the membership or not.
In general, the outcome is one of four states:
* Approved or Accepted - the message may be sent on to the members of
the mailing list.
* Hold - the message will be held for moderator approval. The list
owners and moderators will then have to explicitly approve the
message before the list members will see it.
* Reject - the message is bounced back to the original sender, often
with a notice containing the reason the message was rejected. The
list members never see rejected messages.
* Discard - the message is simply thrown away without further
processing.
Many of the fields in this section are text boxes accepting addresses,
one per line. Unless otherwise noted, these also accept regular
expressions which will be matched against an address, if the line
begins with a ^ (caret) character.
2.7.1 Subscription rules
This subcategory controls the rules for exposing the existence of this
list, and for what new members must do in order to subscribe to the
list.
advertised
This option controls whether this list will show up in the list
overview for the site. Normally, an overview contains the name
and short description of every mailing list in the virtual
domain. By setting this variable to No, it will not show up in
this overview, nor will it show up in the administrative
overview. The only way then to find the list is to guess (or
know!) its name.
subscribe_policy
This option controls the steps that a new member must take to
join the list. The available options may differ based on some
defaults that the site administrator chooses. They are:
+ None - No verification is done on the subscribing member. This
is also called open subscriptions and is generally disabled by
default. The site administrator must allow list admins to
choose this option; if not, this option will not be presented
to you.
+ Confirm - An email confirmation step is required before the
address is added to the list. When a member requests
subscription, either via the web page or by sending a message
to yourlist-join@example.com, Mailman will send a confirmation
message to the requesting address. This mail-back confirmation
contains a unique identifier, which the requester can present
to Mailman in order to confirm their subscription. This can be
done either by replying to the mail-back, or by visiting the
url in the mail-back message. The url points to a page that
lets the user either discard or confirm their request.
+ Require approval - All subscription requests are held for
approval of the list moderator. No mail-back confirmation is
sent, but the list admins will recieve a message indicating
that approval is pending.
+ Confirm and approve - Here, a mail-back notice must first be
confirmed by the requester. Once confirmed, the list moderator
must then approve the request. This is the most secure method
for users to subscribe since it both verifies the requesting
address, and forces the list moderators to approve the
request.
unsubscribe_policy
Specifies whether the list moderator's approval is required for
unsubscription requests. No is highly recommended, since it is
exceedingly impolite to not allow people to leave a mailing list
whenever they want (i.e. opt-out). Yes is useful in some
specialized contexts; e.g. you may not want to allow employees
to unsubscribe from the company newsletter.
ban_list
This contains a list of addresses (or regular expressions), one
per line, that are banned from ever subscribing to your mailing
list. If a match occurs during the subscription process, the
request will be automatically rejected, and the requester will
get a rejection notice. You can use this to permanently ban
troublesome posters to a members-only list.
private_roster
This specifies who is allowed to view the roster of member
addresses. If you choose Anyone, then the list membership is
completely public. You can limit exposure of the roster to just
list members, or just to the list administrators. In the former
case, a user must enter a valid member's address and password
before they can view the roster. In the latter case, a list
administrator's password must be entered; if a matching admin
password is entered, address field is ignored.
obscure_addresses
Controls whether some simple obfuscation of addresses is used
when member addresses are included on web pages. This should
reduce the opportunity for email address harvesting by spammers,
although it probably doesn't eliminate it.
2.7.2 Sender filters
When a message is posted to the list, a series of moderation criteria
is applied to determine the disposition of the message. This section
contains the moderation controls for postings from both members and
non-members.
default_member_moderation
Member postings are held for moderation if their moderation flag
is turned on. Note that only the list administrators can change
the value of a member's moderation flag.
You can control whether new members get their moderation flag
turned on or off by default when they subscribe to the list. By
turning this flag off by default, postings by members will be
allowed without further intervention (barring other restrictions
such as size or implicit recipient lists - see below). By
turning the flag on, you can quarantine new member postings to
make sure that they meet your criteria for netiquette,
topicality, etc. Once you determine that the new member
understands the community's posting rules, you can turn off
their moderation flag and let their postings go through
unstopped.
E-newsletter style lists can also be set up by using the
moderation flag. By setting the member_moderation_action to
Reject, and by turning off the moderation flag for just the few
approved senders, your list will operate in essentially a
one-way direction. Note that you'd also need to reject or
discard postings from non-members.
member_moderation_action
This is the action to take for postings from a member who's
moderation flag is set. For typical discussion lists, you'll
likely set this to Hold so that the list moderator will get a
chance to manually approve, reject, or discard the message. For
e-newsletter and announcement lists, you might want to set this
to Reject or Discard.
Note that when a moderated member posts to your list, and the
member_moderation_action is set to Hold, the message will appear
on the administrative requests page. When you dispose of the
message, you will be given an opportunity to clear the
moderation flag at the same time. If you're quarantining new
posts, this makes it very convenient to both approve a new
member's post and de-moderate them at the same time.
member_moderation_notice
When a member's moderation flag is turned on and
member_moderation_action is Reject, this variable contains the
text sent in the rejection notice.
The next group of settings control messages whose From: domain
publishes a DMARC p=reject or p=quarantine policy.
dmarc_moderation_action
These actions, Accept, Munge From, Wrap Message, Reject and
Discard apply only to messages whose From: domain publishes a
DMARC p=reject or optionally (see the next setting) p=quarantine
policy. If the message is From: such a domain and this action is
other than Accept, this action applies to the message. Otherwise
the from_is_list setting in section 2.1 applies. See the
from_is_list setting in section 2.1 for a description of the
Munge From and Wrap Message actions.
dmarc_quarantine_moderation_action
If this is set to Yes, the above dmarc_moderation_action applies
to messages with From: domain DMARC policy p=quarantine as well
as p=reject.
dmarc_moderation_notice
When dmarc_moderation_action applies and is Reject, this
variable contains the text sent in the rejection notice. If
empty, a generic notice mentioning DMARC is sent.
The next batch of variables controls what happens when non-members post
messages to the list. Each of these accepts one email address per line;
regular expressions are allowed if the line starts with the ^ (caret)
character. These address lists are always consulted in the order in
which they're presented on this page (i.e. accepts first, followed by
holds, rejections, and discards).
accept_these_nonmembers
Postings from non-members whose addresses match this list are
accepted, barring other list restrictions due to size, implicit
recipients, etc. You might want to add alternative addresses of
approved posters to this list.
hold_these_nonmembers
Postings from non-members whose addresses match this list are
held for moderator approval.
reject_these_nonmembers
Postings from non-members whose addresses match this list are
rejected, i.e. bounced back to the original sender. There is
currently no way to add additional text to the rejection
message.
discard_these_nonmembers
Postings from non-members whose addresses match this list are
discarded, with no bounce back message. You might want to add
the addresses of known spammers to this list.
generic_nonmember_action
This variable controls what happens to non-member posts when the
address of the sender doesn't match any of the above four lists.
If you set this to Hold, the posting will appear on the
administrative requests page, and you will be given an
opportunity to add the non-member to one of the above four lists
at the same time you dispose of the held message.
forward_auto_discards
When messages from non-members are discarded, either because the
sender address matched discard_these_nonmembers, or because
generic_nonmember_action is Discard, you can choose whether such
messages are forwarded to the list administrators or not.
2.7.3 Recipient Filters
The variables in this section control various filters based on the
recipient of the message.
require_explicit_destination
This controls whether the mailing list posting address must be
explicitly named in the To: or Cc: recipient lists. The main
reason why it wouldn't is if the message was blind-carbon-copied
(i.e. Bcc:'d) to the list. Spammers like to do this, but
sometimes legitimate messages are forwarded to the list this
way.
If the list is not explicitly addressed and this setting is
turned on, the message will be held for moderator approval.
acceptable_aliases
This is the list of alternative addresses that are acceptable as
a list posting address when require_explicit_destination is
enabled. This is useful for when there aliases for the main
posting address (e.g. help@example.com may be an alias for
help-list@example.com).
max_num_recipients
This is the maximum number of explicit recipients that are
allowed on the posted message. Spammers sometimes send messages
with lots of explicit recipients, so setting this number to a
reasonable value may cut down on spam.
2.7.4 Spam Filters
This section provides some adjuncts to spam fighting tools; it doesn't
replace dedicated anti-spam tools such as SpamAssassin or SpamBayes.
bounce_matching_headers
This variable contains header regular expressions, one per line,
and if any of a message's headers matches one of these patterns,
it will be held for moderation. The format is a colon separated
header and value, where the header is case insensitive and the
value is any valid Python regular expression. Lines that start
with # are ignored.
This variable can be used to catch known spammers by writing
regexps that match against To: or Cc: lines, or known-bad
Message-ID:s. Perhaps more useful though are patterns that match
headers added by spam detection tools higher up in the tool
chain. For example, you might configure SpamAssassin to add an
X-Spam-Score: header with between zero and 5 stars depending on
the spam score. Then you can add a line to this variable like:
X-Spam-Score: [*]{3,5}
This line will match from 3 to 5 stars in the value of this
field.
2.8 The Bounce Processing Category
These policies control the automatic bounce processing system in
Mailman. Here's an overview of how it works:
When a bounce is received, Mailman tries to extract two pieces of
information from the message: the address of the member the message was
intended for, and the severity of the problem causing the bounce. The
severity can be either hard for fatal errors, or soft for transient
errors. When in doubt, a hard severity is used.
If no member address can be extracted from the bounce, then the bounce
message is usually discarded. Every member has a bounce score,
initialized at zero, and every time we encounter a bounce from a member
we increment that member's score. Hard bounces increment by 1 while
soft bounces increment by 0.5. We only increment the bounce score once
per day, so even if we receive ten hard bounces from a member per day,
their score will increase by only 1 for that day.
When a member's bounce score is greater than the bounce score threshold
(see below), the member's subscription is disabled. Once disabled, the
member will not receive any postings from the list until their
membership is explicitly re-enabled, either by the list administrator
or the user. However, they will receive occasional reminders that their
membership has been disabled, and these reminders will include
information about how to re-enable their membership. You can control
both the number of reminders the member will receive and the frequency
with which these reminders are sent.
There is one other important configuration variable; after a certain
period of time - during which no bounces from the member are received -
the bounce information is considered stale and discarded. Thus by
adjusting this value, and the score threshold, you can control how
quickly bouncing members are disabled. You should tune both of these to
the frequency and traffic volume of your list.
bounce_processing
Specifies whether or not this list should do automatic bounce
processing.
bounce_score_threshold
This is the bounce score above which a member's subscription
will be automatically disabled. When the subscription is
re-enabled, their bounce score will be reset to zero. This value
can be a floating point number.
bounce_info_stale_after
The number of days after which a member's bounce information is
considered stale. If no new bounces have been received in the
interim, the bounce score is reset to zero. This value must be
an integer.
bounce_you_are_disabled_warnings
The number of notices a disabled member will receive before
their address is removed from the mailing list's roster. Set
this to 0 to immediately remove an address from the list once
their bounce score exceeds the threshold. This value must be an
integer.
bounce_you_are_disabled_warnings_interval
The number of days between each disabled notification.
bounce_unrecognized_goes_to_list_owner
This variable controls whether unrecognized bounces are
discarded, or forwarded on the list administrator. The bounce
detector isn't perfect, although personalization can make it
much more accurate. The list owner may want to receive
unrecognized bounces so that they can manually disable or remove
such members.
bounce_notify_owner_on_disable
This option controls whether or not the list owner is notified
when a member's subscription is automatically disabled due to
their bounce threshold being reached.
bounce_notify_owner_on_removal
This option controls whether or not the list owner is notified
when a member is removed from the list after their disabled
notifications have been exhausted.
2.9 The Archiving Options Category
Mailman comes with a built-in web-based archiver called Pipermail,
although it can be configured to use external, third party archivers.
archive
This option tells Mailman whether to archive messages it
receives or not, regardless of whether Pipermail or a third
party archiver is used. Turn this off if you don't want to
archive messages.
Note that senders can control whether their own posts are
archived, on an individual per-message basis. If the posted
message has a X-No-Archive: header (regardless of value), or a
X-Archive: header with a value of No (case insensitive), then
the message will not be archived, although it will be treated as
normal in all other ways.
archive_private
Controls whether Pipermail archives are private or public.
Private archives require a valid member address and password, or
a list administrator password in order to access them. This
option has no effect when a third party archiver is used.
archive_volume_frequency
Controls how Pipermail splits messages in the archive. The most
common option is Monthly meaning a new archive volume is started
every month. Very high volume lists may want a shorter frequency
(e.g. Weekly or Daily) where as lower volume lists may want a
longer frequency (e.g. Yearly). This option has no effect when a
third party archiver is used.
2.10 The Mail/News Gateway Category
Mailman has a sophisticated mail-to-news gateway feature. It can
independently gate messages from news to mail and vice versa, and can
even be used to manage moderated newsgroups.
2.11 The Auto-responder Category
2.12 The Content Filtering Category
2.13 The Topics Category
3 Membership Management
4 Tending to Pending Moderator Requests
5 Editing the Public HTML Pages
6 Deleting the Mailing List
1 This is an Appendix
To create an appendix in a Python HOWTO document, use markup like this:
\appendix
\section{This is an Appendix}
To create an appendix in a Python HOWTO document, ....
\section{This is another}
Just add another \section{}, but don't say \appendix again.
About this document ...
GNU Mailman - List Administration Manual, January 11, 2020, Release 2.1
This document was generated using the LaTeX2HTML translator.
LaTeX2HTML is Copyright © 1993, 1994, 1995, 1996, 1997, Nikos Drakos,
Computer Based Learning Unit, University of Leeds, and Copyright ©
1997, 1998, Ross Moore, Mathematics Department, Macquarie University,
Sydney.
The application of LaTeX2HTML to the Python documentation has been
heavily tailored by Fred L. Drake, Jr. Original navigation icons were
contributed by Christopher Petrilli.
__________________________________________________________________
Footnotes
... representation^1
Specifically, a Python pickle
... required^2
The site administrator can configure lists to use a simpler
interpolation format, where $list_name or ${list_name} would be
substituted with the mailing list's name. Ask your site
administrator if they've configured your list this way.
... list^3
For backward compatibility, the variable _internal_name is
equivalent.
... with^4
Usually it makes no difference which of user_address and
user_delivered_to is used, but it's important to remember that
they can be different. When they're different, Mailman always
uses the lower case address as the key to the member's
subscription information, but it always delivers messages to the
case-preserved version.
... immediately^5
They'll also receive the message in the digest.
__________________________________________________________________
Previous Page Up one Level Next Page GNU Mailman - List Administration
Manual
__________________________________________________________________
Release 2.1, documentation updated on January 11, 2020.
wget 'https://lists2.roe3.org/mdrone/doc/mailman-install.pdf'wget 'https://lists2.roe3.org/mdrone/doc/mailman-install.txt' #GNU mailman - installation Manual About this document... About this
document...
Previous Page Up one Level Next Page GNU Mailman - Installation Manual
__________________________________________________________________
GNU Mailman - Installation Manual
Barry Warsaw
barry (at) list dot org
Release 2.1
January 11, 2020
Front Matter
Abstract:
This document describes how to install GNU Mailman on a POSIX-based
system such as Unix, MacOSX, or GNU/Linux. It will cover basic
installation instructions, as well as guidelines for integrating
Mailman with your web and mail servers.
The GNU Mailman website is at http://www.list.org
1 Installation Requirements
Please note that the information on this page may be out of date. Check
for the latest installation information on the Mailman wiki.
GNU Mailman works on most POSIX-based systems such as Unix, MacOSX, or
GNU/Linux. It does not currently work on Windows. You must have a mail
server that you can send messages to, and a web server that supports
the CGI/1.1 API. Apache makes a fine choice for web server, and mail
servers such as Postfix, Exim, Sendmail, and qmail should work just
fine.
To install Mailman from source, you will need an ANSI C compiler to
build Mailman's security wrappers. The GNU C compiler gcc works well.
You must have the Python interpreter installed somewhere on your
system. As of this writing, Python 2.4.4 is recommended, but see the
wiki page above for the latest information.
2 Set up your system
Before installing Mailman, you need to prepare your system by adding
certain users and groups. You will need to have root privileges to
perform the steps in this section.
2.1 Add the group and user
Mailman requires a unique user and group name which will own its files,
and under which its processes will run. Mailman's basic security is
based on group ownership permissions, so it's important to get this
step right^1. Typically, you will add a new user and a new group, both
called mailman. The mailman user must be a member of the mailman group.
Mailman will be installed under the mailman user and group, with the
set-group-id (setgid) bit enabled.
If these names are already in use, you can choose different user and
group names, as long as you remember these when you run configure. If
you choose a different unique user name, you will have to specify this
with configure's --with-username option, and if you choose a different
group name, you will have to specify this with configure's
--with-groupname option.
On Linux systems, you can use the following commands to create these
accounts. Check your system's manual pages for details:
% groupadd mailman
% useradd -c"GNU Mailman" -s /no/shell -d /no/home -g mailman mailman
2.2 Create the installation directory
Typically, Mailman is installed into a single directory, which includes
both the Mailman source code and the run-time list and archive data. It
is possible to split the static program files from the variable data
files and install them in separate directories. This section will
describe the available options.
The default is to install all of Mailman to /usr/local/mailman^2. You
can change this base installation directory (referred to here as
$prefix) by specifying the directory with the --prefix configure
option. If you're upgrading from a previous version of Mailman, you may
want to use the --prefix option unless you move your mailing lists.
Warning: You cannot install Mailman on a filesystem that is mounted
with the nosuid option. This will break Mailman, which relies on setgid
programs for its security. If this describes your environment, simply
install Mailman in a location that allows setgid programs.
Make sure the installation directory is set to group mailman (or
whatever you're going to specify with --with-groupname) and has the
setgid bit set^3. You probably also want to guarantee that this
directory is readable and executable by everyone. For example, these
shell commands will accomplish this:
% cd $prefix
% chgrp mailman .
% chmod a+rx,g+ws .
Warning: The installation directory, $prefix, cannot be the same
directory that the source tarball has been unpacked to and in which you
run configure, but it can, if you wish, be a subdirectory, e.g.,
$prefix/src.
You are now ready to configure and install the Mailman software.
3 Build and install Mailman
3.1 Run configure
Before you can install Mailman, you must run configure to set various
installation options your system might need.
Note: Take special note of the --with-mail-gid and --with-cgi-gid
options below. You will probably need to use these.
You should not be root while performing the steps in this section. Do
them under your own login, or whatever account you typically use to
install software. You do not need to do these steps as user mailman,
but you could. However, make sure that the login used is a member of
the mailman group as that that group has write permissions to the
$prefix directory made in the previous step. You must also have
permission to create a setgid file in the file system where it resides
(NFS and other mounts can be configured to inhibit setgid settings).
If you've installed other GNU software, you should be familiar with the
configure script. Usually you can just cd to the directory you unpacked
the Mailman source tarball into, and run configure with no arguments:
% cd mailman-<version>
% ./configure
% make install
The following options allow you to customize your Mailman installation.
--prefix=dir
Standard GNU configure option which changes the base directory
that Mailman is installed into. By default $prefix is
/usr/local/mailman. This directory must already exist, and be
set up as described in 2.2.
--exec-prefix=dir
Standard GNU configure option which lets you specify a different
installation directory for architecture dependent binaries.
--with-var-prefix=dir
Store mutable data under dir instead of under the $prefix or
$exec_prefix. Examples of such data include the list archives
and list settings database.
--with-python=/path/to/python
Specify an alternative Python interpreter to use for the wrapper
programs. The default is to use the interpreter found first on
your shell's $PATH.
--with-username=username-or-uid
Specify a different username than mailman. The value of this
option can be an integer user id or a user name. Be sure your
$prefix directory is owned by this user.
--with-groupname=groupname-or-gid
Specify a different groupname than mailman. The value of this
option can be an integer group id or a group name. Be sure your
$prefix directory is group-owned by this group.
--with-mail-gid=group-or-groups
Specify an alternative group for running scripts via the mail
wrapper. group-or-groups can be a list of one or more integer
group ids or symbolic group names. The first value in the list
that resolves to an existing group is used. By default, the
value is the list mailman, other, mail, and daemon.
Note: This is highly system dependent and you must get this
right, because the group id is compiled into the mail wrapper
program for added security. On systems using sendmail, the
sendmail.cf configuration file designates the group id of
sendmail processes using the DefaultUser option. (If commented
out, it still may be indicating the default...)
Check your mail server's documentation and configuration files
to find the right value for this switch.
--with-cgi-gid=group-or-groups
Specify an alternative group for running scripts via the CGI
wrapper. group-or-groups can be a list of one or more integer
group ids or symbolic group names. The first value in the list
that resolves to an existing group is used. By default, the
value is the the list www, www-data, and nobody.
Note: The proper value for this is dependent on your web server
configuration. You must get this right, because the group id is
compiled into the CGI wrapper program for added security, and no
Mailman CGI scripts will run if this is incorrect.
If you're using Apache, check the values for the Group option in
your httpd.conf file.
--with-cgi-ext=extension
Specify an extension for cgi-bin programs. The CGI wrappers
placed in $prefix/cgi-bin will have this extension (some web
servers require an extension). extension must include the
leading dot.
--with-mailhost=hostname
Specify the fully qualified host name part for outgoing email.
After the installation is complete, this value can be overriden
in $prefix/Mailman/mm_cfg.py.
--with-urlhost=hostname
Specify the fully qualified host name part of urls. After the
installation is complete, this value can be overriden in
$prefix/Mailman/mm_cfg.py.
--with-gcc=no
Don't use gcc, even if it is found. In this case, cc must be
found on your $PATH.
3.2 Make and install
Once you've run configure, you can simply run make, then make install
to build and install Mailman.
4 Check your installation
After you've run make install, you should check that your installation
has all the correct permissions and group ownerships by running the
check_perms script. First change to the installation (i.e. $prefix)
directory, then run the bin/check_perms program. Don't try to run
bin/check_perms from the source directory; it will only run from the
installation directory.
If this reports no problems, then it's very likely <wink> that your
installation is set up correctly. If it reports problems, then you can
either fix them manually, re-run the installation, or use
bin/check_perms to fix the problems (probably the easiest solution):
* You need to become the user that did the installation, and that
owns all the files in $prefix, or root.
* Run bin/check_perms -f
* Repeat previous step until no more errors are reported!
Warning: If you're running Mailman on a shared multiuser system, and
you have mailing lists with private archives, you may want to hide the
private archive directory from other users on your system. In that
case, you should drop the other execute permission (o-x) from the
archives/private directory. However, the web server process must be
able to follow the symbolic link in public directory, otherwise your
public Pipermail archives will not work. To set this up, become root
and run the following commands:
# cd <prefix>/archives
# chown <web-server-user> private
# chmod o-x private
You need to know what user your web server runs as. It may be www,
apache, httpd or nobody, depending on your server's configuration.
5 Set up your web server
Congratulations! You've installed the Mailman software. To get
everything running you need to hook Mailman up to both your web server
and your mail system.
If you plan on running your mail and web servers on different machines,
sharing Mailman installations via NFS, be sure that the clocks on those
two machines are synchronized closely. You might take a look at the
file Mailman/LockFile.py; the constant CLOCK_SLOP helps the locking
mechanism compensate for clock skew in this type of environment.
This section describes some of the things you need to do to connect
Mailman's web interface to your web server. The instructions here are
somewhat geared toward the Apache web server, so you should consult
your web server documentation for details.
You must configure your web server to enable CGI script permission in
the $prefix/cgi-bin to run CGI scripts. The line you should add might
look something like the following, with the real absolute directory
substituted for $prefix, of course:
Exec /mailman/* $prefix/cgi-bin/*
or:
ScriptAlias /mailman/ $prefix/cgi-bin/
Warning: You want to be very sure that the user id under which your CGI
scripts run is not in the mailman group you created above, otherwise
private archives will be accessible to anyone.
Copy the Mailman, Python, and GNU logos to a location accessible to
your web server. E.g. with Apache, you've usually got an icons
directory that you can drop the images into. For example:
% cp $prefix/icons/*.{jpg,png} /path/to/apache/icons
You then want to add a line to your $prefix/Mailman/mm_cfg.py file
which sets the base URL for the logos. For example:
IMAGE_LOGOS = '/images/'
The default value for IMAGE_LOGOS is /icons/. Read the comment in
Defaults.py.in for details.
Configure your web server to point to the Pipermail public mailing list
archives. For example, in Apache:
Alias /pipermail/ $varprefix/archives/public/
where $varprefix is usually $prefix unless you've used the
--with-var-prefix option to configure. Also be sure to configure your
web server to follow symbolic links in this directory, otherwise public
Pipermail archives won't be accessible. For Apache users, consult the
FollowSymLinks option.
If you're going to be supporting internationalized public archives, you
will probably want to turn off any default charset directive for the
Pipermail directory, otherwise your multilingual archive pages won't
show up correctly. Here's an example for Apache, based on the standard
installation directories:
<Directory "/usr/local/mailman/archives/public/">
AddDefaultCharset Off
</Directory>
Also, you may need to specifically allow access to Mailman's
directories. For example, in Apache, the above Directory block may need
something like
Require all granted
or
Order allow,deny
Allow from all
depending on the Apache version and similarly for the $prefix/cgi-bin/
directory.
Now restart your web server.
6 Set up your mail server
This section describes some of the things you need to do to connect
Mailman's email interface to your mail server. The instructions here
are different for each mail server; if your mail server is not
described in the following subsections, try to generalize from the
existing documentation, and consider contributing documentation updates
to the Mailman developers.
Under rare circumstances or due to mis-configuration, mail to the
owner(s) of the 'mailman' site-list (see section 8) can bounce. In
order to prevent a mail loop this mail is sent with envelope from
mailman-loop which is normally aliased as
mailman-loop: $varprefix/data/owner-bounces.mbox
but which can be aliased to any, always deliverable, local address or
file. If you are using the Postfix MTA integrated as described in
section 6.1, this alias will be generated automatically. In all other
cases, you should install this alias along with your normal system
aliases.
6.1 Using the Postfix mail server
Mailman should work pretty much out of the box with a standard Postfix
installation. It has been tested with various Postfix versions up to
and including Postfix 2.11.3 (as of April 2016).
In order to support Mailman's optional VERP delivery, you will want to
disable luser_relay (the default) and you will want to set
recipient_delimiter for extended address semantics. You should comment
out any luser_relay value in your main.cf and just go with the
defaults. Also, add this to your main.cf file:
recipient_delimiter = +
Using "+" as the delimiter works well with the default values for
VERP_FORMAT and VERP_REGEXP in Defaults.py.
When attempting to deliver a message to a non-existent local address,
Postfix may return a 450 error code. Since this is a transient error
code, Mailman will continue to attempt to deliver the message for
DELIVERY_RETRY_PERIOD - 5 days by default. You might want to set
Postfix up so that it returns permanent error codes for non-existent
local users by adding the following to your main.cf file:
unknown_local_recipient_reject_code = 550
Finally, if you are using Postfix-style virtual domains, read the
section on virtual domain support below.
6.1.1 Integrating Postfix and Mailman
You can integrate Postfix and Mailman such that when new lists are
created, or lists are removed, Postfix's alias database will be
automatically updated. The following are the steps you need to take to
make this work.
In the description below, we assume that you've installed Mailman in
the default location, i.e. /usr/local/mailman. If that's not the case,
adjust the instructions according to your use of configure's --prefix
and --with-var-prefix options.
Note: If you are using virtual domains and you want Mailman to honor
your virtual domains, read the 6.1 section below first! Then come back
here and do these steps.
* Add this to the bottom of the $prefix/Mailman/mm_cfg.py file:
MTA = 'Postfix'
The MTA variable names a module in the Mailman/MTA directory which
contains the mail server-specific functions to be executed when a
list is created or removed.
* Look at the Defaults.py file for the variables POSTFIX_ALIAS_CMD
and POSTFIX_MAP_CMD command. Make sure these point to your
postalias and postmap programs respectively. Remember that if you
need to make changes, do it in mm_cfg.py.
* Run the bin/genaliases script to initialize your aliases file.
% cd /usr/local/mailman
% bin/genaliases
Make sure that the owner of the data/aliases and data/aliases.db
file is mailman, that the group owner for those files is mailman,
or whatever user and group you used in the configure command, and
that both files are group writable:
% su
% chown mailman:mailman data/aliases*
% chmod g+w data/aliases*
* Hack your Postfix's main.cf file to include the following path in
your alias_maps variable:
/usr/local/mailman/data/aliases
Note that there should be no trailing .db. Do not include this in
your alias_database variable. This is because you do not want
Postfix's newaliases command to modify Mailman's aliases.db file,
but you do want Postfix to consult aliases.db when looking for
local addresses.
You probably want to use a hash: style database for this entry.
Here's an example:
alias_maps = hash:/etc/postfix/aliases,
hash:/usr/local/mailman/data/aliases
* When you configure Mailman, use the --with-mail-gid=mailman switch;
this will be the default if you configured Mailman after adding the
mailman owner. Because the owner of the aliases.db file is mailman,
Postfix will execute Mailman's wrapper program as uid and gid
mailman.
That's it! One caveat: when you add or remove a list, the aliases.db
file will updated, but it will not automatically run postfix reload.
This is because you need to be root to run this and suid-root scripts
are not secure. The only effect of this is that it will take about a
minute for Postfix to notice the change to the aliases.db file and
update its tables.
6.1.2 Virtual domains
Note: This section describes how to integrate Mailman with Postfix for
automatic generation of Postfix virtual_alias_maps for Mailman list
addresses. Mailman's support of virtual domains is limited in that list
names must be globally unique within a single Mailman instance, i.e.,
two lists may not have the same name even if they are in different
domains.
Postfix 2.0 supports ``virtual alias domains'', essentially what used
to be called ``Postfix-style virtual domains'' in earlier Postfix
versions. To make virtual alias domains work with Mailman, you need to
do some setup in both Postfix and Mailman. Mailman will write all
virtual alias mappings to a file called, by default,
/usr/local/mailman/data/virtual-mailman. It will also use postmap to
create the virtual-mailman.db file that Postfix will actually use.
First, you need to set up the Postfix virtual alias domains as
described in the Postfix documentation (see Postfix's virtual(5)
manpage). Note that it's your responsibility to include the
virtual-alias.domain anything line as described manpage (in recent
Postfix this is not required if the domain is included in
virtual_alias_domains in main.cf); Mailman will not include this line
in virtual-mailman. You are highly encouraged to make sure your virtual
alias domains are working properly before integrating with Mailman.
Next, add a path to Postfix's virtual_alias_maps variable, pointing to
the virtual-mailman file, e.g.:
virtual_alias_maps = <your normal virtual alias files>,
hash:/usr/local/mailman/data/virtual-mailman
assuming you've installed Mailman in the default location. If you're
using an older version of Postfix which doesn't have the
virtual_alias_maps variable, use the virtual_maps variable instead.
The default mappings in virtual-mailman map list addresses in virtual
domains to unqualified local names as in:
mylist@dom.ain mylist
mylist-request@dom.ain mylist-request
# and so on...
In some Postfix configurations it may be necessary to qualify those
local names as for example:
mylist@dom.ain mylist@localhost
mylist-request@dom.ain mylist-request@localhost
# and so on...
If this is the case, you can include
VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'
or whatever qualification is needed in mm_cfg.py.
Next, in your mm_cfg.py file, you will want to set the variable
POSTFIX_STYLE_VIRTUAL_DOMAINS to the list of virtual domains that
Mailman should update. This may not be all of the virtual alias domains
that your Postfix installation supports! The values in this list will
be matched against the host_name attribute of mailing lists objects,
and must be an exact match.
Here's an example. Note that this example describes an unusual
configuration. A more usual configuration is described next. Say that
Postfix is configured to handle the virtual domains dom1.ain, dom2.ain,
and dom3.ain, and further that in your main.cf file you've got the
following settings:
myhostname = mail.dom1.ain
mydomain = dom1.ain
mydestination = $myhostname, localhost.$mydomain
virtual_alias_maps =
hash:/some/path/to/virtual-dom1,
hash:/some/path/to/virtual-dom2,
hash:/some/path/to/virtual-dom2
If in your virtual-dom1 file, you've got the following lines:
dom1.ain IGNORE
@dom1.ain @mail.dom1.ain
this tells Postfix to deliver anything addressed to dom1.ain to the
same mailbox at mail.dom1.com, its default destination.
In this case you would not include dom1.ain in
POSTFIX_STYLE_VIRTUAL_DOMAINS because otherwise Mailman will write
entries for mailing lists in the dom1.ain domain as
mylist@dom1.ain mylist
mylist-request@dom1.ain mylist-request
# and so on...
The more specific entries trump your more general entries, thus
breaking the delivery of any dom1.ain mailing list.
However, you would include dom2.ain and dom3.ain in mm_cfg.py:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain']
Now, any list that Mailman creates in either of those two domains, will
have the correct entries written to
/usr/local/mailman/data/virtual-mailman.
In a more usual configuration, dom1.ain would not be a virtual domain
at all as in the following:
myhostname = mail.dom1.ain
mydomain = dom1.ain
mydestination = $myhostname, $mydomain localhost.$mydomain
virtual_alias_maps =
hash:/some/path/to/virtual-dom2,
hash:/some/path/to/virtual-dom2
In this case too, you would include dom2.ain and dom3.ain in mm_cfg.py:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain']
As in the previous section with the data/aliases* files, you want to
make sure that both data/virtual-mailman and data/virtual-mailman.db
are user and group owned by mailman.
6.1.3 An alternative approach
Fil fil@rezo.net has an alternative approach based on virtual maps and
regular expressions, as described at:
* (French) http://listes.rezo.net/comment.php
* (English) http://listes.rezo.net/how.php
This is a good (and simpler) alternative if you don't mind exposing an
additional hostname in the domain part of the addresses people will use
to contact your list. I.e. if people should use mylist@lists.dom.ain
instead of mylist@dom.ain.
6.2 Using the Exim mail server
Note: This section is derived from Nigel Metheringham's ``HOWTO - Using
Exim and Mailman together'', which covers Mailman 2.0.x and Exim 3. It
has been updated to cover Mailman 2.1 and Exim 4. The updated document
is here: http://www.exim.org/howto/mailman21.html and is recommended
over the information in the subsections below if you are using Exim 4.
There is no Mailman configuration needed other than the standard
options detailed in the Mailman install documentation. The Exim
configuration is transparent to Mailman. The user and group settings
for Mailman must match those in the config fragments given below.
6.2.1 Exim configuration
The Exim configuration is built so that a list created within Mailman
automatically appears to Exim without the need for defining any
additional aliases.
The drawback of this configuration is that it will work poorly on
systems supporting lists in several different mail domains. While
Mailman handles virtual domains, it does not yet support having two
distinct lists with the same name in different virtual domains, using
the same Mailman installation. This will eventually change. (But see
below for a variation on this scheme that should accommodate virtual
domains better.)
The configuration file excerpts below are for use in an already
functional Exim configuration, which accepts mail for the domain in
which the list resides. If this domain is separate from the others
handled by your Exim configuration, then you'll need to:
* add the list domain, ``my.list.domain'' to local_domains
* add a ``domains=my.list.domain'' option to the director (router)
for the list
* (optional) exclude that domain from your other directors (routers)
Note: The instructions in this document should work with either Exim 3
or Exim 4. In Exim 3, you must have a local_domains configuration
setting; in Exim 4, you most likely have a local_domains domainlist. If
you don't, you probably know what you're doing and can adjust
accordingly. Similarly, in Exim 4 the concept of ``directors'' has
disappeared - there are only routers now. So if you're using Exim 4,
whenever this document says ``director'', read ``router''.
Whether you are using Exim 3 or Exim 4, you will need to add some
macros to the main section of your Exim config file. You will also need
to define one new transport. With Exim 3, you'll need to add a new
director; with Exim 4, a new router plays the same role.
Finally, the configuration supplied here should allow co-habiting
Mailman 2.0 and 2.1 installations, with the proviso that you'll
probably want to use mm21 in place of mailman - e.g., MM21_HOME,
mm21_transport, etc.
6.2.2 Main configuration settings
First, you need to add some macros to the top of your Exim config file.
These just make the director (router) and transport below a bit
cleaner. Obviously, you'll need to edit these based on how you
configured and installed Mailman.
# Home dir for your Mailman installation -- aka Mailman's prefix
# directory.
MAILMAN_HOME=/usr/local/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/mailman
# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.
MAILMAN_USER=mailman
MAILMAN_GROUP=mailman
6.2.3 Transport for Exim 3
Add this to the transports section of your Exim config file, i.e.
somewhere between the first and second ``end'' line:
mailman_transport:
driver = pipe
command = MAILMAN_WRAP \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = MAILMAN_HOME
home_directory = MAILMAN_HOME
user = MAILMAN_USER
group = MAILMAN_GROUP
6.2.4 Director for Exim 3
If you're using Exim 3, you'll need to add the following director to
your config file (directors go between the second and third ``end''
lines). Also, don't forget that order matters - e.g. you can make
Mailman lists take precedence over system aliases by putting this
director in front of your aliasfile director, or vice-versa.
# Handle all addresses related to a list 'foo': the posting address.
# Automatically detects list existence by looking
# for lists/$local_part/config.pck under MAILMAN_HOME.
mailman_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/$local_part/config.pck
suffix_optional
suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
transport = mailman_transport
6.2.5 Router for Exim 4
In Exim 4, there's no such thing as directors - you need to add a new
router instead. Also, the canonical order of the configuration file was
changed so routers come before transports, so the router for Exim 4
comes first here. Put this router somewhere after the ``begin routers''
line of your config file, and remember that order matters.
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.pck
local_part_suffix_optional
local_part_suffix = -admin : -bounces : -bounces+* : \
-confirm : -confirm+* : \
-join : -leave : \
-owner : -request : \
-subscribe : -unsubscribe
transport = mailman_transport
6.2.6 Transports for Exim 4
The transport for Exim 4 is the same as for Exim 3 (see 6.2; just copy
the transport given above to somewhere under the ``begin transports''
line of your Exim config file.
6.2.7 Additional notes
Exim should be configured to allow reasonable volume - e.g. don't set
max_recipients down to a silly value - and with normal degrees of
security - specifically, be sure to allow relaying from 127.0.0.1, but
pretty much nothing else. Parallel deliveries and other tweaks can also
be used if you like; experiment with your setup to see what works.
Delay warning messages should be switched off or configured to only
happen for non-list mail, unless you like receiving tons of mail when
some random host is down.
6.2.8 Problems
* Mailman will send as many MAIL FROM/RCPT TO as it needs. It may
result in more than 10 or 100 messages sent in one connection,
which will exceed the default value of Exim's
smtp_accept_queue_per_connection value. This is bad because it will
cause Exim to switch into queue mode and severely delay delivery of
your list messages. The way to fix this is to set Mailman's
SMTP_MAX_SESSIONS_PER_CONNECTION (in $prefix/Mailman/mm_cfg.py) to
a smaller value than Exim's smtp_accept_queue_per_connection.
* Mailman should ignore Exim delay warning messages, even though Exim
should never send this to list messages. Mailman 2.1's general
bounce detection and VERP support should greatly improve the bounce
detector's hit rates.
* List existence is determined by the existence of a config.pck file
for a list. If you delete lists by foul means, be aware of this.
* If you are getting Exim or Mailman complaining about user ids when
you send mail to a list, check that the MAILMAN_USER and
MAILMAN_GROUP match those of Mailman itself (i.e. what were used in
the configure script). Also make sure you do not have aliases in
the main alias file for the list.
6.2.9 Receiver Verification
Exim's receiver verification feature is very useful - it lets Exim
reject unrouteable addresses at SMTP time. However, this is most useful
for externally-originating mail that is addressed to mail in one of
your local domains. For Mailman list traffic, mail originates on your
server, and is addressed to random external domains that are not under
your control. Furthermore, each message is addressed to many recipients
- up to 500 if you use Mailman's default configuration and don't tweak
SMTP_MAX_RCPTS.
Doing receiver verification on Mailman list traffic is a recipe for
trouble. In particular, Exim will attempt to route every recipient
addresses in outgoing Mailman list posts. Even though this requires
nothing more than a few DNS lookups for each address, it can still
introduce significant delays. Therefore, you should disable recipient
verification for Mailman traffic.
Under Exim 3, put this in your main configuration section:
receiver_verify_hosts = !127.0.0.1
Under Exim 4, this is probably already taken care of for you by the
default recipient verification ACL statement (in the RCPT TO ACL):
accept domains = +local_domains
endpass
message = unknown user
verify = recipient
which only does recipient verification on addresses in your domain.
(That's not exactly the same as doing recipient verification only on
messages coming from non-127.0.0.1 hosts, but it should do the trick
for Mailman.)
6.2.10 SMTP Callback
Exim's SMTP callback feature is an even more powerful way to detect
bogus sender addresses than normal sender verification. Unfortunately,
lots of servers send bounce messages with a bogus address in the
header, and there are plenty that send bounces with bogus envelope
senders (even though they're supposed to just use an empty envelope
sender for bounces).
In order to ensure that Mailman can disable/remove bouncing addresses,
you generally want to receive bounces for Mailman lists, even if those
bounces are themselves not bounceable. Thus, you might want to disable
SMTP callback on bounce messages.
With Exim 4, you can accomplish this using something like the following
in your RCPT TO ACL:
# Accept bounces to lists even if callbacks or other checks would fail
warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes
condition = \
${if and {{match{$local_part}{(.*)-bounces\+.*}} \
{exists {MAILMAN_HOME/lists/$1/config.pck}}} \
{yes}{no}}
accept condition = \
${if and {{match{$local_part}{(.*)-bounces\+.*}} \
{exists {MAILMAN_HOME/lists/$1/config.pck}}} \
{yes}{no}}
# Now, check sender address with SMTP callback.
deny !verify = sender/callout=90s
If you also do SMTP callbacks on header addresses, you'll want
something like this in your DATA ACL:
deny !condition = $header_X-WhitelistedRCPT-nohdrfromcallback:
!verify = header_sender/callout=90s
6.2.11 Doing VERP with Exim and Mailman
VERP will send one email, with a separate envelope sender (return
path), for each of your subscribers - read the information in
$prefix/Mailman/Defaults.py for the options that start with VERP. In a
nutshell, all you need to do to enable VERP with Exim is to add these
lines to $prefix/Mailman/mm_cfg.py:
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
(The director (router) above is smart enough to deal with VERP
bounces.)
6.2.12 Virtual Domains
One approach to handling virtual domains is to use a separate Mailman
installation for each virtual domain. Currently, this is the only way
to have lists with the same name in different virtual domains handled
by the same machine.
In this case, the MAILMAN_HOME and MAILMAN_WRAP macros are useless -
you can remove them. Change your director (router) to something like
this:
require_files = /virtual/${domain}/mailman/lists/${lc:$local_part}/config.pck
and change your transport like this:
command = /virtual/${domain}/mailman/mail/mailman \
${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}}
{post}} \
$local_part
current_directory = /virtual/${domain}/mailman
home_directory = /virtual/${domain}/mailman
6.2.13 List Verification
This is how a set of address tests for the Exim lists look on a working
system. The list in question is quixote-users@mems-exchange.org, and
these commands were run on the mems-exchange.org mail server ("% "
indicates the Unix shell prompt):
% exim -bt quixote-users
quixote-users@mems-exchange.org
router = mailman_main_router, transport = mailman_transport
% exim -bt quixote-users-request
quixote-users-request@mems-exchange.org
router = mailman_router, transport = mailman_transport
% exim -bt quixote-users-bounces
quixote-users-bounces@mems-exchange.org
router = mailman_router, transport = mailman_transport
% exim -bt quixote-users-bounces+luser=example.com
quixote-users-bounces+luser=example.com@mems-exchange.org
router = mailman_router, transport = mailman_transport
If your exim -bt output looks something like this, that's a start: at
least it means Exim will pass the right messages to the right Mailman
commands. It by no means guarantees that your Exim/Mailman installation
is functioning perfectly, though!
6.2.14 Document History
Originally written by Nigel Metheringham postmaster@exim.org. Updated
by Marc Merlin marc_soft@merlins.org for Mailman 2.1, Exim 4.
Overhauled/reformatted/clarified/simplified by Greg Ward
gward@python.net.
6.3 Using the Sendmail mail server
Warning: You may be tempted to set the DELIVERY_MODULE configuration
variable in mm_cfg.py to 'Sendmail' when using the Sendmail mail
server. Don't. The Sendmail.py module is misnamed - it's really a
command line based message handoff scheme as opposed to the SMTP scheme
used in SMTPDirect.py (the default). Sendmail.py has known security
holes and is provided as a proof-of-concept only^4. If you are having
problems using SMTPDirect.py fix those instead of using Sendmail.py, or
you may open your system up to security exploits.
6.3.1 Sendmail ``smrsh'' compatibility
Many newer versions of Sendmail come with a restricted execution
utility called ``smrsh'', which limits the executables that Sendmail
will allow to be used as mail programs. You need to explicitly allow
Mailman's wrapper program to be used with smrsh or Mailman will not
work. If mail is not getting delivered to Mailman's wrapper program and
you're getting an ``operating system error'' in your mail syslog, this
could be your problem.
One good way of enabling this is:
* Find out where your Sendmail executes its smrsh wrapper
% grep smrsh /etc/mail/sendmail.cf
* Figure out where smrsh expects symlinks for allowable mail
programs. At the very beginning of the following output you will
see a full path to some directory, e.g. /var/adm/sm.bin or similar:
% strings $path_to_smrsh | less
* cd into /var/adm/sm.bin, or where ever it happens to reside on your
system - alternatives include /etc/smrsh, /var/smrsh and
/usr/local/smrsh.
% cd /var/adm/sm.bin
* Create a symbolic link to Mailman's wrapper program:
% ln -s /usr/local/mailman/mail/mailman mailman
6.3.2 Integrating Sendmail and Mailman
David Champion has contributed a recipe for more closely integrating
Sendmail and Mailman, such that Sendmail will automatically recognize
and deliver to new mailing lists as they are created, without having to
manually edit alias tables.
In the contrib directory of Mailman's source distribution, you will
find four files:
* mm-handler.readme - an explanation of how to set everything up
* mm-handler - the mail delivery agent (MDA)
* mailman.mc - a toy configuration file sample
* virtusertable - a sample for RFC 2142 address exceptions
6.3.3 Performance notes
One of the surest performance killers for Sendmail users is when
Sendmail is configured to synchronously verify the recipient's host via
DNS. If it does this for messages posted to it from Mailman, you will
get horrible performance. Since Mailman usually connects via localhost
(i.e. 127.0.0.1) to the SMTP port of Sendmail, you should be sure to
configure Sendmail to not do DNS verification synchronously for
localhost connections.
6.4 Using the Qmail mail server
There are some issues that users of the qmail mail transport agent have
encountered. None of the core maintainers use qmail, so all of this
information has been contributed by the Mailman user community,
especially Martin Preishuber and Christian Tismer, with notes by Balazs
Nagy (BN) and Norbert Bollow (NB).
* You might need to set the mail-gid user to either qmail, mailman,
or nofiles by using the --with-mail-gid configure option.
BN: it highly depends on your mail storing policy. For example if
you use the simple ~alias/.qmail-* files, you can use `id -g
alias`. But if you use /var/qmail/users, the specified mail gid can
be used.
If you are going to be directing virtual domains directly to the
mailman user (using ``virtualdomains'' on a list-only domain, for
example), you will have to use --with-mail-gid=gid of mailman
user's group. This is incompatible with having list aliases in
~alias, unless that alias simply forwards to mailman-listname*.
* If there is a user mailman on your system, the alias mailman-owner
will work only in ~mailman. You have to do a touch .qmail-owner in
~mailman directory to create this alias.
NB: An alternative, IMHO better solution is to chown root ~mailman,
that will stop qmail from considering mailman to be a user to whom
mail can be delivered. (See ``man 8 qmail-getpw''.)
* In a related issue, if you have any users with the same name as one
of your mailing lists, you will have problems if list names contain
"-" in them. Putting .qmail redirections into the user's home
directory doesn't work because the Mailman wrappers will not get
spawned with the proper GID. The solution is to put the following
lines in the /var/qmail/users/assign file:
+zope-:alias:112:11:/var/qmail/alias:-:zope-:
.
where in this case the listname is e.g. zope-users.
NB: Alternatively, you could host the lists on a virtual domain,
and use the /var/qmail/control/virtualdomains file to put the
mailman user in charge of this virtual domain.
* BN:If inbound messages are delivered by another user than mailman,
it's necessary to allow it to access ~mailman. Be sure that
~mailman has group writing access and setgid bit is set. Then put
the delivering user to mailman group, and you can deny access to
~mailman to others. Be sure that you can do the same with the WWW
service.
By the way the best thing is to make a virtual mail server to
handle all of the mail. NB: E.g. make an additional "A" DNS record
for the virtual mailserver pointing to your IP address, add the
line lists.kva.hu:mailman to /var/qmail/control/virtualdomains and
a lists.kva.hu line to /var/qmail/control/rcpthosts file. Don't
forget to HUP the qmail-send after modifying ``virtualdomains''.
Then every mail to lists.kva.hu will arrive to mail.kva.hu's
mailman user.
Then make your aliases:
.qmail => mailman@...'s letters
.qmail-owner => mailman-owner's letters
For list aliases, you can either create them manually:
.qmail-list => posts to the 'list' list
.qmail-list-admin => posts to the 'list's owner
.qmail-list-request => requests to 'list'
etc
or for automatic list alias handling (when using the lists.kva.hu
virtual as above), see contrib/qmail-to-mailman.py in the Mailman
source distribution. Modify the ~mailman/.qmail-default to include:
|preline /path/to/python /path/to/qmail-to-mailman.py
and new lists will automatically be picked up.
* You have to make sure that the localhost can relay. If you start
qmail via inetd and tcpenv, you need some line the following in
your /etc/hosts.allow file:
tcp-env: 127. 10.205.200. : setenv RELAYCLIENT
where 10.205.200. is your IP address block. If you use tcpserver,
then you need something like the following in your /etc/tcp.smtp
file:
10.205.200.:allow,RELAYCLIENT=""
127.:allow,RELAYCLIENT=""
* BN: Bigger /var/qmail/control/concurrencyremote values work better
sending outbound messages, within reason. Unless you know your
system can handle it (many if not most cannot) this should not be
set to a value greater than 120.
* More information about setting up qmail and relaying can be found
in the qmail documentation.
BN: Last but not least, here's a little script to generate aliases to
your lists (if for some reason you can/will not have them automatically
picked up using contrib/qmail-to-mailman.py):
This script is for the Mailman 2.0 series:
#!/bin/sh
if [ $# = 1 ]; then
i=$1
echo Making links to $i in the current directory...
echo "|preline /home/mailman/mail/mailman post $i" > .qmail-$i
echo "|preline /home/mailman/mail/mailman mailowner $i" > .qmail-$i-admin
echo "|preline /home/mailman/mail/mailman mailowner $i" > .qmail-$i-owner
echo "|preline /home/mailman/mail/mailman mailowner $i" > .qmail-owner-$i
echo "|preline /home/mailman/mail/mailman mailcmd $i" > .qmail-$i-request
fi
Note: This is for a new Mailman 2.1 installation. Users upgrading from
Mailman 2.0 would most likely change /usr/local/mailman to
/home/mailman. If in doubt, refer to the --prefix option passed to
configure during compile time.
#!/bin/sh
if [ $# = 1 ]; then
i=$1
echo Making links to $i in the current directory...
echo "|preline /usr/local/mailman/mail/mailman post $i" > .qmail-$i
echo "|preline /usr/local/mailman/mail/mailman admin $i" > .qmail-$i-admin
echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-bounc
es
# The following line is for VERP
# echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-bou
nces-default
echo "|preline /usr/local/mailman/mail/mailman confirm $i" > .qmail-$i-confi
rm
echo "|preline /usr/local/mailman/mail/mailman join $i" > .qmail-$i-join
echo "|preline /usr/local/mailman/mail/mailman leave $i" > .qmail-$i-leave
echo "|preline /usr/local/mailman/mail/mailman owner $i" > .qmail-$i-owner
echo "|preline /usr/local/mailman/mail/mailman request $i" > .qmail-$i-reque
st
echo "|preline /usr/local/mailman/mail/mailman subscribe $i" > .qmail-$i-sub
scribe
echo "|preline /usr/local/mailman/mail/mailman unsubscribe $i" > .qmail-$i-u
nsubscribe
fi
6.4.1 Information on VERP
You will note in the alias generating script for 2.1 above, there is a
line for VERP that has been commented out. If you are interested in
VERP there are two options. The first option is to allow Mailman to do
the VERP formatting. To activate this, uncomment that line and add the
following lines to your mm_cfg.py file:
VERP_FORMAT = '%(bounces)s-+%(mailbox)s=%(host)s'
VERP_REGEXP = r'^(?P<bounces>.*?)-\+(?P<mailbox>[^=]+)=(?P<host>[^@]+)@.*$'
The second option is a patch on SourceForge located at:
http://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&grou
p_id=103
This patch currently needs more testing and might best be suitable for
developers or people well familiar with qmail. Having said that, this
patch is the more qmail-friendly approach resulting in large
performance gains.
6.4.2 Virtual mail server
As mentioned in the 6.4 section for a virtual mail server, a patch
under testing is located at:
http://sf.net/tracker/index.php?func=detail&aid=621257&group_id=103&ati
d=300103
Again, this patch is for people familiar with their qmail installation.
6.4.3 More information
You might be interested in some information on modifying footers that
Norbert Bollow has written about Mailman and qmail, available here:
http://mailman.cis.to/qmail-verh/
7 Review your site defaults
Mailman has a large number of site-wide configuration options which you
should now review and change according to your needs. Some of the
options control how Mailman interacts with your environment, and other
options select defaults for newly created lists^5. There are system
tuning parameters and integration options.
The full set of site-wide defaults lives in the
$prefix/Mailman/Defaults.py file, however you should never modify this
file! Instead, change the mm_cfg.py file in that same directory. You
only need to add values to mm_cfg.py that are different than the
defaults in Defaults.py, and future Mailman upgrades are guaranteed
never to touch your mm_cfg.py file.
The Defaults.py file is documented extensively, so the options are not
described here. The Defaults.py and mm_cfg.py are both Python files so
valid Python syntax must be maintained or your Mailman installation
will break.
You should make any changes to mm_cfg.py using the account you
installed Mailman under in the 3 section.
8 Create a site-wide mailing list
After you have completed the integration of Mailman and your mail
server, you need to create a ``site-wide'' mailing list. This is the
one that password reminders will appear to come from, and it is
required for proper Mailman operation. Usually this should be a list
called mailman, but if you need to change this, be sure to change the
MAILMAN_SITE_LIST variable in mm_cfg.py. You can create the site list
with this command, following the prompts:
% bin/newlist mailman
Now configure your site list. There is a convenient template for a
generic site list in the installation directory, under
data/sitelist.cfg which can help you with this. You should review the
configuration options in the template, but note that any options not
named in the sitelist.cfg file won't be changed.
The template can be applied to your site list by running:
% bin/config_list -i data/sitelist.cfg mailman
After applying the sitelist.cfg options, be sure you review the site
list's configuration via the admin pages.
You should also subscribe yourself to the site list.
9 Set up cron
Several Mailman features occur on a regular schedule, so you must set
up cron to run the right programs at the right time^6.
If your version of crontab supports the -u option, you must be root to
do this next step. Add $prefix/cron/crontab.in as a crontab entry by
executing these commands:
% cd $prefix/cron
% crontab -u mailman crontab.in
If you used the --with-username option, use that user name instead of
mailman for the -u argument value. If your crontab does not support the
-u option, try these commands:
% cd $prefix/cron
% su - mailman
% crontab crontab.in
Warning: If you accepted the defaults for the --with-username option
and for the name of the site list, and one of the cron jobs ever
encounters an error, the cron daemon will mail the error output to the
'mailman' user and it will most likely be delivered to the 'mailman'
site list and possibly not be accepted. For this reason it is a good
idea to insert
MAILTO=user@example.com
or
MAILTO=mailman-owner
at the beginning of crontab.in before installing it to cause this
output to be mailed to a real user or to the owner of the site list or
to configure the site list (see section 8) to accept this mail.
10 Start the Mailman qrunner
Mailman depends on a process called the ``qrunner'' to delivery all
email messages it sees. You must start the qrunner by executing the
following command from the $prefix directory:
% bin/mailmanctl start
You probably want to start Mailman every time you reboot your system.
Exactly how to do this depends on your operating system. If your OS
supports the chkconfig command (e.g. RedHat and Mandrake Linuxes) you
can do the following (as root, from the Mailman install directory):
% cp misc/mailman /etc/init.d/mailman
% chkconfig --add mailman
Note that /etc/init.d may be /etc/rc.d/init.d on some systems.
On Gentoo Linux, you can do the following:
% cp misc/mailman /etc/init.d/mailman
% rc-update add mailman default
On Debian, you probably want to use:
% update-rc.d mailman defaults
For Unixes that don't support chkconfig, you might try the following
set of commands:
% cp misc/mailman /etc/init.d/mailman
% cd /etc/rc.d/rc0.d
% ln -s ../init.d/mailman K12mailman
% cd ../rc1.d
% ln -s ../init.d/mailman K12mailman
% cd ../rc2.d
% ln -s ../init.d/mailman S98mailman
% cd ../rc3.d
% ln -s ../init.d/mailman S98mailman
% cd ../rc4.d
% ln -s ../init.d/mailman S98mailman
% cd ../rc5.d
% ln -s ../init.d/mailman S98mailman
% cd ../rc6.d
% ln -s ../init.d/mailman K12mailman
11 Check the hostname settings
You should check the values for DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST
in Defaults.py. Make any necessary changes in the mm_cfg.py file, not
in the Defaults.py file. If you change either of these two values,
you'll want to add the following afterwards in the mm_cfg.py file:
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
You will want to run the bin/fix_url.py to change the domain of any
existing lists.
12 Create the site password
There are two site-wide passwords that you can create from the command
line, using the bin/mmsitepass script. The first is the ``site
password'' which can be used anywhere a password is required in the
system. The site password will get you into the administration page for
any list, and it can be used to log in as any user. Think root for a
Unix system, so pick this password wisely!
The second password is a site-wide ``list creator'' password. You can
use this to delegate the ability to create new mailing lists without
providing all the privileges of the site password. Of course, the owner
of the site password can also create new mailing lists, but the list
creator password is limited to just that special role.
To set the site password, use this command:
% $prefix/bin/mmsitepass <your-site-password>
To set the list creator password, use this command:
% $prefix/bin/mmsitepass -c <list-creator-password>
It is okay not to set a list creator password, but you probably do want
a site password.
13 Create your first mailing list
For more detailed information about using Mailman, including creating
and configuring mailing lists, see the Mailman List Adminstration
Manual. These instructions provide a quick guide to creating your first
mailing list via the web interface:
* Start by visiting the url http://my.dom.ain/mailman/create.
* Fill out the form as described in the on-screen instructions, and
in the ``List creator's password'' field, type the password you
entered in section 7. Type your own email address for the ``Initial
list owner address'', and select ``Yes'' to notify the list
administrator.
* Click on the ``Create List'' button.
* Check your email for a message from Mailman informing you that your
new mailing list was created.
* Now visit the list's administration page, either by following the
link on the confirmation web page or clicking on the link from the
email Mailman just sent you. Typically the url will be something
like http://my.dom.ain/mailman/admin/mylist.
* Type in the list's password and click on ``Let me in...''
* Click on ``Membership Management'' and then on ``Mass
Subscription''.
* Enter your email address in the big text field, and click on
``Submit Your Changes''.
* Now go to your email and send a message to mylist@my.dom.ain.
Within a minute or two you should see your message reflected back
to you via Mailman.
Congratulations! You've just set up and tested your first Mailman
mailing list. If you had any problems along the way, please see the 14
section.
14 Troubleshooting
If you encounter problems with running Mailman, first check the
question and answer section below. If your problem is not covered
there, check the online help, including the FAQ and the community FAQ
wiki.
Also check for errors in your syslog files, your mail and web server
log files and in Mailman's $prefix/logs/error file. If you're still
having problems, you should send a message to the
mailman-users@python.org mailing list^7; see
http://mail.python.org/mailman/listinfo/mailman-users for more
information.
Be sure to including information on your operating system, which
version of Python you're using, and which version of Mailman you're
installing.
Here is a list of some common questions and answers:
* Problem: All Mailman web pages give a 404 File not found error.
Solution: Your web server has not been set up properly for handling
Mailman's CGI programs. Make sure you have:
1. configured the web server to give permissions to
$prefix/cgi-bin
2. restarted the web server properly.
Consult your web server's documentation for instructions on how to
do check these issues.
* Problem: All Mailman web pages give an "Internal Server Error".
Solution: The likely problem is that you are using the wrong user
or group for the CGI scripts. Check your web server's log files. If
you see a line like
Attempt to exec script with invalid gid 51, expected 99
you will need to reinstall Mailman, specifying the proper CGI group
id, as described in the 3 section.
* Problem: I send mail to the list, and get back mail saying the list
is not found!
Solution: You probably didn't add the necessary aliases to the
system alias database, or you didn't properly integrate Mailman
with your mail server. Perhaps you didn't update the alias
database, or your system requires you to run newaliases explicitly.
Refer to your server specific instructions in the 6 section.
* Problem: I send mail to the list, and get back mail saying,
``unknown mailer error''.
Solution: The likely problem is that you are using the wrong user
or group id for the mail wrappers. Check your mail server's log
files; if you see a line like
Attempt to exec script with invalid gid 51, expected 99
you will need to reinstall Mailman, specifying the proper mail
group id as described in the 3 section.
* Problem: I use Postfix as my mail server and the mail wrapper
programs are logging complaints about the wrong GID.
Solution: Make sure the $prefix/data/aliases.db file is user owned
by mailman (or whatever user name you used in the configure
command). If this file is not user owned by mailman, Postfix will
not run the mail programs as the correct user.
* Problem: I use Sendmail as my mail server, and when I send mail to
the list, I get back mail saying, ``sh: mailman not available for
sendmail programs''.
Solution: Your system uses the Sendmail restricted shell (smrsh).
You need to configure smrsh by creating a symbolic link from the
mail wrapper ($prefix/mail/mailman) to the directory identifying
executables allowed to run under smrsh.
Some common names for this directory are /var/admin/sm.bin,
/usr/admin/sm.bin or /etc/smrsh.
Note that on Debian Linux, the system makes /usr/lib/sm.bin, which
is wrong, you will need to create the directory /usr/admin/sm.bin
and add the link there. Note further any aliases newaliases spits
out will need to be adjusted to point to the secure link to the
wrapper.
* Problem: I messed up when I called configure. How do I clean things
up and re-install?
Solution:
% make clean
% ./configure --with-the-right-options
% make install
15 Platform and operating system notes
Generally, Mailman runs on any POSIX-based system, such as Solaris, the
various BSD variants, Linux systems, MacOSX, and other generic Unix
systems. It doesn't run on Windows. For the most part, the generic
instructions given in this document should be sufficient to get Mailman
working on any supported platform. Some operating systems have
additional recommended installation or configuration instructions.
15.1 GNU/Linux issues
Linux seems to be the most popular platform for running Mailman. Here
are some hints on getting Mailman to run on Linux:
* If you are getting errors with hard link creations and/or you are
using a special secure kernel (securelinux/openwall/grsecurity),
see the file contrib/README.check_perms_grsecurity in the Mailman
source distribution.
Note that if you are using Linux Mandrake in secure mode, you are
probably concerned by this.
* Apparently Mandrake 9.0 changed the permissions on gcc, so if you
build as the mailman user, you need to be sure mailman is in the
cctools group.
* If you installed Python from your Linux distribution's package
manager (e.g. .rpms for Redhat-derived systems or .deb for Debian),
you must install the ``development'' package of Python, or you may
not get everything you need.
For example, using Python 2.2 on Debian, you will need to install
the python2.2-dev package. On Redhat, you probably need the
python2-devel package.
If you install Python from source, you should be fine.
One symptom of this problem, although for unknown reasons, is that
you might get an error such as this during your install:
Traceback (most recent call last):
File "bin/update", line 44, in ?
import paths
ImportError: No module named paths
make: *** [update] Error 1
If this happens, install the Python development package and try
configure and make install again. Or install the latest version of
Python from source, available from http://www.python.org.
This problem can manifest itself in other Linux distributions in
different ways, although usually it appears as ImportErrors.
15.2 BSD issues
Vivek Khera writes that some BSDs do nightly security scans for setuid
file changes. setgid directories also come up on the scan when they
change. Also, the setgid bit is not necessary on BSD systems because
group ownership is automatically inherited on files created in
directories. On other Unixes, this only happens when the directory has
the setgid bit turned on.
To install without turning on the setgid bit on directories, simply
pass in the DIRSETGID variable to make, after you've run configure:
% make DIRSETGID=: install
This disables the chmod g+s command on installed directories.
15.3 MacOSX issues
Much of the following is no longer applicable to more recent versions
of MacOSX. See the FAQ at http://wiki.list.org/x/O4A9 for links to more
recent information.
Many people run Mailman on MacOSX. Here are some pointers that have
been collected on getting Mailman to run on MacOSX.
* Jaguar (MacOSX 10.2) comes with Python 2.2. While this isn't the
very latest stable version of Python, it ought to be sufficient to
run Mailman 2.1.
* David B. O'Donnell has a web page describing his configuration of
Mailman 2.0.13 and Postfix on MacOSX Server.
http://www.afp548.com/Articles/mail/python-mailman.html
* Kathleen Webb posted her experiences in getting Mailman running on
Jaguar using Sendmail.
http://mail.python.org/pipermail/mailman-users/2002-October/022944.
html
* Panther server (MacOSX 10.3) comes with Mailman; Your operating
system should contain documentation that will help you, and Apple
has a tech document about a problem you might encounter running
Mailman on Mac OS X Server 10.3:
http://docs.info.apple.com/article.html?artnum=107889
Terry Allen provides the following detailed instructions on running
Mailman on the 'client' version of OSX, or in earlier versions of OSX:
Mac OSX 10.3 and onwards has the basics for a successful Mailman
installation. Users of earlier versions of Mac OSX contains Sendmail
and those users should look at the Sendmail installation section for
tips. You should follow the basic installation steps as described
earlier in this manual, substituting as appropriate, the steps outlined
in this section.
By default, Mac OSX 10.3 'client' version does not have a fully
functional version of Postfix. Setting up a working MTA such as Postfix
is beyond the scope of this guide and you should refer to
http://www.postfix.org for tips on getting Postfix running. An easy way
to set Postfix up is to install and run Postfix Enabler, a stand-alone
tool for configuring Postfix on Mac OSX, available from
http://www.roadstead.com/weblog/Tutorials/PostfixEnabler.html.
Likewise, Mac OSX 'client' version from 10.1 onwards includes a working
Apache webserver. This is switched on using the System Preferences
control panel under the 'Sharing tab'. A useful tool for configuring
the Apache on Mac OSX is Webmin, which can be obtained from
http://www.webmin.com.
Webmin can also perform configuration for other system tasks, including
Postfix, adding jobs to your crontab, adding user and groups, plus
adding startup and shutdown jobs.
In a stock installation of OSX, the requirement for Mailman is to have
Python installed. Python is not installed by default, so it is advised
that you install the developer's tools package, which may have been
provided with your system. It can also be downloaded from the Apple
developer site at http://connect.apple.com. Not only is the developer
tools package an essential requirement for installing Mailman, but it
will come in handy at a later date should you need other tools. The
developer's tools are also know by the name XCode tools.
As a minimum, the Python version should be 2.2, but 2.3 is recommended.
If you wish to add a user and group using the command line in OSX
instead of via Webmin or another GUI interface, open your terminal
application and follow the commands as indicated below - do not type
the comments following the "#" since they are just notes:
sudo tcsh
niutil -create / /users/mailman
niutil -createprop / /users/mailman name mailman
# Note that xxx is a free user ID number on your system
niutil -createprop / /users/mailman uid xxx
niutil -createprop / /users/mailman home /usr/local/mailman
mkdir -p /usr/local/mailman
niutil -createprop / /users/mailman shell /bin/tcsh
passwd mailman
# To prevent malicious hacking, supply a secure password here
niutil -create / /groups/mailman
niutil -createprop / /groups/mailman name mailman
# Note that xxx is a free group ID number on your system
niutil -createprop / /groups/mailman gid xxx
niutil -createprop / /groups/mailman passwd '*'
niutil -createprop / /groups/mailman users 'mailman'
chown mailman:mailman /usr/local/mailman
cd /usr/local/mailman
chmod a+rx,g+ws .
exit
su mailman
For setting up Apache on OSX to handle Mailman, the steps are almost
identical and the configuration file on a stock Mac OSX Client version
is stored in the nearly standard location of /etc/httpd/httpd.conf.
The AFP548.com site has a time-saving automated startup item creator
for Mailman, which can be found at
http://www.afp548.com/Software/MailmanStartup.tar.gz
To install it, copy it into your /Library/StartupItems directory. As
the root or superuser, from the terminal, enter the following:
gunzip MailmanStartup.tar.gz
tar xvf MailmanStartup.tar
It will create the startup item for you so that when you reboot,
Mailman will start up.
About this document ...
GNU Mailman - Installation Manual, January 11, 2020, Release 2.1
This document was generated using the LaTeX2HTML translator.
LaTeX2HTML is Copyright © 1993, 1994, 1995, 1996, 1997, Nikos Drakos,
Computer Based Learning Unit, University of Leeds, and Copyright ©
1997, 1998, Ross Moore, Mathematics Department, Macquarie University,
Sydney.
The application of LaTeX2HTML to the Python documentation has been
heavily tailored by Fred L. Drake, Jr. Original navigation icons were
contributed by Christopher Petrilli.
__________________________________________________________________
Footnotes
... right^1
You will be able to check and repair your permissions after
installation is complete.
.../usr/local/mailman^2
This is the default for Mailman 2.1. Earlier versions of Mailman
installed everything under /home/mailman by default.
... set^3
BSD users should see the 15.2 section for additional
information.
... only^4
In fact, in later versions of Mailman, this module is explicitly
sabotaged. You have to know what you're doing in order to
re-enable it.
... lists^5
In general, changing the list defaults described in this section
will not affect any already created lists. To make changes after
a list has been created, use the web interface or the command
line scripts, such as bin/withlist and bin/config_list.
... time^6
Note that if you're upgrading from a previous version of
Mailman, you'll want to install the new crontab, but be careful
if you're running multiple Mailman installations on your site!
Changing the crontab could mess with other parallel Mailman
installations.
... list^7
You must subscribe to this mailing list in order to post to it,
but the mailing list's archives are publicly visible.
__________________________________________________________________
Previous Page Up one Level Next Page GNU Mailman - Installation Manual
__________________________________________________________________
Release 2.1, documentation updated on January 11, 2020.
wget 'https://lists2.roe3.org/mdrone/doc/mailman-member-es.pdf'wget 'https://lists2.roe3.org/mdrone/doc/mailman-member-es.txt' #GNU Mailman Manual del Suscriptor de Listas Contents About this
document... About this document...
Previous Page Up one Level Next Page GNU Mailman
Manual del Suscriptor de Listas
__________________________________________________________________
GNU Mailman Manual del Suscriptor de Listas
Terri Oda
terri(en)zone12.com
Release 2.1
11 de enero 2020
Prefacio
Resumen:
Este documento describe el interfaz del suscriptor de listas GNU
Mailman 2.1. Este manual contiene instrucciones para suscripción,
desuscripción, consulta de los archivos de la lista, edición de
opciones de suscriptor, obtención de recordatorios de contraseñas y
otras tareas a nivel del suscriptor. También responde algunas
preguntas comunes de interés para miembros de listas Mailman.
Ãndice General
*
+ 1 Introducción
o 1.1 Reconocimientos
o 1.2 ¿Qué es una lista de correo?
o 1.3 GNU Mailman
+ 2 Pasando de nuestros ejemplos a las listas reales
+ 3 Interfaces de Mailman
o 3.1 El interfaz web
o 3.2 El interfaz de correo electrónico
+ 4 ¡Necesito hablar con un humano!
+ 5 Suscripción y desuscripción
o 5.1 ¿Cómo me uno a la lista? (subscribe)
o 5.2 ¿Cómo dejo la lista? (unsubscribe)
+ 6 Contraseñas
o 6.1 ¿Cómo obtengo mi contraseña?
o 6.2 ¿Cómo cambio mi contraseña?
o 6.3 ¿Cómo activo/desactivo los recordatorios de
contraseñas? (opción reminders)
+ 7 Cambiando la entrega del correo
o 7.1 ¿Cómo activo o desactivo la entrega de correo?
(opción delivery)
o 7.2 ¿Cómo puedo evitar recibir mensajes duplicados?
(opción duplicates)
o 7.3 ¿Cómo cambio mi dirección de suscripción?
o 7.4 ¿Cómo hago para dejar de o iniciar a recibir copias
de mis propios envÃos? (opción myposts)
o 7.5 ¿Cómo puedo hacer para que Mailman me diga cuando
mi envÃo ha sido recibido por la lista? (opción ack)
o 7.6 Parece que no estoy recibiendo correo de las listas.
¿Qué deberÃa hacer?
+ 8 EnvÃos agrupados
o 8.1 ¿Cómo puedo iniciar o dejar de recibir los mensajes
enviados a la lista agrupados en un correo de gran
tamaño? (opción digest)
o 8.2 ¿Qué son los EnvÃos Agrupados MIME o de Texto
Plano? ¿Cómo puedo decidir cuales recibir? (opción
digest)
+ 9 Temas de listas de correo
o 9.1 ¿Cómo puedo asegurarme que mis envÃos tienen el
tema apropiado?
o 9.2 ¿Cómo me suscribo a algunos o a todos los temas de
una lista?
o 9.3 ¿Cómo logro o evito recibir mensajes sin tema
definido?
+ 10 Definiendo otras opciones
o 10.1 ¿Cambiar Globalmente? ¿Definir Globalmente? ¿Qué
significa esto?
o 10.2 ¿Cómo cambio el nombre que registré en Mailman?
o 10.3 ¿Cómo selecciono mi idioma preferido?
o 10.4 ¿Cómo evito que mi nombre aparezca en la lista de
suscriptores? (opción hide)
+ 11 Otras preguntas comunes
o 11.1 ¿Cómo puedo consultar los archivos de la lista?
o 11.2 ¿Qué hace Mailman para ayudar a protegerme de
correo basura no solicitado (spam)?
+ 1 Referencia rápida de órdenes de correo electrónico
+ 2 Referencia rápida de opciones del suscriptor
1 Introducción
Este documento tiene como propósito ayudar a los miembros de una lista
de correo Mailman 2.1 a aprender a usar las caracterÃsticas de este
software, disponibles para ellos. Este cubre el uso de los interfaces
web y de correo electrónico para suscribipción y desuscripción,
cambio de opciones de suscriptor y otras tareas a nivel de suscriptor.
También responde algunas preguntas comunes de interés para miembros
de listas Mailman.
La información para administradores de listas y de sitio se
proporciona en otros documentos.
Este documento se debe leer en orden. Si usted simplemente está
buscando una respuesta a una pregunta especÃfica, consulte la sección
o subsección que necesite, donde encuentrará referencias a otras
secciones, en caso de ser necesario o de potencial utilidad.
Nota: Para los propósitos de este documento, se asume que el lector
está familiarizado con términos comunes relacionados con correo
electrónico (por ejemplo: LÃnea de Asunto, cuerpo del mensaje) y
sitios web (por ejemplo: cuadro de lista desplegable, botón), o los
puede consultar. También se asume que el lector ya puede usar lo
suficientemente bien su programa de correo electrónico y navegador
web, de tal forma que sean claras las instrucciones tales como ``envÃe
correo electrónico a esta dirección'' o ``visite esta página web'' o
``rellene el formulario proporcionado''. Si usted no está
familiarizado con estas acciones, usted puede desear consultar otra
documentación para aprender como hacer estas cosas con su
configuración particular.
1.1 Reconocimientos
Varias secciones de este documento se tomaron del Manual de
Administrador de Listas del CVS de Mailman, escritas por Barry A.
Warsaw, y también de la ayuda integrada de Mailman 2.1.
El resto de este manual fue escrito por Terri Oda. Terri ha estado
manteniendo listas de correo desde el año que ella alcanzó la edad
para votar en Canada, aunque las dos cosas no están relacionadas. Ella
actualmente administra las listas de correo de Linuxchix.org, asà como
tambien varios servidores más pequeños. En el mundo ajeno a la
administración de listas, Terri está haciendo un trabajo con un
detector de spam de vida artificial, y realmente es más una
programadora que una escritora de temas técnicos.
Gracias a Margaret McCarthy, Jason Walton y Barry Warsaw por su ayuda
en la revisión y mejoramiento de este manual.
Gracias también a Ikeda Soji, quien hizo una traducción Japonesa de
este documento.
1.2 ¿Qué es una lista de correo?
Una lista de correo es simplemente una lista de direcciones a las
cuales se envÃa la misma información. Si usted fuera un editor de una
revista, usted tendrÃa una lista de direcciones de correo postal de
todos los suscriptores de la revista. En el caso de las listas de
correo electrónico, se usa una una lista de direcciones de correo
electrónico de gente interesada en escuchar o discutir acerca de un
tema dado.
Dos tipos comunes de listas de correo electrónico son las listas de
anuncios y las listas de discusión.
Las listas de anuncios sirven para que una o más personas puedan
enviar anuncios a un grupo de personas, en forma similar a la manera
cómo hace un editor de una revista que utiliza su lista de direcciones
postales para enviar las revistas. Por ejemplo, una banda musical
podrÃa usar una lista de anuncios para facilitar que sus seguidores
estén al tanto de sus conciertos futuros.
Una lista de discusión permite a un grupo de personas discutir
temáticas entre ellos mismos, pudiendo cada uno enviar correo a la
lista y hacer que se distribuya a todos los integrantes del grupo. Esta
discusión también se puede moderar, de tal manera que sólo los
mensajes seleccionados se envien al grupo como un todo, o que
únicamente se le permita enviar al grupo a ciertas personas. Por
ejemplo, un grupo de entusiastas de modelos de aviones podrÃan usar una
lista de discusión para compartir consejos útiles sobre la
construcción de modelos y aviación.
Algunos términos comunes:
* Un ``envÃo'' tÃpicamente denota un mensaje que se envÃa a una lista
de correo. (Piense en poner un mensaje en un tablero de anuncios.)
* A las personas que son parte de una lista de correo electrónico
normalmente se las llama ``miembros'' de la lista o
``suscriptores.''
* ``Los administradores de las listas'' son personas encargadas de,
precisamente, mantener esas listas. Las listas pueden tener uno o
más administradores.
* Una lista puede tener también personas encargadas de leer los
mensajes enviados a la lista y decidir si ellos deberÃan ser
enviados a todos los suscriptores. A estas personas se las llama
moderadores de las listas.
* A menudo varias listas de correo electrónico utilizan el mismo
software. A la persona que mantiene el software gracias al cual
funcionan las listas se le llama el ``administrador del sitio.'' A
menudo el administrador del sitio también administra listas
individuales.
1.3 GNU Mailman
GNU Mailman es software que le permite administrar listas de correo
electrónico, con soporte para un rango amplio de tipos de listas de
correo, tales como listas de discusión general y listas de sólo
anuncios. Mailman tiene caracterÃsticas extensivas que lo hacen bueno
para listas de suscriptores, tales como facilidad en la suscripción y
desuscripción, opciones de privacidad, y la capacidad de detener
temporalmente la recepción de los envÃos a la lista. En este documento
se incluye sobre las caracterÃsticas de los miembros de las listas.
Mailman también tiene muchas caracterÃsticas que lo hacen atractivo a
administradores de listas y administradores de sitio. Estas
caracterÃsticas están cubiertas en los manuales del administrador de
listas y del sitio.
2 Pasando de nuestros ejemplos a las listas reales
A menudo es más fácil, simplemente dar un ejemplo que explicar
exactamente como encontrar la dirección de una lista especÃfica. Por
ello, aquà frecuentemente se darán ejemplos para una lista ficticia
llamada NOMBRELISTA@DOMINIO cuya página de información se puede
encontrar en http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA.
Ninguna de estas direcciones es real, pero muestran la forma tÃpica de
las direcciones de las listas. Las letras máyusculas utilizadas para
las partes especÃficas a las listas de cada dirección deberÃa hacerlo
más fácil para mirar lo que se deberÃa cambiar para cada lista.
Aunque las configuraciones especÃficas para las listas pueden ser
diferentes, usted probablemente podrá simplemente reemplazar las
palabras dadas en letras mayúsculas con los valores apropiados para
una lista real:
NOMBRELISTA
El nombre de su lista.
DOMINIO
El nombre del servidor de correo que gestiona la lista.
SERVIDORWEB
El nombre del servidor web que gestiona el interfaz web de la
lista. Este puede ser el mismo utilizado como DOMINIO, y a
menudo se refiere a la misma máquina, pero no tiene que ser
idéntico.
Como ejemplo de la vida real, si usted está interesado en la lista de
usuarios mailman (mailman-users), usted realizarÃa las siguientes
sustituciones: NOMBRELISTA=mailman-users, DOMINIO=python.org,
SERVIDORWEB=mail.python.org. De esta forma, para la lista de correo
mailman-users@python.org, la página de información de esa lista se
encontrarÃa en la dirección URL
http://mail.python.org/mailman/listinfo/mailman-users (estas, a
diferencia de la mayorÃa de ejemplos datos en este documento, son
direcciones reales).
La mayorÃa de las listas tendrán esta información almacenada en las
cabeceras List-*:. Muchos programs de correo ocultarán estas cabeceras
por omisión, asà que usted tiene que seleccionar mirar todas las
cabeceras antes que pueda mirar estas cabeceras informativas.
3 Interfaces de Mailman
Mailman tiene dos interfaces diferentes para los suscriptores de las
listas: la interfaz web y la interfaz de correo electrónico. La
mayorÃa de suscriptores de las listas de discusión usan el interfaz de
correo electrónico, ya que ésta incluye las direcciones de correo
electrónico que usted utiliza para enviar correo a todos los
suscriptores de esa lista.
La interfaz que usted use para cambiar las opciones es cuestión de
preferencia, ya que la mayorÃa de (pero no todas) las opciones que se
pueden cambiar utilizando la interfaz web también se pueden cambiar
por correo electrónico. Usualmente es más fácil utilizar la interfaz
web para cambiar opciones, ya que la interfaz web proporciona
instrucciones como parte de las mismas páginas, pero hay ocasiones en
las cuales las personas prefieren la interfaz de correo electrónico,
asà que las dos se proporcionan y son útiles.
3.1 El interfaz web
Para mucha gente, el interfaz web de Mailman es su punto más
destacable ya que lo hace mucho más fácil para suscriptores y
administradores mirar que opciones están disponibles y lo que hacen
estas opciones.
Cada lista de correo también está accesible desde un número de
páginas web. Note que las direcciones URL exactas son configurables
por el administrador del sitio, asà que ellas pueden ser diferentes a
las que se describen abajo. Nosotros describiremos la configuración
más común, pero consulte los detalles con su administrador de sitio o
proveedor del servicio.
Página de información de la lista (listinfo)
+ Usualmente se encuentra en http://SERVIDORWEB/mailman
/listinfo/NOMBRELISTA (por ejemplo,
http://listas.ejemplo.com/mailman/listinfo/milista).
+ La página listinfo es el punto de inicio del interfaz del
suscriptor. Como uno podrÃa asumir por el nombre dado, ésta
contiene información acerca de la lista NOMBRELISTA.
Usualmente todas las otras páginas del suscriptor se pueden
acceder desde este punto, asà que realmente usted sólo
necesita conocer esta dirección.
Página de opciones del suscriptor
+ Usualmente se encuentra en http://SERVIDOR/mailman/options
/NOMBRELISTA/DIRECCIONCORREO (por ejemplo,
http://listas.ejemplo.com/mailman/options/milista
/maria@aqui.com).
+ También se puede acceder a esta página yendo a la página
listinfo y entrando su dirección de correo en el cuadro de
texto junto al botón marcado ``Opciones de Edición y
Desuscripción'' (este está cerca del final de la página).
+ La página de opciones de suscriptor le permite a usted
entrar/salir y cambiar la configuración de sus opciones, asÃ
como también desuscribirse u obtener una copia de su
contraseña por correo electrónico.
+ Para ingresar en su página de opciones de suscriptor: Si
usted aún no ha ingresado, encontrará un cuadro de texto
cerca a la parte superior de la página para introducir su
contraseña (si usted no conoce su contraseña, mire la
seccion 6.1 para más información sobre cómo obtener su
contraseña). Entre su contraseña en el cuadro de texto
mencionado y haga clic en el botón ``Cambiar''.
+ Una vez usted esté adentro, podrá mirar y cambiar toda la
configuración personal de su lista.
Archivos de la Lista
+ Usualmente los encontrará en
http://SERVIDORWEB/pipermail/NOMBRELISTA si la lista se
archiva públicamente, y
http://SERVIDORWEB/mailman/private/NOMBRELISTA si la lista se
archiva en forma privada (por ejemplo,
http://listas.ejemplo.com/pipermail/milista o
http://listas.ejemplo.com/mailman/private/milista).
+ Las páginas de los archivos de la lista disponen de una copia
de los mensajes enviados a la lista de correo, usualmente
agrupados por mes. En cada grupo mensual, los envÃos se
indexan por autor, fecha, hilo, y asunto.
+ Nota: Pipermail es el nombre del archivador predeterminado que
viene con Mailman. Otros programas de archivado están
disponibles.
+ Si el archivo es privado, usted necesitará suministrar su
dirección de correo de suscriptor y su contraseña para
ingresar (mire la Sección 6.1 para mayor información sobre
la obtención de su contraseña).
3.2 El interfaz de correo electrónico
Toda lista de correo tiene un conjunto de direcciones de correo
electrónico a las cuales se pueden enviar los mensajes. Siempre hay
una dirección para enviar los mensajes a la lista, una dirección a a
la cual se envÃan los mensajes devueltos y direcciones para procesar
órdenes de correo. Para una lista de correo ficticia llamada
milista@ejemplo.com, usted encontrarÃa estas direcciones:
* milista@ejemplo.com - esta es la dirección de correo que la gente
deberÃa usar para los nuevos envÃos a la lista.
* milista-join@ejemplo.com - enviando un mensaje a esta dirección,
un nuevo miembro puede solicitar suscripción a la lista. Tanto la
cabecera de Asunto: como el cuerpo de tal mensaje son ignorados.
Note que milista-subscribe@ejemplo.com es un alias para la
dirección -join.
* milista-leave@ejemplo.com - enviando un mensaje a esta dirección
un miembro puede solicitar desuscripción de la lista. Igual que
con la dirección -join, la cabecera Asunto: y el cuerpo del
mensaje son ignorados. Note que milista-unsubscribe@ejemplo.com es
un alias para la dirección -leave.
* milista-owner@ejemplo.com - Con esta dirección se llega
directamente al propietario y moderador de la lista. Esta es la
dirección que usted usa si necesita contactar a la persona o
personas encargadas de la lista.
* milista-request@ejemplo.com - Esta dirección alcanza un robot de
correo que procesa órdenes de correo electrónico que se pueden
usar para definir opciones de suscripción de los miembros, asÃ
como también para procesar otros comandos. En el Apéndice A se
proporciona una lista de órdenes de correo electrónico de
miembros de listas.
* milista-bounces@ejemplo.com - Esta dirección se usa para
procesamiento automático de mensajes devueltos de Mailman.
* milista-confirm@ejemplo.com - Esta dirección se usa para procesar
mensajes de confirmación de solicitudes de suscripción y
desuscripción.
También hay una dirección -admin con la cual también se llega a los
administradores de listas, pero esta dirección solamente existe por
compatibilidad con las versiones más antigüas de Mailman.
Para cambiar las opciones, se usa la dirección NOMBRELISTA-request
(por ejemplo, milista-request@ejemplo.com).
Las órdenes pueden aparecer en la lÃnea de asunto o en el cuerpo del
mensaje. Cada comando deberÃa ir en una lÃnea separada. Si su programa
de correo adiciona automáticamente una firma a sus mensajes, usted
podrÃa desear colocar la palabra ``end'' (sin las comillas) en una
lÃnea separada después de sus otras órdenes. La orden end le dice a
Mailman que no procese el correo electrónico después de ese punto.
La órden más importante es probablemente la orden ``help'', ya que
ésta hace que Mailman devuelva un mensaje completo de información
útil sobre las órdenes de correo y direcciones para uso del interfaz
web.
En los Apéndices A y B se proporcionan referencias rápidas a las
órdenes de suscriptor (éstas se han adaptado ligeramente de la salida
de la orden help.)
4 ¡Necesito hablar con un humano!
Si usted tiene problemas con cualquiera de estas órdenes, usted
siempre puede contactar a la persona o personas encargadas de las
listas utilizando las direcciones administrativas de las listas. Los
administradores de las listas pueden ayudar a resolver como hacer algo,
suscribirlo/desuscribirlo, o cambiar su configuración si usted no
puede cambiarla por alguna razón. Por favor recuerde que muchos
administradores de listas de correo son voluntarios quienes están
donando su tiempo libre para administrar la lista y ellos pueden ser
gente muy ocupada.
La dirección de correo del administrador de una lista tiene la forma
NOMBRELISTA-owner@DOMINIO, donde NOMBRELISTA es el nombre de la lista
(por ejemplo: usuarios-mailman) y DOMINIO es el nombre del servidor
(por ejemplo: python.org). Esta dirección de correo, junto con las
direcciones de correo electrónico de administradores especÃficos,
están dadas en la parte inferior de las páginas de información de
cada lista. Mire en la Sección 3.1 mayor información sobre cómo
encontrar la página de información de su lista.
5 Suscripción y desuscripción
Dado que suscribirse (unirse) o desuscribirse (salirse) son a menudo
las únicas cosas que un miembro de lista necesita conocer, con Mailman
éstas se pueden hacer opcionalmente sin necesidad de que usted conozca
una contraseña.
5.1 ¿Cómo me uno a la lista? (subscribe)
Hay dos formas comunes para que usted se suscriba a una lista de correo
Mailman.
Usando el interfaz web:
1. Vaya a la página de información de la lista a la cual usted desea
suscribirse (esta será probablemente similar a
http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA).
2. Mire la sección identificada como ``Suscribirse a NOMBRELISTA'' y
rellene en los cuadros de texto. Usted puede introducir lo
siguiente:
+ Usted debe entrar su dirección de correo electrónico.
+ Usted puede suministrar su nombre real.
+ Usted puede seleccionar una contraseña. Si no selecciona una,
Mailman generará una para usted.
Advertencia: NO use una contraseña valiosa, ya que
eventualmente esta contraseña se enviará por correo
electrónico como texto plano.
+ Si la lista soporta más de un idioma, usted puede seleccionar
su idioma preferido. Nota: Este cambio no afecta los envÃos a
la lista, solamente a los textos Mailman que vienen con el
software de la listas, tal como su página de opciones de
suscriptor.
3. Haga clic en el botón subscribe. Una nueva página deberÃa
aparecer diciéndole que se ha recibido su solicitud de
suscripción. Esta página le proporcionará instrucciones
adicionales, tales como la necesidad de esperar y responder a un
mensaje de confirmación, dependiendo de las polÃticas de
suscripción de la lista.
Usando el interfaz de correo electrónico:
1. Abra un programa de correo que le permita enviar correo desde la
dirección que usted desea suscribir.
2. EnvÃe un correo a la dirección de suscripción de la lista, la
cual estará en la forma NOMBRELISTA-join@DOMINIO. El asunto y
cuerpo del mensaje se ignorarán, asà que no importa lo que usted
coloque ahÃ.
Después de seguir uno de los dos procedimientos (¡usted no necesita
llevar a cabo los dos!), hay unos pocas posibilidades dependiendo de la
configuración de la lista:
* Usted puede recibir un mensaje de correo de confirmación que usted
realmente desea suscribirse a la lista. Esto es para prevenir que
cualquier otra persona lo suscriba a la lista sin su permiso. Siga
las instrucciones dadas en el mensaje para confirmar su deseo de
estar suscrito.
* Un moderador también puede necesitar confirmar su suscripción si
usted se está suscribiendo a una lista cerrada.
* O usted puede tener que esperar a un moderador y seguir las
instrucciones en el correo de confirmación.
Una vez hecho esto, usted muy probablemente recibirá otro mensaje,
dándole la bienvenida a la lista. Este mensaje contiene información
útil, incluyendo su contraseña de la lista y algunos enlaces directos
para el cambio de sus opciones, de manera que usted puede desear
guardarlo para referencia posterior.
Nota: La suscripción también se puede realizar de otras maneras. Mire
en el Apéndice A las órdenes de suscripción por correo electrónico
más avanzadas.
5.2 ¿Cómo dejo la lista? (unsubscribe)
¿Ya no desea estar en una lista? Si usted sólo va a salir de
vacaciones o está demasiado ocupado para leer correos y desea
suspender temporalmente la recepción de esos mensajes, usted puede
desear detener la entrega de correo en lugar de desuscribirse. Esto
significa que usted mantendrá su contraseña y configuración personal
de manera que usted pueda aún, por ejemplo, aún tener acceso a los
archivos privados de la lista. Si esto es lo que usted desea, mire en
la Sección 7.1 las instrucciones para inhabilitar temporalmente la
entrega de correo.
Si usted realmente desea dejar la lista, hay dos formas para que usted
se desuscriba de una lista de correo Mailman.
Usando el interfaz web:
1. Vaya a la página de información de la lista que usted desea dejar
(la dirección de esa página probablemente será similar a
http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA).
2. Ubique la sección identificada como ``suscriptores de
NOMBRELISTA'' (usualmente se encuentra cerca de la parte inferior
de la página).
3. DeberÃa haber un botón etiquetado ``Desuscribirse o Editar
Opciones.'' Introduzca su dirección de correo electrónico en el
cuadro de texto que se encuentra junto a ese botón y haga clic en
el.
4. Usted deberÃa observar en pantalla una nueva página con un botón
de ``Desuscribir''. Haga clic en él para desuscribirse y siga las
instrucciones dadas.
Usando el interfaz de correo electrónico:
1. Abra un programa de correo que le permita enviar correo desde la
dirección que usted desee desuscribir.
2. EnvÃe un correo a la dirección de desuscripción de la lista, la
cual tendrá la forma NOMBRELISTA-leave@DOMINIO. El asunto y cuerpo
del mensaje serán ignorados, asà que no importa lo que usted
coloque ahÃ.
Después de seguir alguno de estos procedimientos (¡usted no
necesitará llevar a cabo los dos!), a usted se le enviará un correo
de confirmación, siendo necesario que usted siga las instrucciones
dadas en ese correo para completar la desuscripción. Esto es neceario
para evitar que otras personas lo desuscriban sin su permiso. En
adición, un moderador puede necesitar aprobar su desuscripción (son
poco comunes las desuscripciones aprobadas por un administrador).
Si usted no recibe ese correo de confirmación con las instrucciones
incluidas, asegúrese de haber escrito correctamente la dirección de
correo electrónico (si usted está usando el interfaz web para
desuscribirse) y que la dirección que usted trató de dar de baja,
está de hecho, realmente suscrita a la lista. Por razones de
seguridad, Mailman genera la misma página de opciones de suscriptor
independientemente de si la dirección entrada está o no suscrita.
Esto significa que la gente no puede usar esta parte del interfaz web
para averiguar si alguien está suscrito a la lista, pero también
significa que es difÃcil decir si usted solamente cometió un error al
teclear.
Una vez que se haya procesado su desuscripción, usted probablemente
recibirá otro mensaje confirmando su desuscripción de la lista, y en
ese punto usted deberÃa dejar de recibir mensajes.
Si usted desea saltarse el proceso de confirmación (por ejemplo,
podrÃa estar desuscribiendo una dirección que ya no trabaja), es
posible omitirlo utilizando su contraseña en su lugar, ya sea,
ingresando a su página de opciones usando su contraseña (ver
Sección 3.1), o enviar la contraseña con sus órdenes de correo a
NOMBRELISTA-request (mire en el Apéndice A las órdenes avanzadas de
suscripción por correo electrónico). Mire en la Sección 6.1 más
información sobre obtención de su contraseña.
6 Contraseñas
Cuando usted se suscribió, usted seleccionó su contraseña o Mailman
se la generó. Usted probablemente tiene una copia de ella en el
mensaje de bienvenida que se le envÃo a usted cuando se unió a la
lista, y puede también recibir un recordatorio de ella cada mes. Esta
se usa para verificar su identidad ante Mailman, de manera que sólo
quien tenga la contraseña (¡usted!) y los administradores puedan
mirar y cambiar su configuración.
Advertencia: No use contraseñas valiosas con Mailman, ya que éstas
eventualmente se envÃan en formato de texto plano.
6.1 ¿Cómo obtengo mi contraseña?
Si usted ha olvidado su contraseña y no ha grabado el mensaje de
bienvenida o cualquier mensaje recordatorio, usted siempre puede
obtener un recordatorio a través del interfaz web:
1. Vaya a la página de información de la lista de la cual usted
desea obtener su contraseña (esta probablemente será similar a
http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA).
2. Ubique la sección identificada como ``Suscriptores de
NOMBRELISTA'' (esta sección usualmente se encuentra cerca de la
parte inferior de la página).
3. DeberÃa haber un botón etiquetado ``Desuscribir o Editar
Opciones.'' Introduzca su dirección de correo electrónico en el
cuadro de texto que se encuentra junto a ese botón y haga clic en
él.
4. Usted deberÃa observar en pantalla una nueva página que tiene una
sección identificada como ``Recordatorio de Contraseña''. Haga
clic en el botón ``Recordar'' para hacer que se le envÃe su
contraseña por correo electrónico.
Si usted no recibe el recordatorio de contraseña por correo
electrónico después de hacer esto, asegúrese de haber escrito
correctamente su dirección de correo electrónico y que la dirección
que utilizó está, efectivamente, realmente suscrita a la lista. Por
razones de seguridad, Mailman genera la misma página de opciones de
suscriptor independientemente de si la dirección entrada está o no
suscrita. Esto significa que la gente no puede usar esta parte del
interfaz web para averiguar si alguien está suscrito a la lista, pero
también significa que es difÃcil decir si usted solamente cometió un
error al teclear.
Usted también puede obtener un recordatorio utilizando el interfaz de
correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden password
Los comandos pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 mayor información
sobre envÃo de órdenes de correo).
Si usted no está enviando correo desde la dirección suscrita,
también puede especificar esta dirección enviando la orden
password address= $<$ DIRECCIÃN $>$ .
6.2 ¿Cómo cambio mi contraseña?
Advertencia: NO use una contraseña valiosa, ya que esta contraseña se
puede enviar por correo como texto plano.
Desde el interfaz web:
1. Ingrese a su página de opciones de suscriptor (Mire en la
Section 3.1 las instrucciones de cómo hacer esto).
2. Ubique los cuadros de texto de cambio de contraseña en el lado
derecho de la página e introduzca allà su nueva contraseña, luego
haga clic en el botón etiquetado ``Cambiar mi contraseña''.
Esto también se puede cambiar para múltiples listas al mismo tiempo
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 la información sobre cambios globales de
configuración.
Desde el interfaz de correo electrónico:
1. EnvÃe un correo a la dirección de correo
NOMBRELISTA-request@DOMINIO con la orden password $<$
CONTRASEÃA - ANTERIOR $>$ $<$ CONTRASEÃA - NUEVA $>$ .
Las órdenes pueden aparecer ya sea en cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 la información sobre
el envÃo de órdenes de correo).
Si usted no está enviando correo desde su dirección de membresÃa,
usted puede también especificar esta dirección con address= $<$
DIRECCIÃN $>$ después de $<$ CONTRASEÃA-NUEVA $>$ .
Por ejemplo, si maria@micasa.com deseaba cambiar su contraseña de
la lista milista, de zirc a miko, pero ella estaba enviando correo
desde la dirección de la oficina maria@trabajo.com, podrÃa enviar
un mensaje a milista-request@ejemplo.com con la lÃnea de asunto
password zirc miko address=maria@micasa.com.
6.3 ¿Cómo activo/desactivo los recordatorios de contraseñas? (opción
reminders)
Si usted no desea recibir recordatorios de contraseña cada mes, puede
desactivarlos desde la página de opciones del suscriptor (usted
siempre puede conseguir que se le envÃe la contraseña por correo
cuando realmente lo desee. Mire las instrucciones en la Sección 6.1).
Usando el interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 las instrucciones de cómo hacer esto).
2. Ubique la sección identificada como ``Obtener recordatorio de
contraseña para esta lista'' y cambie el valor en forma apropiada.
Esto también se puede cambiar para múltiples listas al mismo tiempo
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 la información sobre cambios globales de
configuración.
Usando el interfaz de correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set reminders on o set reminders off.
Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje. Mire en la Sección 3.2 la información sobre
el envÃo de órdenes de correo.
2. Seleccione ``on'' para recibir recordatorios y ``off'' para dejar
de recibir los recordatorios.
7 Cambiando la entrega del correo
7.1 ¿Cómo activo o desactivo la entrega de correo? (opción delivery)
Usted puede desear dejar de recibir temporalmente los mensajes de la
lista sin necesidad de darse de baja. Si usted desactiva la entrega de
correo, ya no podrá recibir mensajes, pero aún será un suscriptor y
como tal retendrá su contraseña y su configuración.
Esto puede ser práctico en muchos casos diferentes. Por ejemplo, usted
podrÃa salir de vacaciones o necesitar un descanso de la lista porque
está demasiado ocupado para leer cualquier correo extra.
También, muchas listas de correo únicamente permiten a los
suscriptores enviar mensajes a la lista, asà que si usted comunmente
envÃa correo desde más de una dirección (por ejemplo, una dirección
para la casa y otra para cuando está viajando), podrÃa tener más de
una cuenta suscrita, pero hacer que solamente una de ellas realmente
reciba correo.
Usted también puede usar su suscripción como un medio para leer
archivos privados, inclusive en una lista que pueda ser demasiado
ocupada para que usted haga enviar los mensajes directamente a su
buzón de correo. Todo lo que necesita hacer es suscribirse, desactivar
la entrega de correo, y usar su contraseña y dirección de correo
electrónico para acceder a los archivos.
Para desactivar/activar la entrega de correo usando el interfaz web:
1. Ingrese a su página de opciones (mire las instrucciones en la
Sección 3.1).
2. Ubique la sección identificada como ``Entrega de correo'' y
seleccione ``Desactivar'' para detener la recepción de correo, y
``Activar'' para iniciar a recibir el correo.
Esto también se puede cambiar para múltiples listas al mismo tiempo,
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 la información acerca de cambios globales de
configuración.
Para activar/desactivar la entrega de correo usando el interfaz de
correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set delivery off o set delivery on.
Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 más información sobre
envÃo de órdenes de correo).
2. Seleccione ``off'' para parar la recepción de los envÃos, y ``on''
para iniciar a recibirlos otra vez.
7.2 ¿Cómo puedo evitar recibir mensajes duplicados? (opción duplicates)
Mailman no puede impedir completamente que usted reciba mensajes
duplicados, pero puede ayudar. Una razón común para que la gente
reciba múltiples copias de un correo es que el remitente haya usado
una función ``responder al grupo'' para enviar correo tanto a la lista
como a algún número de individuos. Si usted desea evitar recibir
estos mensajes, se puede configurar Mailman para que revise y mire si
usted está en las lÃneas To: o Cc: del mensaje. Si su dirección
aparece ahÃ, entonces se le puede indicar a Mailman que no le envÃe
otra copia. Esto significa que usted recibirá solamente la copia
enviada por el remitente, y no una copia que haya sido alterada por
Mailman (incluir cabeceras y piés, borrar adjuntos, etc.).
Para activar/desactivar esta opción usando el interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 los detalles de cómo hacer esto).
2. Ubique en la parte inferior de la página la sección identificada
como ``¿Evitar copias de mensajes duplicados?'' y cambie el valor
según corresponda.
Esto también se puede cambiar para múltiples listas al mismo tiempo
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 la información sobre cambios globales de
configuración.
Para activar/desactivar esto usando el interfaz de correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set duplicates on o set duplicates off.
Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 más información sobre
envÃo de órdenes de correo).
2. Seleccione ``on'' para recibir copias de los mensajes que ya le
hayan enviado, seleccione ``off'' para evitar recibir esos
duplicados.
7.3 ¿Cómo cambio mi dirección de suscripción?
Para cambiar su dirección de suscripción:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 más detalles de cómo hacer esto).
2. Introduzca su nueva dirección en la sección identificada como
``Cambiando su información de membresÃa de NOMBRELISTA''.
3. Si usted desea cambiar su dirección para todas sus suscripciones
usando la dirección antigüa, habilite la opción ``Cambiar
globalmente''. Si uste tiene suscripciones desde otras direcciones
o suscripciones a listas en un dominio diferente, estas tendrán
que hacerse por separado. Mire en la Sección 10.1 más
información sobre cambios globales de configuración.
Mailman le enviará un mensaje de confirmación a su nueva dirección,
pero el cambio no tendrá efecto hasta que usted confirme el cambio
siguiendo las instrucciones dadas en ese mensaje.
No hay una forma especial de hacer esto desde el interfaz de correo
electrónico, pero usted puede suscribirse y desuscribirse para
conseguir más o menos el mismo efecto (mire en las Secciones 5.1 y 5.2
más información sobre suscripción y desuscripción).
7.4 ¿Cómo hago para dejar de o iniciar a recibir copias de mis propios envÃos?
(opción myposts)
Por omisión en Mailman, usted recibe una copia de todos los mensajes
que usted envÃa a la lista. A algunas personas les gusta esto ya que
les permite saber que el envÃo ha alcanzado su destino y asà ellas
tienen una copia de sus propias palabras con el resto de una
discusión, pero otros no desean molestarse recibiendo copias de sus
propios envÃos.
Nota: Esta opción no tiene efecto si usted está recibiendo mensajes
agrupados
Usted también puede desear mirar la Sección 7.5, la cual discute
sobre los correos electrónicos de acuso de recibo de los mensajes que
se envÃan a la lista.
Para hacer esto usando el interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 las instrucciones de cómo hacer esto).
2. Ubique la sección identificada como ``¿Recibir sus propios envÃos
a la lista?'', seleccione ``Si'' para recibir copias de sus propios
mensajes, y ``No'' para evitar recibirlos.
Para hacer esto usando el interfaz de correo:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set myposts on o set myposts off. Las órdenes pueden aparecer ya
sea en el cuerpo o en la lÃnea de asunto del mensaje. Mire en la
Sección 3.2 más información sobre el envÃo de órdenes de
correo.
2. Seleccione ``on'' para recibir copias de sus propios mensajes, y
``off'' para evitar recibirlos.
7.5 ¿Cómo puedo hacer para que Mailman me diga cuando mi envÃo ha sido
recibido por la lista? (opción ack)
En la mayorÃa de las listas, usted simplemente recibirá una copia de
su correo cuando éste se haya ido, no obstante, esta opción puede ser
útil para usted, si esta opción está desactivada (ver Section 7.4),
su entrega de correo está desactivada (ver Section 7.1), usted no
está suscrito a ese tema (ver Section 9.2) o usted simplemente desea
una confirmación de mensaje recibido extra del sistema.
Nota: Si usted no está suscrito a la lista, no se puede usar esta
opción. Usted debe, ya sea, revisar los archivos por su cuenta (si la
lista tiene archivos públicos), preguntarle a alguien que esté
suscrito a la lista, o suscribirse para usar esta opción.
Para utilizar esta opción usando el interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 mayores detalles de cómo hacer esto).
2. Ubique la sección identficada como ``¿Recibir correos de acuso de
rebibo cuando usted envÃa correo a la lista?'' Seleccione ``Si''
para recibir un correo haciéndole saber que se ha recibido su
envÃo y ``No'' para evitar recibir tal mensaje de acuso de recibo.
Para utilizar esta opción usando el interfaz de correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set ack on o set ack off.
Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje. Mire en la Sección 3.2 más información sobre
el envÃo de órdenes de correo.
2. Seleccione ``on'' si usted desea recibir correo haciéndole saber
que se ha recibido su envÃo y ``off'' para evitar recibir tal
mensaje de acuso de recibo.
7.6 Parece que no estoy recibiendo correo de las listas. ¿Qué deberÃa hacer?
Hay pocas razones comunes para que esto ocurra:
* Durante un cierto lapso de tiempo nadie ha enviado correo a la
lista o listas en las cuales usted está suscrito.
Para revisar si este es el caso, intente accediendo a los archivos
de la lista (asumiendo que la lista tiene archivos). Si la lista no
tiene archivos, puede preguntar a otro suscriptor (mire en la
Sección 3.1 la ayuda para encontrar los archivos de una lista).
Nota: Generalmente se considera descortés envÃar mensajes de
prueba a la lista entera. Si usted siente la necesidad de probar
que la lista está trabajando y por alguna razón usted no puede
simplemente redactar un mensaje regular a la lista, es menos
perturbador solicitar un mensaje de ayuda a la dirección
administrativa de la lista (NOMBRELISTA-request@DOMINIO) para mirar
si trabaja, o contactar al administrador de la lista para
preguntarle si la lista está operando normalmente.
* Su dirección de correo está causando mensajes devueltos y por
ello el software de la lista le ha deshabilitado la entrega de
correo (temporalmente).
Si su proveedor de correo ``devuelve'' demasiados mensajes (es
decir, si le dice a Mailman que el mensaje no se pudo enviar),
Mailman eventualmente ya no intenta enviarle correo. Esta
caracterÃstica permite a Mailman manipular con gusto direcciones
que ya no existen (por ejemplo, cuando un suscriptor encuentra un
nuevo servicio de Internet y olvida darse de baja de la dirección
antigüa), asà como también direcciones que están temporalmente
fuera de servicio (por ejemplo, cuando el suscriptor ha utilizado
todo el espacio asignado de su cuenta de correo, o cuando el
proveedor de correo del suscriptor está experimentando
dificultades).
Aún si usted no está enterado de cualquier dificultad con su
proveedor de correo, es una buena idea revisar esto. Algunos
proveedores populares de correo basado en web y servidores de
Internet no son tan confiables como uno podrÃa asumir, ni tampoco
lo es el Internet como un todo. Usted también puede desear
enviarse usted mismo un mensaje de prueba desde otra cuenta o
pedirle a un amigo que le envÃe un mensaje de prueba para
asegurarse que su dirección suscrita está trabajando.
Para revisar si esta puede ser la razón por la cual usted no está
recibiendo mensajes, ingrese a su página de opciones (consulte en
la Sección 3.1 más detalles de cómo hacer esto) y mire sus
opciones. Si se ha desactivado su suscripción o si Mailman ha
recibido mensajes devueltos provenientes de su dirección de
correo, usted encontrará un gran mensaje en la parte superior de
esta página.
Para reactivar la entrega de correo, ubique una opción
identificada como ``Entrega del correo'' y seleccione ``Habilitar''
para iniciar de nuevo a recibir el correo. Para deshacerse de su
puntaje de mensajes devueltos, usted puede desactivar y luego
volver a activar la entrega. Más instrucciones sobre la
desactivación o activación de la entrega del correo se encuentran
en la Sección 7.1.
Nota: Aún si usted no estuviera inhabilitado en el momento en que
revisa, usted podrÃa estar recibiendo mensajes devueltos y no haber
alcanzado el lÃmite para que su suscripción se desactive. Usted
puede necesitar revisar de nuevo.
* Hay un retardo o interrupción en las redes existentes entre usted
y el servidor de listas.
Por mucho que nos gustarÃa, Internet no es 100% confiable ni
siempre es rápida. Algunas veces los mensajes simplemente demoran
mucho tiempo en llegar. Trate de ser paciente, especialmente si el
servidor está alejado (en términos de redes, no geográficamente,
aunque a menudo lo uno implica lo otro) de su proveedor de servicio
de Internet.
Para revisar si esta podrÃa ser la causa de su problema, usted
puede probar realizando un ping al servidor de la lista o trazar la
ruta entre usted y él (las instrucciones de cómo hacer esto varÃa
de una plataforma a otra, asà que usted puede desear usar un motor
de búsqueda para encontrar aquellas más apropiadas para usted).
* El servidor de correo o Mailman podrÃan no estar funcionando
correctamente. Esto puede ocurrir si el sistema está sobrecargado
con virus o spam y el sistema de correo que aloja Mailman tiene
problemas al procesarlos.
Para revisar si este es el caso, pruebe utilizando el interfaz web
de la lista y trate de enviar un mensaje a
NOMBRELISTA-request@DOMINIO con la orden ``help'' (sin las
comillas) en la lÃnea de Asunto:. Si nada de esto funciona después
de un razonable lapso de tiempo, ese puede ser el problema. Usted
puede desear contactar al administrador de la lista o al
administrador del sitio.
8 EnvÃos agrupados
8.1 ¿Cómo puedo iniciar o dejar de recibir los mensajes enviados a la lista
agrupados en un correo de gran tamaño? (opción digest)
Los grupos de envÃos se llaman ``digests'' en Mailman. En lugar de
recibir los mensajes de uno en uno, usted puede recibir los mensajes
agrupados (digests). En una lista bastante ocupada, esto tÃpicamente
significa que usted recibe un correo por dÃa, aunque podrÃa ser más o
menos frecuente dependiendo de la lista.
Usted también puede desear mirar la Sección 8.2 que trata sobre los
envÃos agrupados en formato MIME y texto plano.
Para activar o desactivar los envÃos en modo agrupado usando la
interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 más detalles de cómo hacer esto).
2. Ubique la sección identificada como ``Activar envÃos agrupados''
Seleccione ``On'' para recibir los envÃos agrupados. Seleccione
``Off'' para recibir por separado cada uno de los envÃos.
Para activar o desactivar los envÃos en modo agrupado usando el
interfaz de correo electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden
set digest plain o set digest mime o set digest off.
Las órdenes pueden aparecer ya sea en el cuerpo o el la lÃnea de
asunto de un mensaje (ver en la Sección 3.2 más información
sobre el envÃo de órdenes de correo).
2. Seleccione ``off'' si usted desea recibir los mensajes cada uno por
separado y seleccione ``plain'' o ``mime'' para recibir los
mensajes agrupados en un gran correo, en forma periódica. Mire en
la Sección 8.2 más información sobre envÃos agrupados en formato
MIME versus texto plano.
8.2 ¿Qué son los EnvÃos Agrupados MIME o de Texto Plano? ¿Cómo puedo decidir
cuales recibir? (opción digest)
MIME es la sigla de Multipurpose Internet Mail Extensions (Extensiones
Multipropósito de Correo de Internet). Se usa para enviar por correo
electrónico cosas que no necesariamente son simple texto plano (por
ejemplo, se podrÃa usar MIME si usted fuera a enviar una fotografÃa de
su perro a un amigo).
Un envÃo agrupado en formato MIME contiene cada mensaje como un adjunto
dentro del mensaje, junto con un resumen de la tabla de contenido.
Un envÃo agrupado en formato texto plano es una forma más simple de
envÃo agrupado, el cual deberÃa ser legible aún en los lectores de
correo que no soportan MIME. Los mensajes se ponen simplemente uno
después de otro en un gran mensaje de texto.
Los programas de correo más modernos soportan MIME, asà que usted
sólo necesita seleccionar envÃos agrupados en formato de texto plano
si está teniendo problemas al leer los que están en formato MIME.
Nota: Esta opción no tiene efecto si usted no está recibiendo correo
en modo agrupado (mire en la Sección 8.1 más información sobre
recepción del correo en modo agrupado).
Para seleccionar el tipo de envÃos agrupados a recibir, usando el
interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 más detalles de cómo hacer esto).
2. Ubique la sección identificada como ``¿Recibir envÃos agrupados
MIME o de texto plano?''
Seleccione ``MIME'' para recibir los envÃos agrupados en formato
MIME, o ``Plain text'' para recibir los envÃos agrupados en formato
de texto plano.
Esto también se puede cambiar para múltiples listas al mismo tiempo
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 la información sobre cambios globales de
configuración.
Para seleccionar su tipo de envÃos agrupados a recibir, usando el
interfaz de correo electrónico:
1. EnvÃe un correo electrónico a NOMBRELISTA-request@DOMINIO con la
orden set digest plain o set digest mime.
Los comandos pueden aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 más información sobre
envÃo de órdenes de correo).
2. Seleccione ``plain'' para recibir los envÃos agrupados en formato
de texto plano, o ``mime'' para recibir los envÃos agrupados en
formato MIME.
9 Temas de listas de correo
Algunas listas están configuradas para que Mailman maneje diferentes
temas. Por ejemplo, la lista de cursos en Linuxchix.org es una lista de
discusión para cursos que se están dictando para miembros de
linuxchix, y a menudo, hay varios cursos que se están dictando al
mismo tiempo (por ejemplo, redes para principiantes, programación en
C, etiquetado de documentos LaTeX).
Cada uno de estos cursos que se están dictando está asociado con un
tema diferente en la lista de manera que la gente puede escoger que
curso o cursos tomar. El administrador debe configurar los temas, pero
es responsabilidad de cada suscriptor asegurarse que cada envÃo tenga
el tema correcto. Usualmente, ello requiere adicionar una palabra o
etiqueta de algún tipo a la lÃnea de asunto (por ejemplo: [Redes]
¿Qué tipos de cables necesito?) o asegurarse que la lÃnea Palabras
claves: tiene la información correcta (por omisión, usted puede poner
una sección Palabras claves: en el comienzo del cuerpo de su mensaje,
pero esto lo puede configurar su administrador de la lista). Note que
estas etiquetas no son sensibles a minúsculas/mayúsculas.
9.1 ¿Cómo puedo asegurarme que mis envÃos tienen el tema apropiado?
Cuando un administrador de lista define un tema, puede definir tres
cosas:
* un nombre de tema
* una expresión regular (regexp)
* una descripción
Usted puede mirar esta información ingresando a su página de opciones
de suscriptor (ver en la Sección 3.1 más detalles de cómo hacer
esto) y haciendo clic en el enlace ``Detalles'' de cualquiera de los
temas que le interesen.
Para enviar un mensaje sobre un determinado tema, usted necesita
asegurarse que las Palabras claves: o las cabeceras de Asunto: de su
mensaje concuerdan con la expresión regular de ese tema. Una
expresión regular es un patrón que puede coincidir con más de una
cosa. Realmente las expresiones regulares pueden ser mucho más
complejas, asà que usted puede sencillamente preguntar al administrador
de la lista si usted no sabe como crear cabeceras o colas de una
expresión dada.
Si realmente usted desea saber más sobre expresiones regulares, siga
leyendo, pero para la mayor parte, su administador de la lista deberÃa
incluir en la descripción del tema, lo que usted necesita adicionar a
sus Palabras Claves o lÃnea de Asunto para que coincida con el patrón
del tema.
La mayorÃa de expresiones de temas Mailman corresponderan a expresiones
regulares bastante simples, asà que en este documento simplemente se
darán algunos ejemplos comunes. Las expresiones regulares son un
poquito complejas para enseñar aquà en unas pocas lÃneas, asà que si
usted realmente desea entender como trabajan, usted deberÃa encontrar
un instructivo o referencia en otro lado (por ejemplo, DevShed tiene un
buen instructivo en
http://www.devshed.com/Server_Side/Administration/RegExp/)
Aquà hay algunos ejemplos de posibles expresiones regulares y lÃneas
concordantes:
Expresión Regular LÃneas concordantes
zuff Palabras Claves: zuff
zuff Palabras Claves: ZUFF
zuff Palabras Claves: Zuff
zuff Palabras Claves: amarilis, zuff, puré de manzana
zuff Asunto: [zuff] ¿Tienes lo necesario para el zuff?
zuff Asunto: ¿Tienes lo apropiado para el zuff?
zuff Asunto: ¿Qué es zuff?
\[zuff\] Palabras Claves: [zuff]
\[zuff\] Asunto: [zuff] ¿Tienes lo necesario?
\[zuff\] Asunto: Tutoriales en lÃnea de zuff (Re: [zuff] ¿Qué es
zuff?)
Unas pocas notas:
* Las concordancias no son sensibles a mayúsculas/minúsculas, asÃ
que si concuerda zuff, lo hará ZUFF, zuFF, y cualquier otra
variación en el uso de las mayúsculas/minúsculas.
* Algunos caracteres tienen un significado especial en una expresión
regular, asà que para concordar especÃficamente con esos
caracteres, ellos deben ser ``escapados'' con una diagonal inversa
(\). Como usted puede ver en los ejemplos de arriba, los
paréntesis rectangulares ([ y ]) son unos de esos caracteres
(otros incluyen ``.'', ``?'', y ``*''). La diagonal inversa
también se usa para otras cosas (no es broma la complejidad de las
expresiones regulares: consulte en otra documentación los detalles
sobre otros usos del caracter de diagonal inversa), pero este es el
uso más probable en una expresión de tema.
9.2 ¿Cómo me suscribo a algunos o a todos los temas de una lista?
Si el administrador de su lista configuró temas, usted puede elegir
suscribirse solamente a una parte de la lista seleccionado los temas
que usted desee recibir.
Si usted desea recibir todos los mensajes enviados a la lista,
asegúrese que usted no está suscrito a ninguno de los temas.
Probablemente usted también desdea mirar la Sección 9.3 la cual
discute el cambio de su configuración para mensajes que no tienen
temas definidos.
Para seleccionar los temas que desea recibir, utilizado el interfaz
web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 más detalles de cómo hacer esto).
2. Ubique la sección identificada como ``¿A qué temas le gustarÃa
suscribirse?''
Si algún tema está definido, usted puede seleccionar aquelos que
desee. Si usted no selecciona ningún tema de interés, usted
recibirá todos los mensajes enviados a la lista.
9.3 ¿Cómo logro o evito recibir mensajes sin tema definido?
Algunos mensajes no corresponderán con ninguno de los patrones de
temas definidos. Usted puede escoger recibir o ignorar tales mensajes
que no coinciden. Si usted desea recibir todos los mensajes enviados a
la lista, asegúrse que usted no está suscrito a ningún tema
especÃfico (ver Sección 9.2).
Si usted únicamente está suscrito a algunos temas, usted puede elegir
si recibe o no recibe mensajes sin tema definido, de la misma forma
cómo usted puede seleccionar suscribirse únicamente a ciertos temas.
Para cambiar esta opción:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 los detalles de cómo hacer esto).
2. Ubique la sección identificado como ``¿Desea recibir mensajes que
no concuerden con algún filtro de tema?''
Si usted desea recibir mensajes sin tema definido, seleccione
``Si''. Si usted no desea recibir tales mensajes, seleccione
``No''.
This setting has no effect if you are not subscribed to any topics.
Este cambio no tiene efecto si usted no está suscrito a algún tema de
las listas.
10 Definiendo otras opciones
10.1 ¿Cambiar Globalmente? ¿Definir Globalmente? ¿Qué significa esto?
Para algunas de las opciones dadas en su página de opciones de
suscriptor, hay una casilla de verificación que dice ``Cambiar
globalmente'' o ``Aplicar globalmente''. Esto significa que si usted
cambia esta opción, también se hará el cambio para todas las
suscripciones que usted tenga en el mismo dominio. Esto puede ser
práctico si, por ejemplo, usted desea utilizar una misma contraseña
para todas sus listas, o si usted sale de vacaciones y desea suspender
la entrega de correo de todas las listas.
10.2 ¿Cómo cambio el nombre que registré en Mailman?
Para cambiar su nombre de suscripción:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 más detalles de cómo hacer esto).
2. En la sección ``Cambio de su información de suscriptor de
NOMBRELISTA'', entre su nuevo nombre en el cuadro de texto
apropiado.
Esto también se puede cambiar para múltiples listas al mismo tiempo
si usted está suscrito a más de una lista en el mismo dominio. Mire
en la Sección 10.1 información sobre cambios globales de
configuración.
Nota: Usted no necesita tener un nombre de suscriptor definido.
10.3 ¿Cómo selecciono mi idioma preferido?
Mailman es multilingüe, lo que quiere decir que su interfaz se ha
traducido a muchos idiomas diferentes. El administrador de su lista
puede habilitar varios idiomas para su uso cuando se interactúa con
Mailman. (Para obtener un listado completo de los idiomas disponibles
mire http://wiki.list.org/display/DEV/Languages). Si su lista tiene
otros idiomas habilitados, usted puede utilizar el interfaz web y el
interfaz de correo electrónico, en un idioma de su elección.
Nota: Esto no significa que los mensajes enviados a la lista estarán
en el idioma que haya seleccionado. Ãnicamente las plantillas y otros
textos propios de Mailman, serán afectados por esta configuración.
Los envÃos se hacen en el idioma que escriban los suscriptores.
Su idioma preferido se define cuando usted se suscribe (mire la
Sección5.1), pero se puede cambiar posteriormente si la lista soporta
más de un idioma.
Para cambiar su idioma preferido en Mailman:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 las instrucciones sobre cómo hacer esto).
2. Vaya a la sección identificada como ``¿Qué idioma prefiere?'' y
escoja el idioma apropiado de la lista desplegable. Si no hay una
lista de idiomas, probablemente la lista en que se encuentra sólo
soporta un idioma.
Si su lista no soporta el idioma que usted preferirÃa usar, puede
contactar al administrador de la lista (NOMBRELISTA-owner@DOMINIO) para
mirar si se puede adicionar, pero recuerde que esto puede representar
mayor trabajo y el administrador de la lista o del sitio pueden no
tener el tiempo necesario o la capacidad de hacerlo.
Si el idioma de su elección no está disponible porque no existe
traducción para Mailman, por favor considere ofrecer su tiempo como
traductor voluntario. Para mayor información, usted puede desear
consultar la lista de correo mailman-i18n en
http://mail.python.org/mailman/listinfo/mailman-i18n. Información
sobre el estado actual de los esfuerzos de internacionalización se
encuentra en http://wiki.list.org/display/DEV/Languages.
Nota: i18n en una abreviatura para ``internationalization'' ya que la
palabra comienza con una i, termina con una n, y tiene 18 letras entre
ellas. Si usted musita un poco, i18n inclusive suena un tanto como
``internationalization''.
10.4 ¿Cómo evito que mi nombre aparezca en la lista de suscriptores? (opción
hide)
Si usted por alguna razón no desea que su dirección de correo
aparezca en la lista de suscriptores, puede optar por tenerla oculta.
Las razones comunes para hacer esto incluyen el evitar correo basura no
solicitado (spam). Por omisión la lista de suscriptores se oculta para
bloquear a recolectores de spam, pero si usted siente que esto es
insuficiente, es bastante fácil eliminar su dirección de la lista de
de suscriptores dada en las páginas de información o mediante una
solicitud de correo electrónico (note que esto no oculta su dirección
de los administradores de la lista). Si usted desea mire en la
Sección 11.2 más información sobre lo que Mailman hace para ayudar a
evitar el spam.
Para cambiar esta opción utilizando el interfaz web:
1. Ingrese a su página de opciones de suscriptor (mire en la
Sección 3.1 instrucciones sobre cómo hacer esto).
2. Vaya a la sección identificada como ``¿Ocultarse de la lista de
suscriptores?'' y escoja ``Si'' para ocultar su nombre de la lista,
o ``No'' para permitir que su nombre aparezca en la lista.
Para cambiar esta opción utilizando el interfaz de correo
electrónico:
1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la órden
set hide on o set hide off.
Las órdenes puede aparecer ya sea en el cuerpo o en la lÃnea de
asunto del mensaje (mire en la Sección 3.2 más información sobre
el envÃo de órdenes de correo.
2. Seleccione ``on'' para ocultar su dirección de correo electrónico
de la lista de membresÃa, u ``off'' para dejar de ocultar su
dirección.
11 Otras preguntas comunes
11.1 ¿Cómo puedo consultar los archivos de la lista?
Si la lista se está archivando, los mensajes previamente enviados se
pueden ver yendo a las páginas web del archivo, un enlace al cual se
encuentra en la página de información de la lista y en la cabecera
List-Archive: de todo mensaje enviado (a menos que el administración
de su lista haya desactivado tales cabeceras). Muchos programas de
correo ocultan la cabecera de correo List-Archive:, asà que usted
primero necesita hacer que su programa de correo le muestre las
cabeceras completas antes de que usted pueda mirar esa cabecera.
Los archivos públicos usualmente tienen direcciones de la forma
http://SERVIDORWEB/pipermail/NOMBRELISTA/, mientras que los archivos
privados usualmente tienen direcciones de la forma
http://SERVIDORWEB/mailman /private/NOMBRELISTA.
Mire en la Sección 3.1 más información sobre búsqueda de
direcciones de una lista.
11.2 ¿Qué hace Mailman para ayudar a protegerme de correo basura no solicitado
(spam)?
Los archivos de una lista técnica pueden incluir respuestas a un rango
de preguntas diferentes. A menudo, la gente que ha enviado estas
respuestas estarÃa gustoso de ayudar a alguien que no entiende
completamente la respuesta, y no le preocuparÃa dar su dirección para
ese propósito. Pero aunque serÃa maravilloso si todos nos puedieramos
contactar unos a otros con facilidad, también queremos asegurarnos que
la gente que envÃa spam no abuse de la lista ni de los archivos de la
lista.
Para hacer que un rango de opciones esté disponible a los
administradores de listas, Mailman permite una variedad de
configuraciones para ayudar a proteger las direcciones de correo.
Muchos de estas configuraciones son opcionales para el administrador de
la lista, asà que su lista particular puede estar configurada en forma
diferente. Los administradores de listas deben encontrar un punto de
equilibrio entre proteger a suscriptores y hacerlo difÃcil para que la
gente se ponga en contacto.
* Lista de suscriptores
+ El administrador de la lista puede seleccionar entre tener la
lista de suscriptores pública, visible únicamente a miembros
de la lista, o visible únicamente a administradores de la
lista.
+ La lista de suscriptores se muestra con las direcciones
disimuladas para que a los recolectores de spam se les
dificulte obtener su dirección.
+ Usted puede mantener su dirección oculta de la lista de
suscriptores (mire más información en la Sección 10.4).
+ Nota: La lista entera de suscriptores siempre está disponible
a los administradores de la lista.
* Archivos de la lista
+ El administrador de la lista pueden elegir que los archivos
sean públicos, visibles únicamente a suscriptores
(privados), o completamente no disponibles.
+ Los archivos HTML que son creados por Pipermail (el programa
de archivado que viene incluido por omisión con Mailman)
contienen únicamente direcciones disimuladas. Existen otros
programas de archivado que modifican las direcciones en
diferentes grados para que permanezcan menos legibles.
+ Si usted desea estar más seguro, puede definir la cabecera de
correo ``X-No-archive: yes'' y Mailman no archivará sus
envÃos. Similarmente, puede definir la cabecera de correo
``X-Archive: no'' para inhabilitar el archivado.
Advertencia: Esto no evita que otros suscritores reenvÃen sus
mensajes, posiblemente aún, incluyendo su dirección de
correo electrónico.
* EnvÃos limitados a las listas
+ El administrador de la lista puede elegir quien puede envÃar a
la lista. La mayorÃa de las listas, se moderan (un moderador o
administrador revisa cada envÃo), se configuran para que
solamente los suscriptores puedan enviar a la lista, o se
permite que cualquier persona pueda enviar a la lista.
+ Permitiendo que solamente los suscriptores puedan enviar a la
lista, Mailman a menudo bloquea todo el spam y algunos virus
que se envÃan a la lista. Como tal, esta es una configuración
bastante común utilizada por los administradores de listas.
* Listas anónimas
+ Las listas también se pueden volver completamente anónimas:
toda la información que identifique al remitente se elimina
de la cabecera antes de enviar un mensaje.
+ Esto no es tipicamente usado como medida anti-spam (tiene
otros usos), pero se podrÃa usar en esa forma si se quisiera.
Por supuesto, muchos métodos para disimular direcciones pueden ser
burlados por determinadas personas, asà que sea consciente de que las
protecciones usadas pueden no ser suficientes.
1 Referencia rápida de órdenes de correo electrónico
* confirm $<$ CADENA-DE-CONFIRMACIÃN $>$
+ Confirma una acción. La cadena de confirmación es
obligatoria y se deberÃa enviar en la respuesta al mensaje de
confirmación enviado por Mailman.
* end
+ Termina el procesamiento de órdenes. Utilice esta orden si su
programa de correo añade automáticamente un archivo de
firma.
* help
+ Recibe una copia del mensaje de ayuda.
* info
+ Obtiene información acerca de la lista.
* lists
+ Obtiene una listado de las listas de correo (cuyos nombres se
muestran públicamente), del servidor GNU Mailman.
* password [ $<$ CONTRASEÃA-ANTERIOR $>$ $<$ CONTRASEÃA-NUEVA $>$ ]
[address= $<$ DIRECCIÃN $>$ ]
+ Obtiene o cambia su contraseña. Sin argumentos, devuelve su
contraseña actual. Usted puede cambiar su contraseña
indicando los argumentos $<$ CONTRASEÃA-ANTERIOR $>$ y $<$
CONTRASEÃA-NUEVA $>$
* set ...
+ Cambia o muestra sus opciones de membresÃa.
Use `set help' (sin las comillas) para obtener una lista más
detallada de las opciones que puede cambiar. Esta lista
también se presenta en el Apéndice B.
Use `set show' (sin las comillas) para mirar la configuración
actual de sus opciones.
* subscribe [ $<$ CONTRASEÃA $>$ ] [digest|nodigest] [address= $<$
DIRECCIÃN $>$ ]
+ Suscribirse a la lista de correo. Usted debe proporcionar su
contraseña para desuscribirse o cambiar sus opciones, pero si
omite la contraseña, Mailman le generará una. Usted puede
obtener recordatorios de su contraseña periódicamente.
El siguiente parámetro puede ser ya sea: `nodigest' o
`digest' (sin comillas). Si usted desea suscribir una
dirección diferente de la dirección desde donde está
enviando esta solicitud, puede especificar `address= $<$
DIRECCIÃN $>$ ' (sin paréntesis angulares ni comillas).
* unsubscribe [ $<$ CONTRASEÃA $>$ ] [address= $<$ DIRECCIÃN $>$ ]
+ Desuscribirse de la lista de correo. Si usted suministra una
contraseña, ésta debe concordar con su contraseña actual.
Si se omite, el sistema le enviará un mensaje de
confirmación para desuscribir la dirección. Si usted desea
desuscribir una dirección diferente a la dirección desde
donde envÃa esta solicitud, puede especificar `address= $<$
DIRECCIÃN $>$ ' (sin paréntesis angulares ni comillas).
* who [ $<$ CONTRASEÃA $>$ ] [address= $<$ DIRECCIÃN $>$ ]
+ Muestra quien pertenece a la lista de correo. La lista está
limitada únicamente a los suscriptores, y usted debe
proporcionar su contraseña de membresÃa para obtenerla. Si
usted está enviando desde una dirección diferente a su
dirección de membresÃa, especifique su dirección de
membresÃa con `address= $<$ DIRECCIÃN $>$ ' (sin paréntesis
angulares ni comillas).
2 Referencia rápida de opciones del suscriptor
* set help
+ Muestra esta ayuda detallada.
* set show [address= $<$ DIRECCIÃN $>$ ]
+ Muestra la configuración actual de sus opciones. Si usted
está enviando desde una dirección diferente de su dirección
de membresÃa, especifique su dirección de membresÃa con
`address= $<$ DIRECCIÃN $>$ ' (sin paréntesis angulares ni
comillas).
* set authenticate $<$ CONTRASEÃA $>$ [address= $<$ DIRECCIÃN $>$ ]
+ Para cambiar cualquiera de sus opciones, usted debe incluir
este comando primero, junto con su contraseña de membresÃa.
Si usted está enviando desde una dirección diferente de su
dirección de membresÃa, especifique su dirección de
membresÃa con `address= $<$ DIRECCIÃN $>$ ' (sin paréntesis
angulares ni comillas).
* set ack on
set ack off
+ Cuando se activa la opción `ack', usted recibirá un mensaje
de acuso de recibo cada vez que usted envÃe un mensaje a la
lista.
* set digest plain
set digest mime
set digest off
+ Cuando la opción `digest' está desactivada, usted recibirá
los mensajes inmediatamente cuando ellos se envÃan. Use `set
digest plain' si en su lugar desea recibir los mensajes
agrupados en formato texto plano (p.e. envÃos agrupados RFC
1153). Use `set digest mime' si en su lugar desea recibir los
mensajes agrupados en formato MIME.
* set delivery on
set delivery off
+ Activa o desactiva la entrega. Esta opción no lo desuscribe,
en lugar de ello, hace que Mailman deje de entregarle
mensajes. Esto puede ser útil si usted sale de vacaciones.
¡Asegúrese de usar `set delivery on' cuando regrese de
vacaciones!
* set myposts on
set myposts off
+ Use `set myposts off' para evitar recibir copias de los
mensajes que usted envÃa a la lista. Esto no tiene efecto si
usted está recibiendo envÃos agrupados.
* set hide on
set hide off
+ Use `set hide on' para ocultar su dirección de correo
electrónico cuando la gente solicite la lista de
suscriptores.
* set duplicates on
set duplicates off
+ Use `set duplicates off' si usted desea que Mailman no le
envÃe mensajes si su dirección está explicitamente en los
campos To: o Cc: del mensaje. Esto puede reducir el número de
envÃos duplicados que usted recibe.
* set reminders on
set reminders off
+ Use `set reminders off' si usted desea desactivar el
recordatorio mensual de contraseña para la lista de correo.
Sobre este documento...
GNU Mailman Manual del Suscriptor de Listas, 11 de enero 2020, Release
2.1
This document was generated using the LaTeX2HTML translator.
LaTeX2HTML is Copyright © 1993, 1994, 1995, 1996, 1997, Nikos Drakos,
Computer Based Learning Unit, University of Leeds, and Copyright ©
1997, 1998, Ross Moore, Mathematics Department, Macquarie University,
Sydney.
The application of LaTeX2HTML to the Python documentation has been
heavily tailored by Fred L. Drake, Jr. Original navigation icons were
contributed by Christopher Petrilli.
__________________________________________________________________
Previous Page Up one Level Next Page GNU Mailman
Manual del Suscriptor de Listas
__________________________________________________________________
Release 2.1, documentation updated on 11 de enero 2020.
wget 'https://lists2.roe3.org/mdrone/doc/mailman-member.pdf'wget 'https://lists2.roe3.org/mdrone/doc/mailman-member.txt' #GNU mailman - list Member Manual Contents About this document... About
this document...
Previous Page Up one Level Next Page GNU Mailman - List Member Manual
__________________________________________________________________
GNU Mailman - List Member Manual
Terri Oda
terri(at)zone12.com
Release 2.1
January 11, 2020
Front Matter
Abstract:
This document describes the list member interface for GNU Mailman 2.1.
It contains instructions for subscribing, unsubscribing, viewing the
archives, editing user options, getting password reminders, and other
subscriber-level tasks. It also answers some common questions of
interest to Mailman list members.
Contents
*
+ 1 Introduction
o 1.1 Acknowledgements
o 1.2 What is a mailing list?
o 1.3 GNU Mailman
+ 2 Translating from our examples to real lists
+ 3 Mailman's interfaces
o 3.1 The web interface
o 3.2 The email interface
+ 4 I need to talk to a human!
+ 5 Subscribing and unsubscribing
o 5.1 How do I join a list? (subscribe)
o 5.2 How do I leave a list? (unsubscribe)
+ 6 Passwords
o 6.1 How do I get my password?
o 6.2 How do I change my password?
o 6.3 How do I turn password reminders on or off?
(reminders option)
+ 7 Changing mail delivery
o 7.1 How do I turn mail delivery on or off? (delivery
option)
o 7.2 How can I avoid getting duplicate messages?
(duplicates option)
o 7.3 How do I change my subscription address?
o 7.4 How do I stop or start getting copies of my own
posts? (myposts option)
o 7.5 How can I get Mailman to tell me when my post has
been received by the list? (ack option)
o 7.6 I don't seem to be getting mail from the lists. What
should I do?
+ 8 Digests
o 8.1 How can I start or stop getting the list posts
grouped into one big email? (digest option)
o 8.2 What are MIME and Plain Text Digests? How do I change
which one I get? (digest option)
+ 9 Mailing list topics
o 9.1 How do I make sure that my post has the right topic?
o 9.2 How do I subscribe to all or only some topics on a
list?
o 9.3 How do I get or avoid getting messages with no topic
set?
+ 10 Setting other options
o 10.1 Change Globally? Set Globally? What does that mean?
o 10.2 How do I change my name as Mailman knows it?
o 10.3 How do I set my preferred language?
o 10.4 How do I avoid having my name appear on the
subscribers list? (the hide option)
+ 11 Other common questions
o 11.1 How do I view the list archives?
o 11.2 What does Mailman do to help protect me from
unsolicited bulk email (spam)?
+ 1 Email commands quick reference
+ 2 Member options quick reference
1 Introduction
This document is intended to help the members of a Mailman 2.1 mailing
list learn to use the features available to them. It covers the use of
the web and email interfaces for subscribing and unsubscribing,
changing member options, getting password reminders and other
subscriber-level tasks. It also answers some common questions of
interest to Mailman list members.
Information for list and site administrators is provided in other
documents.
This document need not be read in order. If you are simply looking for
an answer to a specific question, jump to the appropriate place and
references to other sections will be provided if necessary or
potentially helpful.
Note: For the purposes of this document, we assume that the reader is
familiar with common terms related to email (eg: Subject line, body of
the message) and web sites (eg: drop-down box, button) or can look them
up. We also assume that the reader can already use his or her email
program and web browser well enough that instructions such as "send
email to this address" or "visit this web page" or "fill in the form
provided" are clear. If you are not familiar with these actions, you
may want to consult other documentation to learn how to do these things
with your particular setup.
1.1 Acknowledgements
Sections of this document have been borrowed from the List
Administrator Manual found in Mailman CVS, which was written by Barry
A. Warsaw, and from the in-line help for Mailman 2.1.
The rest of this manual has been written by Terri Oda. Terri has been
maintaining mailing lists since the year she attained voting age in
Canada, although the two are not related. She currently oversees the
mailing lists at Linuxchix.org, as well as several smaller servers. In
the world outside of list administration, Terri is doing work with an
artificial life spam detector, and is actually more of a programmer
than technical writer.
Proofreading thanks go to Margaret McCarthy and Jason Walton.
1.2 What is a mailing list?
A mailing list is simply a list of addresses to which the same
information is being sent. If you were a magazine publisher, you would
have a list of the mailing addresses of all the subscribers to the
magazine. In the case of an electronic mailing list, we use a list of
email addresses from people interested in hearing about or discussing a
given topic.
Two common types of email mailing lists are announcement lists and
discussion lists.
Announcement lists are are used so that one person or group can send
announcements to a group of people, much like a magazine publisher's
mailing list is used to send out magazines. For example, a band may use
a mailing list to let their fan base know about their upcoming
concerts.
A discussion list is used to allow a group of people to discuss topics
amongst themselves, with everyone able to send mail to the list and
have it distributed to everyone in the group. This discussion may also
be moderated, so only selected posts are sent on to the group as a
whole, or only certain people are allowed to send to the group. For
example, a group of model plane enthusiasts might use a mailing list to
share tips about model construction and flying.
Some common terms:
* A "post" typically denotes a message sent to a mailing list. (Think
of posting a message on a bulletin board.)
* People who are part of an electronic mailing list are usually
called the list's "members" or "subscribers."
* "List administrators" are the people in charge of maintaining that
one list. Lists may have one or more administrators.
* A list may also have people in charge of reading posts and deciding
if they should be sent on to all subscribers. These people are
called list moderators.
* Often more than one electronic mailing list will be run using the
same piece of software. The person who maintains the software which
runs the lists is called the "site administrator." Often the site
administrator also administrates individual lists.
1.3 GNU Mailman
GNU Mailman is software that lets you manage electronic mailing lists.
It supports a wide range of mailing list types, such as general
discussion lists and announce-only lists. Mailman has extensive
features which make it good for list subscribers, such as easy
subscription and unsubscription, privacy options, and the ability to
temporarily stop getting posts from the list. The list member features
are covered in this document.
Mailman also has many features which make it attractive to list and
site administrators. These features are covered in the list and site
administrator manuals.
2 Translating from our examples to real lists
Often, it's easier to simply give an example than explain exactly how
to find the address for your specific list. As such, we'll frequently
give examples for a fictional list called LISTNAME@DOMAIN whose list
information page can be found at
http://WEBSERVER/mailman/listinfo/LISTNAME.
Neither of these are real addresses, but they show the form of a
typical list address. The capital letters used for the list-specific
parts of each address should make it easier to see what should be
changed for each list. Although specific list configurations may be
different, you will probably be able to just replace the words given in
capital letters with the appropriate values for a real list:
LISTNAME
The name of your list.
DOMAIN
The name of the mail server which handles that list.
WEBSERVER
The name of the web server which handles the list web interface.
This may be the same as DOMAIN, and often refers to the same
machine, but does not have to be identical.
As a real-life example, if you are interested in the mailman-users
list, you'd make the following substitutions: LISTNAME=mailman-users,
DOMAIN=python.org, WEBSERVER=mail.python.org. As such, for the
mailman-users@python.org mailing list, the list information page can be
found at the URL http://mail.python.org/mailman/listinfo/mailman-users.
(These, unlike most of the examples given in this document, are real
addresses.)
Most lists will have this information stored in the List-*: headers.
Many mail programs will hide these by default, so you may have to
choose to view full headers before you can see these informational
headers.
3 Mailman's interfaces
Mailman has two different interfaces for the list subscriber: the web
interface and the email interface. Most discussion list subscribers use
the email interface, since this includes the email address you use to
send mail to all the subscribers of that list.
The interface you use for changing options is largely a matter of
preference, since most (but not all) of the options which can be
changed from the web interface can also be changed by email. Usually it
is easier to use the web interface for changing options, since the web
interface provides instructions as you go, but there are times when
people may prefer the email interface, so both are provided.
3.1 The web interface
The web interface of Mailman is its selling point for many
administrators, since it makes it much easier for subscribers and
administrators to see which options are available, and what these
options do.
Every mailing list is also accessible by a number of web pages. Note
that the exact URLs are configurable by the site administrator, so they
may be different than what's described below. We'll describe the most
common configuration, but check with your site administrator or hosting
service for details.
List information (listinfo) page
+ Usually found at http://WEBSERVER/mailman/listinfo/LISTNAME
(for example,
http://lists.example.com/mailman/listinfo/mylist)
+ The listinfo page is the starting point for the subscriber
interface. As one would assume from the name it's given, it
contains information about the LISTNAME list. Usually all the
other subscriber pages can be accessed from this point, so you
really only need to know this one address.
Member options page
+ Usually found at
http://WEBSERVER/mailman/options/LISTNAME/EMAIL (For example,
http://lists.example.com/mailman/options/mylist/kathy@here.com
)
+ This page can also be accessed by going to the listinfo page
and entering your email address into the box beside the button
marked "Unsubscribe or Edit Options" (this is near the bottom
of the page).
+ The member options page allows you to log in/out and change
your list settings, as well as unsubscribe or get a copy of
your password mailed to you.
+ To log in to your member options page: If you are not already
logged in, there will be a box near the top for you to enter
your password. (If you do not know your password, see
Section 6.1 for more information on getting your password.)
Enter your password in the box and press the button.
+ Once you are logged in, you will be able to view and change
all your list settings.
List Archives
+ Usually found at http://WEBSERVER/pipermail/LISTNAME if the
list is publicly archived, and
http://WEBSERVER/mailman/private/LISTNAME if the list is
privately archives. (For example,
http://lists.example.com/pipermail/mylist or
http://lists.example.com/mailman/private/mylist)
+ The list archive pages have copies of the posts sent to the
mailing list, usually grouped by month. In each monthly group,
the posts are usually indexed by author, date, thread, and
subject.
+ Note: Pipermail is the name of the default archiver that comes
with Mailman. Other archive programs are available.
+ If the archive is private, you will need to supply your
subscribed email address and your password to log in. (See
Section 6.1 for more information on getting your password.)
3.2 The email interface
Every mailing list has a set of email addresses to which messages can
be sent. There's always one address for posting messages to the list,
one address to which bounces are sent, and addresses for processing
email commands. For a fictional mailing list called mylist@example.com,
you'd find these addresses:
* mylist@example.com - this is the email address people should use
for new postings to the list.
* mylist-join@example.com - by sending a message to this address, a
new member can request subscription to the list. Both the Subject:
header and body of such a message are ignored. Note that
mylist-subscribe@example.com is an alias for the -join address.
* mylist-leave@example.com - by sending a message to this address, a
member can request unsubscription from the list. As with the -join
address, the Subject: header and body of the message is ignored.
Note that mylist-unsubscribe@example.com is an alias for the -leave
address.
* mylist-owner@example.com - This address reaches the list owner and
list moderators directly. This is the address you use if you need
to contact the person or people in charge.
* mylist-request@example.com - This address reaches a mail robot
which processes email commands that can be used to set member
subscription options, as well as process other commands. A list of
members' email commands is provided in Appendix A.
* mylist-bounces@example.com - This address receives bounces from
members whose addresses have become either temporarily or
permanently inactive. The -bounces address is also a mail robot
that processes bounces and automatically disables or removes
members as configured in the bounce processing settings. Any bounce
messages that are either unrecognized, or do not seem to contain
member addresses, are forwarded to the list administrators.
* mylist-confirm@example.com - This address is another email robot,
which processes confirmation messages for subscription and
unsubscription requests.
There's also an -admin address which also reaches the list
administrators, but this address only exists for compatibility with
older versions of Mailman.
For changing options, we use the LISTNAME-request address (for example,
mylist-request@example.com).
Commands can appear in the subject line or the body of the message.
Each command should be on a separate line. If your mail program
automatically appends a signature to your messages, you may want to put
the word "end" (without the quotes) on a separate line after your other
commands. The end command tells Mailman not to process the email after
that point.
The most important command is probably the "help" command, since it
makes Mailman return a message full of useful information about the
email commands and directions to the web interface.
Quick references to the subscriber commands have been provided in
Appendices A and B. (These have been slightly adapted from the output
of the help command.)
4 I need to talk to a human!
If you have any trouble with any of these commands, you can always
reach the person or people in charge of a list by using the list
administrator email address. The list administrators can help you
figure out how to do something, subscribe/unsubscribe you, or change
your settings if you are unable to change them yourself for some
reason. Please remember that many mailing list administrators are
volunteers who are donating their spare time to run the list, and they
may be very busy people.
This list administrator email address is in the form
LISTNAME-owner@DOMAIN, where LISTNAME is the name of the list (eg:
mailman-users) and DOMAIN is the name of the server (eg: python.org).
This email address, along with the email addresses of specific
administrators, is given on the bottom of the list information pages.
See Section 3.1 for more information on finding the list information
page for your list
5 Subscribing and unsubscribing
Since subscribing (joining) and unsubscribing (leaving) lists are often
the only things a list member needs to know, these can both be done
without requiring you to know a password.
5.1 How do I join a list? (subscribe)
There are two common ways you can subscribe to a Mailman mailing list.
Using the web interface:
1. Go to the list information page for the list you want to join.
(This will probably be something like
http://WEBSERVER/mailman/listinfo/LISTNAME)
2. Look for the section marked "Subscribing to LISTNAME" and fill in
the boxes. You can fill in the following:
+ You must enter your email address.
+ You may choose to supply your real name.
+ You may choose a password. If you do not choose one, Mailman
will generate one for you.
Warning: Do NOT use a valuable password, since this password
may be mailed to you in plain text.
+ If the list supports more than one language, you may be able
to choose your preferred language. Note: This setting does not
affect posts to the list, only pre-prepared Mailman texts such
as your member options page.
3. Press the subscribe button. A new page should appear telling you
that your request has been sent.
Using the email interface:
1. Open a mail program which sends mail from the address you want to
subscribe.
2. Send a mail to the list subscription address, which will be in the
form LISTNAME-join@DOMAIN. The subject and body of the message will
be ignored, so it doesn't matter what you put there.
After following one of these sets of instructions (you don't need to do
both!), there are a few possible outcomes depending upon the settings
for that list.
* You may receive an email message asking for confirmation that you
really want to be subscribed to the list. This is to prevent anyone
from subscribing you to lists without your permission. Follow the
instructions given in the message to confirm your wish to be
subscribed.
* A moderator may also need to confirm your subscription if you are
subscribing to a limited list.
* Or you may have to wait for a moderator and follow the instructions
in the confirmation mail.
Once this is done, you will likely receive another message welcoming
you to the list. This message contains some useful information
including your list password and some quick links for changing your
options, so you may want to save it for later reference.
Note: Subscribing can be done in other ways as well. See Appendix A for
more advanced email subscribing commands.
5.2 How do I leave a list? (unsubscribe)
Don't want to be on a list any more? If you're just going on vacation
or are too busy to read mails and want to temporarily turn them off,
you may want to stop mail delivery rather than unsubscribing. This
means you keep your password and other settings so you can, for
example, still have access to private list archives. If this is what
you'd prefer, see Section 7.1 for instructions on disabling mail
delivery temporarily.
If you actually want to leave the list, there are two common ways you
can unsubscribe from a Mailman mailing list.
Using the web interface:
1. Go to the list information page for the list you want to leave.
(This will probably be something like
http://WEBSERVER/mailman/listinfo/LISTNAME)
2. Look for the section marked "LISTNAME subscribers" (usually found
near the bottom of the page).
3. There should be a button marked "Unsubscribe or Edit Options."
Enter your email address in the box beside this button and press
the button.
4. You should be brought to a new page which has an "Unsubscribe"
button. Press it to unsubscribe and follow the instructions given.
Using the email interface:
1. Open a mail program which sends mail from the address you want to
unsubscribe.
2. Send a mail to the list unsubscribe address, which will be of the
form LISTNAME-leave@DOMAIN. The subject and body of this message
will be ignored, so it doesn't matter what you put there.
After following one of these sets of instructions (you don't need to do
both!), you will be sent a confirmation mail and must follow the
instructions given in that mail to complete the unsubscription. This is
to stop people from unsubscribing you without your permission. In
addition, a moderator may need to approve your unsubscription.
If you do not receive this confirmation mail with instructions, make
sure that you typed your email address correctly (if you were using the
web interface to unsubscribe) and that the address you tried to
unsubscribe is, indeed, actually subscribed to that list. For security
reasons, Mailman generates the same member options page regardless of
whether the address entered is subscribed or not. This means that
people cannot use this part of the web interface to find out if someone
is subscribed to the list, but it also means that it's hard to tell if
you just made a typo.
Once your unsubscription has been processed, you will will probably
receive another message confirming your unsubscription from the list,
and at that point you should stop receiving messages.
If you wish to skip the confirmation process (for example, you might be
unsubscribing an address which no longer works), it is possible to
bypass it by using your password instead and either logging in to your
options page using it (See Section 3.1), or sending it with your email
commands to LISTNAME-request (See Appendix A for advanced email
unsubscription commands). See Section 6.1 for more information on
getting your password.
6 Passwords
Your password was either set by you or generated by Mailman when you
subscribed. You probably got a copy of it in a welcome message sent
when you joined the list, and you may also receive a reminder of it
every month. It is used to verify your identity to Mailman so that only
the holder of the password (you!) and the administrators can view and
change your settings.
Warning: Do NOT use a valuable password for Mailman, since it can be
sent in plain text to you.
6.1 How do I get my password?
If you've forgotten your password and haven't saved the welcome message
or any reminder messages, you can always get a reminder through the web
interface:
1. Go to the list information page for the list from which you wish to
get your password (This will probably be something like
http://WEBSERVER/mailman/listinfo/LISTNAME)
2. Look for the section marked "LISTNAME subscribers" (this section is
usually found near the bottom of the page).
3. There should be a button marked "Unsubscribe or Edit Options."
Enter your email address in the box beside this button and press
the button.
4. You should be brought to a new page which has an "Password
Reminder" section. Press the "Remind" button to have your password
emailed to you.
If you do not receive the password reminder email after doing this,
make sure that you typed your email address correctly and that the
address you used is, indeed, actually subscribed to that list. For
security reasons, Mailman generates the same member options page
regardless of whether the address entered is subscribed or not. This
means that people cannot use this part of the web interface to find out
if someone is subscribed to the list, but it also means that it's hard
to tell if you just made a typo.
You can also get a reminder using the email interface,
1. Send a mail to LISTNAME-request@DOMAIN with the command password
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
If you are not sending mail from your subscribed address, you can
also specify this address by sending the command password address=
$<$ ADDRESS $>$ .
6.2 How do I change my password?
Warning: Do NOT use a valuable password, since this password may be
mailed to you in plain text.
From the web interface:
1. Log in to your member options page. (See Section 3.1 for
instructions on how to do this.)
2. Look for the password changing boxes on the right-hand side of the
page and enter your new password in the appropriate boxes, then
press the button marked "Change My Password."
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
From the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command password
$<$ OLDPASSWORD $>$ $<$ NEWPASSWORD $>$ .
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
If you are not sending mail from your membership address, you can
also specify this address with address= $<$ ADDRESS $>$ after $<$
NEWPASSWORD $>$ .
For example, if kathy@here.com wanted to change her mylist password
from zirc to miko, but she was sending mail from her work address
kathy@work.com, she could send a message to
mylist-request@example.com with the subject set to
password zirc miko address=kathy@here.com.
6.3 How do I turn password reminders on or off? (reminders option)
If you don't wish to the reminder email including your password every
month, you can disable it from the member options page. (You can always
get the password mailed out when you actually want it. See Section 6.1
for instructions.)
Using the web interface:
1. Log in to your member options page. (See Section 3.1 for
instructions on how to do this.)
2. Look for the section marked "Get password reminder email for this
list?" and change the value accordingly.
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
Using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command
set reminders on or set reminders off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "on" to receive reminders, and "off" to stop receiving
reminders.
7 Changing mail delivery
7.1 How do I turn mail delivery on or off? (delivery option)
You may wish to temporarily stop getting messages from the list without
having to unsubscribe. If you disable mail delivery, you will no longer
receive messages, but will still be a subscriber and will retain your
password and other settings.
This can be handy in a many different cases. For example, you could be
going on vacation or need a break from the list because you're too busy
to read any extra mail. Many mailing lists also allow only subscribers
to post to the list, so if you commonly send mail from more than one
address (eg, one address for at home and another for when you're
travelling), you may want to have more than one subscribed account, but
have only one of them actually receive mail. You can also use this as a
way to read private archives even on a list which may be too busy for
you to have sent directly to your mailbox. All you need to do is
subscribe, disable mail delivery, and use your password and email to
log in to the archives.
To disable/enable mail delivery using the web interface:
1. Log in to your options page. (See Section 3.1 for instructions.)
2. Go down to the section marked "Mail delivery" and select "Disabled"
to stop receiving mail, and "Enabled" to start receiving mail.
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
To disable/enable mail delivery using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command
set delivery off or set delivery on.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "off" to stop receiving posts, and "on" to start
receiving them again.
7.2 How can I avoid getting duplicate messages? (duplicates option)
Mailman can't completely stop you from getting duplicate messages, but
it can help. One common reason people get multiple copies of a mail is
that the sender has used a "group reply" function to send mail to both
the list and some number of individuals. If you want to avoid getting
these messages, Mailman can be set to check and see if you are in the
To: or CC: lines of the message. If your address appears there, then
Mailman can be told not to deliver another copy to you.
To turn this on or off using the web interface:
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Scroll down to the bottom of the page to the section marked "Avoid
duplicate copies of messages?" and change the value accordingly.
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
To turn this on or off using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command
set duplicates on or set duplicates off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "on" to receive list copies of messages already sent to
you, set it to "off" to avoid receiving these duplicates.
7.3 How do I change my subscription address?
To change your subscription address,
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. In the section marked "Changing your LISTNAME membership
information," enter your new address.
3. If you wish to change your address for all subscriptions using the
old address, select the "Change globally" box. If you have
subscriptions under another address or for lists on a different
domain, these will have to be done separately. See Section 10.1 for
more information about changing settings globally.
There is no special way to do this from the email interface, but you
can subscribe and unsubscribe for more or less the same effect. (See
Sections 5.1 and 5.2 for more information on subscribing and
unsubscribing.)
7.4 How do I stop or start getting copies of my own posts? (myposts option)
By default in Mailman, you get a copy of every post you send to the
list. Some people like this since it lets them know when the post has
gone through and means they have a copy of their own words with the
rest of a discussion, but others don't want to bother downloading
copies of their own posts.
Note: This option has no effect if you are receiving digests.
You may also want to see Section 7.5, which discusses acknowledgement
emails for posts sent to the list.
To set this using the web interface:
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Receive your own posts to the list?"
Set it to "Yes" to receive copies of your own posts, and "No" to
avoid receiving them.
To set this using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command
set myposts on or set myposts off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "on" to receive copies of your own posts, and "off" to
avoid receiving them.
7.5 How can I get Mailman to tell me when my post has been received by the list?
(ack option)
On most lists, you will simply receive a copy of your mail when it has
gone through the list software, but if this is disabled (See
Section 7.4), your list mail delivery is disabled (See Section 7.1),
you are not subscribed to that topic (See Section 9.2) or you simply
want an extra acknowledgement from the system, this option may be
useful to you.
Note: If you are not subscribed to the list, this option cannot be
used. You must either check the archives yourself (if the list has
public archives), ask someone who is subscribed to the list, or
subscribe to use this option.
To set this using the web interface:
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Receive acknowledgement mail when you
send mail to the list?" Set it to "Yes" to receive a mail letting
you know your post has been received, and "No" to avoid receiving
such an acknowledgement.
To set this using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command set ack on
or set ack off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "on" if you wish to receive mail letting you know your
post has been received, and "off" to avoid receiving such an
acknowledgement.
7.6 I don't seem to be getting mail from the lists. What should I do?
There are a few common reasons for this:
* No one has sent any mail to the list(s) you're on for a little
while.
To check if this is the case, try visiting the archives of the list
(assuming that the list has archives). If the list has no archives,
you may have to ask another subscriber. (See Section 3.1 for help
in finding the list archives.)
Note: Generally, it is considered impolite to send test messages to
the entire list. If you feel a need to test that the list is
working and for some reason you cannot simply compose a regular
message to the list, it is less disruptive to send a help message
to the list request address (LISTNAME-request@DOMAIN) to see if
that works, or to contact the list administrator
(LISTNAME-owner@DOMAIN) to ask if the list is working.
* You were bouncing mail and have had mail delivery (temporarily)
disabled by the list software.
If your mail provider "bounces" too many messages (that is, it
tells Mailman that the message could not be delivered) Mailman
eventually stops trying to send you mail. This feature allows
Mailman to gracefully handle addresses which no longer exist (for
example, the subscriber has found a new internet service provider
and forgot to unsubscribe the old address), as well as addresses
which are temporarily out-of-service (for example, the subscriber
has used up all of the allotted space for his or her email account,
or the subscriber's mail provider is experiencing difficulties).
Even if you are unaware of any difficulties with your mail
provider, it is a good idea to check this. Some popular webmail
providers and internet servers are not as reliable as one might
assume, nor is the internet as a whole. You may want to also send
yourself a test message from another account or ask a friend to
send you a test message to make sure your subscribed address is
working.
To check if this may be the reason you are not receiving messages,
log in to the your options page (See Section 3.1 for more details
on how to do this) and look at your options. There should be one
marked "Mail Delivery" - if it is set to "Disabled," set it to
"Enabled" to start receiving mail again. (For more instructions on
disabling or enabling mail delivery, see Section 7.1.)
Note: Even if you have not been disabled at the time you check, you
could be bouncing messages and not have reached the threshold for
your subscription to be disabled. You may need to check again.
* There is a delay or break in the networks between you and the list
server.
No matter what many of us would like, the internet is not 100%
reliable, nor is it always fast. Sometimes, messages simply take a
long time to get to you. Try to be patient, especially if the
server is far (in terms of networks, not geography, although often
one implies the other) from your internet service provider.
To check if this might be causing your problem, you can try pinging
the list server or tracing the route between you and it.
(Instructions on how to do this varies from platform to platform,
so you may want to use a search engine to find those appropriate
for you.)
* The Mailman installation on the list server is not functioning or
not functioning properly.
To test if this is a case, try visiting the list's web interface
and try sending a message to LISTNAME-request@DOMAIN with the
command "help" (without the quotes) in the Subject:. If neither of
these works after a reasonable length of time, this may be the
problem. You may wish to contact either the list or site
administrator(s).
8 Digests
8.1 How can I start or stop getting the list posts grouped into one big email?
(digest option)
Groups of posts are called "digests" in Mailman. Rather than get
messages one at a time, you can get messages grouped together. On a
moderately busy list, this typically means you get one email per day,
although it may be more or less frequent depending upon the list.
You may also want to look at Section 8.2 which discusses MIME and plain
text digests.
To turn digest mode on or off using the web interface,
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Set Digest Mode."
Set it to "On" to receive messages bundled together in digests. Set
it to "Off" to receive posts separately.
To turn digest mode on or off using the email interface,
1. Send a mail to LISTNAME-request@DOMAIN with the command
set digest plain or set digest mime or set digest off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "off" if you wish to receive individual posts separately,
and to "plain" or "mime" to receive posts grouped into one large
mail. See Section 8.2 for more information on plain versus MIME
digests.
8.2 What are MIME and Plain Text Digests? How do I change which one I get?
(digest option)
MIME is short for Multipurpose Internet Mail Extensions. It is used to
send things by email which are not necessarily simple plain text. (For
example, MIME would be used if you were sending a picture of your dog
to a friend.)
A MIME digest has each message as an attachment inside the message,
along with a summary table of contents.
A plain text digest is a simpler form of digest, which should be
readable even in mail readers which don't support MIME. The messages
are simply put one after the other into one large text message.
Most modern mail programs do support MIME, so you only need to choose
plain text digests if you are having trouble reading the MIME ones.
Note: This option has no effect if you are not receiving mail bunched
as digests. (See Section 8.1 for more information on receiving mail as
digests.)
To set your digest type using the web interface:
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Get MIME or Plain Text Digests?."
Set it to "MIME" to receive digests in MIME format, or "Plain text"
to receive digests in plain text format.
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
To set your digest type using the email interface,
1. Send a mail to LISTNAME-request@DOMAIN with the command
set digest plain or set digest mime.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "plain" to get posts bundled into a plain text digest, or
"mime" to get posts bundled together into a MIME digest.
9 Mailing list topics
Some lists are set up so that different topics are handled by Mailman.
For example, the courses list on Linuxchix.org is a discussion list for
courses being run by linuxchix members, and often there are several
courses being run at the same time. (eg: Networking for beginners, C
programming, LaTeX document mark up.) Each of the courses being run is
a separate topic on the list so that people can choose only to receive
the course they want to take.
These topics must be configured by the list administrator, but it is
the responsibility of each poster to make sure that their post is put
with the correct topic. Usually, this means adding a tag of some type
to the subject line (eg: [Networking] What type of cables do I need?)
or making sure the Keywords: line has the right information. (By
default, you can put a Keywords: section in the beginning of the body
of your message, but this can be configured by your list
administrator.) Note that these tags are case-insensitive.
9.1 How do I make sure that my post has the right topic?
When a list administrator defines a topic, he or she sets three things:
* a topic name
* a regular expression (regexp)
* a description
You can view this information by logging in to your member options
page. (See Section 3.1 for more details on how to do this.) and
clicking on the "details" link for any topic that interests you.
To post on a given topic, you need to make sure that the Keywords: or
Subject: headers in a message match the regular expression for that
topic. Regular expressions can actually be fairly complex, so you may
want to just ask the list administrator if you don't know how to make
heads or tails of the expression given.
Most Mailman topic expressions will be fairly simple regular
expressions, so in this document we will simply give you some common
examples. Regular expressions are a bit too complex to teach in a few
lines here, so if you really want to understand how the regular
expressions work, you should find a tutorial or reference elsewhere.
(For example, DevShed has a decent tutorial at
http://www.devshed.com/Server_Side/Administration/RegExp/)
Here are some examples of possible regular expressions and matching
lines:
Regular expression Matching lines
zuff Keywords: zuff
zuff Keywords: ZUFF
zuff Keywords: Zuff
zuff Keywords: amaryllis, zuff, applesauce
zuff Subject: [zuff] Do you have the right stuff for zuff?
zuff Subject: Do you have the right stuff for zuff?
zuff Subject: What is zuff?
\[zuff\] Keywords: [zuff]
\[zuff\] Subject: [zuff] Do you have the right stuff?
\[zuff\] Subject: Online zuff tutorials (was Re: [zuff] What is zuff?)
A few notes:
* The matching is case-insensitive, so if zuff matches, so will ZUFF,
zuFF, and any other variations in capitalization.
* Some characters have special meaning in a regular expression, so to
match those characters specifically, they must be "escaped" with a
backslash (\). As you can see in the above example, [ and ] are
such characters. (Others include ".", "?", and "*"). The backslash
is also used for other things (I wasn't kidding about regular
expressions being complex: consult other documentation for details
about other uses of the backslash character), but this is the most
likely use in a topic expression.
9.2 How do I subscribe to all or only some topics on a list?
If topics have been set up by your mailing list administrator, you can
choose to subscribe to only part of a list by selecting the topics you
want to receive.
If you wish to get all messages sent to the list, make sure you are not
subscribed to any topics.
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Which topic categories would you like
to subscribe to?"
If any topics are defined, you can select those you wish. If you do
not select any topics of interest, you will receive all posts sent
to the list.
You probably also want to look at Section 9.3 which discusses changing
your settings for messages where no topic is set.
9.3 How do I get or avoid getting messages with no topic set?
If you wish to get all messages sent to the list, make sure you are not
subscribed to any specific topic. (See Section 9.2.)
If you are only subscribed to some topics, you can either choose to
either receive or not receive messages with no topic set, much the way
you can choose to subscribe only to certain topics.
To change this setting,
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. Look for the section marked "Do you want to receive message that do
not match any topic filter?"
If you wish to receive messages with no topic set, select "Yes." If
you do not wish to receive such messages, choose "No."
This setting has no effect if you are not subscribed to any topics.
10 Setting other options
10.1 Change Globally? Set Globally? What does that mean?
For some of the options given in your member options page, there is a
tick-box which says "Change Globally" or "Set Globally." This means
that if you change this option, you can also have the change made for
all your other list subscriptions with the same address to lists on the
same domain. This can be handy if, for example, you want to make sure
all your passwords are the same, or you are going on vacation and want
to turn off mail delivery from all the lists.
10.2 How do I change my name as Mailman knows it?
To change your subscription name,
1. Log in to your member options page. (See Section 3.1 for more
details on how to do this.)
2. In the section marked "Changing your LISTNAME membership
information," enter your new name in the appropriate box.
This can also be changed for multiple lists at the same time if you are
subscribed to more than one list on the same domain. See Section 10.1
for information about changing settings globally.
Note: You do not need to have a subscription name set.
10.3 How do I set my preferred language?
Mailman is available with many different languages. (For a complete
listing see http://wiki.list.org/display/DEV/Languages.) This means
that, if your list has other languages enabled, you may be able to have
the web interface, etc. in a language of your choice.
Note: This does NOT necessarily mean that all the posts sent to the
list will be in the language you selected. Only the pre-prepared texts
presented by Mailman will be affected by this setting. Posts are in
whatever language the poster uses.
Your preferred language is set when you subscribe (see Section5.1), and
can be changed later if the list supports more than one language.
To change your preferred language in Mailman,
1. Log in to your member options page. (See Section 3.1 for
instructions on how to do this.)
2. Go to the section marked "What language do you prefer?" and choose
the appropriate language from the drop-down list. If there is no
drop-down list of languages, the list you are on probably only
supports one language.
If your list does not support the language you would prefer to use, you
may contact the list administrator (LISTNAME-owner@DOMAIN) to see if it
can be added, but remember that this may mean some work that the list
and/or site administrator(s) do not have time or the ability to do.
If your language of choice is not available because no translation
exists for Mailman, please consider volunteering your time as a
translator. For more information you may want to consult the
mailman-i18n mailing list at
http://mail.python.org/mailman/listinfo/mailman-i18n. (i18n is a common
short-hand for "internationalization" because the word starts with an
i, ends with an n, and has 18 letters in between. If you mumble a bit,
i18n even sounds a bit like "internationalization.")
10.4 How do I avoid having my name appear on the subscribers list? (the hide
option)
If you do not want to have your email address show up on the subscriber
list for any reason, you can opt to have it concealed.
Common reasons for doing this include avoiding unsolicited bulk email
(spam). By default, the subscribers list is obscured to hinder spam
harvesters, but if you feel this is insufficient it's easy enough to
remove address from the subscriber list given in the information pages
or by email request. (Note that this does not conceal your address from
the list administrators.) You may wish to see Section 11.2 for more
information on what Mailman can do to help avoid spam.
To change this setting using the web interface:
1. Log in to your member options page. (See Section 3.1 for
instructions on how to do this.)
2. Go to the section marked "Conceal yourself from subscriber list?"
and choose "Yes" to hide your name from the list, or "No" to allow
your name to appear on the list.
To change this setting using the email interface:
1. Send a mail to LISTNAME-request@DOMAIN with the command set hide on
or set hide off.
Commands can appear in either the body or the subject of the
message. (See Section 3.2 for more information about sending mail
commands.)
2. Set it to "on" to conceal your email address from the membership
list, or "off" to stop concealing your address.
11 Other common questions
11.1 How do I view the list archives?
If the list has archives, they can be viewed by going to a web page
address. This address usually linked from the list information page and
can be found in the List-Archive: of every list message unless your
list administrator has disabled these headers. (Many mail programs hide
the List-Archive: mail header, so you may have to tell your mail
program to allow you to view full headers before you will be able to
see it.)
Public archives usually have addresses of the form
http://WEBSERVER/pipermail/LISTNAME/ and private archives usually have
addresses of the form http://WEBSERVER/mailman/private/LISTNAME.
See Section 3.1 for more information on finding the addresses of a
list.
11.2 What does Mailman do to help protect me from unsolicited bulk email (spam)?
A technical list's archives may include answers to a range of different
questions. Often, the people who have posted these answers would be
happy to help someone who doesn't quite understand the answer, and
don't mind giving their address out for that purpose. But although it
would be wonderful if everyone could contact each other easily, we also
want to make sure that the list and list archives are not abused by
people who send spam.
To make a range of options available to list administrators, Mailman
allows a variety of configurations to help protect email addresses.
Many of these settings are optional to the list administrator, so your
particular list may be set up in many ways. List administrators must
walk a fine line between protecting subscribers and making it difficult
for people to get in touch.
* Subscriber lists
+ The list administrator can choose to have the subscriber list
public, viewable only to list members, or viewable only to
list administrators.
+ The subscriber list is shown with the addresses obscured to
make it difficult for spam harvesters to collect your address.
+ You can choose to have your address hidden from the subscriber
list. (See Section 10.4 for more information.)
+ Note: The entire subscriber list is always available to the
list administrators.
* List archives
+ The list administrator can choose for the archives to be
public, viewable only to members (private), or completely
unavailable.
+ The HTML archives which are created by Pipermail (the
archiving program which comes default with Mailman) contain
only obscured addresses. Other archiving programs are
available and can do different levels of obfuscation to make
addresses less readable.
+ If you wish to be more sure, you can set the mail header
X-no-archive: and Mailman will not archive your posts.
Warning: This does not stop other members from quoting your
posts, possibly even including your email address.
* Limited posting to the lists
+ The list administrator can choose who can post to the list.
Most lists are either moderated (a moderator or administrator
reviews each posting), set so only subscribers may post to the
list, or allow anyone to post to the list.
+ By allowing only subscribers to post to a list, Mailman often
blocks all spam and some viruses from being sent through the
list. As such, this is a fairly common setting used by list
administrators.
* Anonymous lists
+ Lists can also be made fully anonymous: all identifying
information about the sender is stripped from the header
before the message is sent on.
+ This is not typically used for anti-spam measures (it has
other uses), but it could be used in that way if desired.
Of course, many address-obscuring methods can be circumvented by
determined people, so be aware that the protections used may not be
enough.
1 Email commands quick reference
* confirm $<$ CONFIRMATION-STRING $>$
+ Confirm an action. The confirmation-string is required and
should be supplied within a mailback confirmation notice.
* end
+ Stop processing commands. Use this if your mail program
automatically adds a signature file.
* help
+ Receive a copy of the help message.
* info
+ Get information about this mailing list.
* lists
+ See a list of the public mailing lists on this GNU Mailman
server.
* password [ $<$ OLDPASSWORD $>$ $<$ NEWPASSWORD $>$ ] [address= $<$
ADDRESS $>$ ]
+ Retrieve or change your password. With no arguments, this
returns your current password. With arguments $<$ OLDPASSWORD
$>$ and $<$ NEWPASSWORD $>$ you can change your password.
* set ...
+ Set or view your membership options.
Use `set help' (without the quotes) to get a more detailed
list of the options you can change. This list is also given in
Appendix B.
Use `set show' (without the quotes) to view your current
option settings.
* subscribe [ $<$ PASSWORD $>$ ] [digest|nodigest] [address= $<$
ADDRESS $>$ ]
+ Subscribe to this mailing list. Your password must be given to
unsubscribe or change your options, but if you omit the
password, one will be generated for you. You may be
periodically reminded of your password.
The next argument may be either: `nodigest' or `digest' (no
quotes!). If you wish to subscribe an address other than the
address you sent this request from, you may specify `address=
$<$ ADDRESS $>$ ' (no brackets around the email address, and
no quotes!)
* unsubscribe [ $<$ PASSWORD $>$ ] [address= $<$ ADDRESS $>$ ]
+ Unsubscribe from the mailing list. If given, your password
must match your current password. If omitted, a confirmation
email will be sent to the unsubscribing address. If you wish
to unsubscribe an address other than the address you sent this
request from, you may specify `address= $<$ ADDRESS $>$ ' (no
brackets around the email address, and no quotes!)
* who [ $<$ PASSWORD $>$ ] [address= $<$ ADDRESS $>$ ]
+ See everyone who is on this mailing list. The roster is
limited to list members only, and you must supply your
membership password to retrieve it. If you're posting from an
address other than your membership address, specify your
membership address with `address= $<$ ADDRESS $>$ ' (no
brackets around the email address, and no quotes!)
2 Member options quick reference
* set help
+ Show this detailed help.
* set show [address= $<$ ADDRESS $>$ ]
+ View your current option settings. If you're posting from an
address other than your membership address, specify your
membership address with `address= $<$ ADDRESS $>$ ' (no
brackets around the email address, and no quotes!).
* set authenticate $<$ PASSWORD $>$ [address= $<$ ADDRESS $>$ ]
+ To set any of your options, you must include this command
first, along with your membership password. If you're posting
from an address other than your membership address, specify
your membership address with `address= $<$ ADDRESS $>$ ' (no
brackets around the email address, and no quotes!).
* set ack on
set ack off
+ When the `ack' option is turned on, you will receive an
acknowledgement message whenever you post a message to the
list.
* set digest plain
set digest mime
set digest off
+ When the `digest' option is turned off, you will receive
postings immediately when they are posted. Use `set digest
plain' if instead you want to receive postings bundled into a
plain text digest (i.e. RFC 1153 digest). Use `set digest
mime' if instead you want to receive postings bundled together
into a MIME digest.
* set delivery on
set delivery off
+ Turn delivery on or off. This does not unsubscribe you, but
instead tells Mailman not to deliver messages to you for now.
This is useful if you're going on vacation. Be sure to use
`set delivery on' when you return from vacation!
* set myposts on
set myposts off
+ Use `set myposts off' to avoid receiving copies of messages
you post to the list. This has no effect if you're receiving
digests.
* set hide on
set hide off
+ Use `set hide on' to conceal your email address when people
request the membership list.
* set duplicates on
set duplicates off
+ Use `set duplicates off' if you want Mailman not to send you
messages if your address is explicitly mentioned in the To: or
Cc: fields of the message. This can reduce the number of
duplicate postings you will receive.
* set reminders on
set reminders off
+ Use `set reminders off' if you want to disable the monthly
password reminder for this mailing list.
About this document ...
GNU Mailman - List Member Manual, January 11, 2020, Release 2.1
This document was generated using the LaTeX2HTML translator.
LaTeX2HTML is Copyright © 1993, 1994, 1995, 1996, 1997, Nikos Drakos,
Computer Based Learning Unit, University of Leeds, and Copyright ©
1997, 1998, Ross Moore, Mathematics Department, Macquarie University,
Sydney.
The application of LaTeX2HTML to the Python documentation has been
heavily tailored by Fred L. Drake, Jr. Original navigation icons were
contributed by Christopher Petrilli.
__________________________________________________________________
Previous Page Up one Level Next Page GNU Mailman - List Member Manual
__________________________________________________________________
Release 2.1, documentation updated on January 11, 2020.
wget 'https://lists2.roe3.org/mdrone/doc/mysqli-notes.txt'// dbconnect.php script
<?php
$conn=mysqli_connect("localhost","mdrone","einstein","databasename");
if (mysqli_connect_errno()) {
echo "Failed to connect to MySQL: " . mysqli_connect_error();
exit();
}
?>
$lastname = mysqli_real_escape_string($conn, $lastname);
$safe_variable = mysqli_real_escape_string($_POST["user-input"], $conn);
mysqli_query($conn, "INSERT INTO table (column) VALUES ('" . $safe_variable . "')");S
// Use the following as replacements for the common mysql_query,
// mysql_num_rows, mysql_fetch_array and/or mysql_fetch_assoc functions
$result = mysqli_query($conn,$query);
$numrows = mysqli_num_rows($result);
while ($row = mysqli_fetch_array($result, MYSQLI_ASSOC)) {
S}
// Function to replace the mysql_result function :: place at top of script
function mysqli_result($res,$row=0,$col=0){
$numrows = mysqli_num_rows($res);
if ($numrows && $row <= ($numrows-1) && $row >=0){
mysqli_data_seek($res,$row);
$resrow = (is_numeric($col)) ? mysqli_fetch_row($res) : mysqli_fetch_assoc($res);
if (isset($resrow[$col])){
return $resrow[$col];
}
}
return false;
}
// Function to replace mysql_field_name :: place at top of script
function mysqli_field_name($result, $field_offset)
{
$properties = mysqli_fetch_field_direct($result, $field_offset);
return is_object($properties) ? $properties->name : false;
}
<?php
$conn = mysqli_connect("localhost", "mdrone", "einstein", "database");
// Check connection
if (mysqli_connect_errno()) {
echo "Database connection failed.";
}
$firstname = "Robert'O";
$lastname = "O'Connell";
// Remove the special characters from the
// string using mysqli_real_escape_string
$lastname_escape = mysqli_real_escape_string($conn, $lastname);
$firstname_escape = mysqli_real_escape_string($conn, $firstname);
$sql="INSERT INTO Persons (FirstName, LastName) VALUES ('$firstname', '$lastname')";
if (mysqli_query($conn, $sql)) {
// Print the number of rows inserted in the table, if insertion is successful
printf("%d row inserted.\n", $mysqli->affected_rows);
}
// reduce the likelihood of SQL injection from the URL
$maxLen = 5;
$jcode = substr($_REQUEST['jcode'],0,$maxLen);
$jcode = mysqli_real_escape_string($conn,$jcode);
$maxLen = 4;
$id = substr($_REQUEST['id'],0,$maxLen);
$id = mysqli_real_escape_string($conn,$id);
?>
PDO
$stmt = $pdo->prepare('SELECT * FROM employees WHERE name = :name');
$stmt->execute([ 'name' => $name ]);
foreach ($stmt as $row) {
// Do something with $row
}