Mailman 3 March 2000 - Mailman-Users

HTML-Mails
by Roland Scheike March 27, 2000

March 27, 2000

Hi, is there any possibility to automatically convert HTML-messages to plain-text? Or: How could I block HTML-Mails? Please answer with a copy to PM. Thanks a lot from germany, Roland

3 2

Subscriber e-mail address not recognized?
by Kevin N. Carpenter March 27, 2000

March 27, 2000

I'm using Mailman 1.1 under Redhat Linux 6.1 and have a problem with a couple of addresses in a subscription list: The addresses appear to be fine, but Mailman is forcing post from a couple of the addresses to be approved. Most of the addresses in the list work great. I've tried removing and re-adding them to no avail. Any suggestions? Kevin C.

2 1

Virtual Domains
by Sergio A. Murillo March 26, 2000

March 26, 2000

I've been trying to configure Mailman to work with a virtual domain on a web server with serveral virtual domains. I read William R. Dickson sugestion of installing a copy of mailman for each of the virtual domains. How do i do this?/?? I've been traying all week now and still no luck... This is what I have. BTW my server is a Redhat 6.1 Pro with SecureWeb 3.01 apples.com has mailing lists (which works fine). This domain is the "main domain" (not a virtual domain) The Root directory is /www/… [View More]

4 4

Re: [Mailman-Users] Re: [Mailman-Users] Does Mailman support local characters=?iso-8859-1?q?_like=E5=E4=F6=C5=C4=D6?=
by Matthias Andree March 26, 2000

March 26, 2000

Ralf Hildebrandt <R.Hildebrandt(a)tu-bs.de> writes: > 1) In the archive -- it really sucks there > 2) When approving via the web interface -- I just cannot properly read the > mail I'm supposed to aceept/reject. I'm currently filtering mailman input through emil to force things to use Content-Transfer-Encoding: 8bit and charset=iso-8859-1, which gets things right for me if it's not about attachments. This, however, imposes the risk of trashing those "high characters" (with … [View More]

1 0

[ANNOUNCE] Mailman 2.0 beta 1
by Barry A. Warsaw March 25, 2000

March 25, 2000

I've just uploaded the Mailman 2.0 beta 1 tarball to www.list.org. I decided to name the new version "2.0" because of the architectural changes that have been made. See the excerpt from the NEWS file below for details of what's changed since version 1.1. Two important things to take note of. You will need Python 1.5.2 to run this version of Mailman. Also, if you are upgrading from Mailman 1.x you will need to read the UPGRADING file for instructions. I don't plan to make wider release … [View More]announcements until 2.0 final is ready to go, but I also don't expect the beta cycle to be very long. We'll see! Enjoy, -Barry -------------------- snip snip -------------------- - A new bundled auto-responder has been added. You can now configure an autoresponse text for each list's primary addresses: listname(a)yourhost.com -- the general posting address listname-request@... -- the automated "request bot" address listname-admin@... -- the human administrator address - The standard UI now includes three logos at the bottom of the page: Dragon's Mailman logo, the Python Powered logo, and the GNU logo. All point to their respective home pages. - It is now possible to set the Reply-To: field on lists to an arbitrary address. NOTE: Reply-To: munging is generally considered harmful! However for some read-only lists, it is useful to direct replies to a parallel discussion list. - There is a new message delivery architecture which uses a pipeline processor for incoming and internally generated messages. Mailman no longer contains a bundled bulk-mailer; instead message delivery is handled completely by the MTA. Most MTAs give a high enough priority to connections from the localhost that mail will not be lost because of system load, but this is not guaranteed (or handled) by Mailman currently. Be careful also if your smtpd is on a different host than the Mailman host. In practice, mail lossage has not be observed. For this reason cron/run_queue is no longer needed (see the UPGRADING file for details). Also, you can choose whether you want direct smtp delivery, or delivery via the command line to a sendmail-compatible daemon. You can also easily add your own delivery module. See Mailman/Defaults.py for details. - A similar pipeline architecture for the parsing of bounce messages has been added. Most common bounce formats are now handled, including Qmail, Postfix, and DSN. It is now much easier to add new bounce detectors. - The approval pending architecture has also been revamped. Subscription requests and message posts waiting for admin approval are no longer kept in the config.db file, but in a separate requests.db file instead. - Finally made consistent the use of Sender:/From:/From_ in the matching of headers for such things as member-post-only. Now, if USE_ENVELOPE_SENDER is true, Sender: will always be chosen over From:, however the default has been changed to USE_ENVELOPE_SENDER false so that From: is always chosen over Sender:. In both cases, if no header is found, From_ (i.e. the envelope sender is used). Note that the variable is now misnamed! Most people want From: matching anyway and any are easily spoofable. - New scripts bin/move_list, bin/config_list - cron/upvolumes_yearly, cron/upvolumes_monthly, cron/archive, cron/run_queue all removed. Edit your crontab if you used these scripts. Other scripts removed: contact_transport, deliver, dumb_deliver. - Several web UI improvements, especially in the admin page. - Remove X-pmrqc: headers to prevent return reciepts for Pegasus mail users. - Security patch when using external archivers. - Honor "X-Archive: No" header by not putting this message in the archive. - Changes to the log file format. - The usual bug fixes. [View Less]

8 13

Does Mailman support local characters like åäöÅÄÖ
by Hans Lohmander March 25, 2000

March 25, 2000

Does Mailman handle quoted printable in a good way? Characters like åäöÅÄÖ /Hans -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Hans Lohmander -- Sigma Exallon Information AB Internet & Intranet solutions Talkto:+46 (0)40 247636 Faxto:+46 (0)40 24 99 50 Mobile# +46 (0)709-898636 mailto:hans.lohmander@ei.sigma.se http://www.ei.sigma.se/ ICQ# 9319123 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

3 4

error in logs/error
by Ron Echeverri March 25, 2000

March 25, 2000

I am repeatedly seeing this pop up in $MAILMAN/log/error: Mar 24 15:38:21 2000 post: Traceback (innermost last): post: File "/home/mailman/Mailman/Archiver/Archiver.py", line 236, in ArchiveMail post: h = HyperArch.HyperArchive(self) post: File "/home/mailman/Mailman/Archiver/HyperArch.py", line 543, in __init__ post: database=HyperDatabase.HyperDatabase(maillist.archive_dir())) post: File "/home/mailman/Mailman/Archiver/pipermail.py", line 179, in __init__ post: d=pickle.… [View More]

1 0

Re: [Mailman-Users] 2.0beta1 test failure
by nbecker＠fred.net March 25, 2000

March 25, 2000

>>>>> "Jose" == Jose Roberto B de A Monteiro <betoes(a)igbt.sel.eesc.sc.usp.br> writes: >> After upgrading 1.1-2.0b1, I tried to send mail to test. Here's the >> bounce I got. Any ideas? >> >> This message was created automatically by mail delivery software. >> >> A message sent by >> >> <nbecker(a)hns.com> >> >> could not be delivered to all of its recipients. … [View More]

1 0

MailMan on Mac OS X 1.2 (Rhapsody)?
by Dave Otto March 25, 2000

March 25, 2000

Has anyone successfully compiled MailMan on Mac OS X 1.2? Dave Otto

1 0

weird problem
by Doug Hughes March 25, 2000

March 25, 2000

I have a machine running debian potato at the very latest patch level (apt upgrade) with mailman 1.1-4. I have python-base 1.5.2-9 (incidentally, I think it's time somebody removed the dependency on libdb1.85 which no longer exists (now called libdb1-1.85 *sigh*). I go to admin page.. enter list password. I'm in. Click on a section, back to password.. back in. Every single thing I click on, sends me back to re-enter the password. I also cannot change the password. I know it's not my browser … [View More]

1 1