I want all mails sent to the list to come from the list's email address...
But, in this case, if the user forgets to sign their name at the
bottom of their mail body, effectively the mail to the list is
anonymous...!
Is there a way to add the user name (or email address) to the top of
each mail so that the mails have the name of the sender, while the
mail itself comes from the list address?
I have looked high and low for an answer, but noone seems to have the solution.
Thank you!
Mal
Hi - I have searched FAQ and archives to find an answer. Hoping you can
help.
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
plain text.
QUESTIONS:
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
Thanks -
Steve
When authorizing a moderated list posting is it possible to change the
date/time on the outgoing authorized list message to the time it was
approved instead of the message showing the time it was first received
by mailman?
Thanks
Paul
Mailman 2.1.5 on RedHat Linux -
How can I set up a new list that sends to multiple existing lists - but
only sends one message to each person - even if the person is a member
of multiple lists?
a. LSOFT calls this a "superlist"
b. Can "Mailman" do this?
c. In this case, we have a system newsletter that will be sent to
multiple lists. I'd like people to receive the message only once, even
if they are on more than one of the lists included in the mailing.
Thank you,
Sandi Gruver
Unix system administrator
Center for Information Services
Bellevue, WA 98004
phone 425.803.9753
fax 425.803.9652
OK,
I've got another problem with Qmail/Plesk/Mailman (same customer,
rebuilt server). Plesk is 7.5.4 reloaded.
Mail delivered fails with "need GID 110 got 101" error. I set up the
brute-force wrapper to deliver with GID 110, and set the permissions
correctly for it to work. Now, I'm getting the following (broken up
into multiple lines for courtesy):
qmail: 1157518628.995172 delivery 726: success:
group_mismatch_error._Mailman_expected_the_mail_wrapper_script_to_be/
executed_as_one_of_the_following_groups:/[mail,_nobody,_mailman],/
but_the_system's_mail_server_executed_the_mail_script_as_group:_"popuser"./
Try_tweaking_the_mail_server_to_run_the_script_as_one_of_these_groups:/
[mail,_nobody,_mailman],/or_re-run_configure_providing_the_
command_line_option:/'--with-mail-gid=popuser'./Failed_to_start_
/usr/lib/mailman/mail/mailman./did_0+0+1/
I'm about ready to pull my hair out. I even added the popuser user to
the mailman group in /etc/passwd.
So, that being said, are there any ideas out there? I have been
messing with this for a week, and have not come up with anything else
to do.
--
Douglas G. Phillips
Simple Business Solutions
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Hi all,
I need to migrate lists from an *old* Slackware system running MM 2.0
(0x200000f0) to a new system where MM is installed via RPM (2.1.9).
I've read the posts linked to by the FAQ, and the basic procedure is to
copy the data, lists, and archives directories and run withlist
fix_url. But I have a couple of minor questions:
According to the UPGRADE document, file formats have changed as have
actual files (some new, some gone). What triggers the 2.1 version to do
the necessary conversions ? Is it just finding files of the old version
and recognizing them as such ? Does the last_mailman_version in the
data directory trigger this ?
There are various minor concerns, such as file permissions, aliases,
redoing public archive symlinks, and so forth. This made me wonder if
it would be easier/possible to run bin/newlist for each existing 2.0
list in the 2.1.9 system, and *then* bring over the data, lists, and
archives/private directories. Advisable ?
TIA
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am happy to announce the first beta release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for two new language translations, Hebrew and Slovak and a few new features.
Mailman is free software for managing email mailing lists and e-
newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.
For more information, including download links, please see:
http://www.list.orghttp://mailman.sf.nethttp://www.gnu.org/software/mailman
Special thanks are due to Barry Warsaw and Tokio Kikuchi for much coding
and support, Moritz Naumann for help with security issues and Jim Tittsler
for a significant patch.
Here's a list of the major changes.
Security
- The 2.1.9 fixes for CVE-2006-3636 have been enhanced. In particular,
many potential cross-site scripting attacks have are now detected in
editing templates and updating the list's info attribute via the web
admin interface. Thanks again to Moritz Naumann for assistance with
this.
New Features
- Changed cmd_who.py to list all members if authorization is with the
list's admin or moderator password and to accept the password if the
roster is public. Also changed the web roster to show hidden members
when authorization is by site or list's admin or moderator password
(1587651).
- Added the ability to put a list name in accept_these_nonmembers
to accept posts from members of that list (1220144).
- Added a new 'sibling list' feature to exclude members of another list
from receiving a post from this list if the other list is in the To: or
Cc: of the post or to include members of the other list if that list is
not in the To: or Cc: of the post (Patch ID 1347962).
- Added the admin_member_chunksize attribute to the admin General Options
interface (Bug 1072002, Partial RFE 782436).
Internationalization
- Added the Hebrew translation from Dov Zamir. This includes addition of
a direction ('ltr', 'rtl') to the LC_DESCRIPTIONS table. The
add_language() function defaults direction to 'ltr' to not break
existing mm_cfg.py files.
- Added the Slovak translation from Martin Matuska.
- --
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD4DBQFHVjjPVVuXXpU7hpMRArQHAJ9NE4Fj8b2rpWaXX6+BFa27wWB2MACWIGqJ
1wxPhA7ZBRVG9gSiEhTb2A==
=vzXz
-----END PGP SIGNATURE-----
I have a group of Mailman lists that I moved to a new server. When I run
genaliases, it is correctly creating the aliases but not the entries in
virtual-mailman.
I made the move and ran "withlist -l -r fix_url [listname]" for each list,
but Mailman is still not creating the virtual entries.
Thanks for any help.
--Richard
So all of a sudden my mailman ( version 2.1.9 ) quit working, returning
mail posted to lists with the error
|/local/mailman/teamnet/mail/mailman post fot". Command output: Name
"main::debugfile" used only once: possible typo at /local/majordomo/demime
line 280. -p on unopened filehandle _PATH_LOG at /local/majordomo/demime
line 176. Traceback (most recent call last): File
"/local/mailman/teamnet/scripts/post", line 69, in ? main() File
"/local/mailman/teamnet/scripts/post", line 64, in main tolist=1,
_plaintext=1) File "/local/mailman/teamnet/Mailman/Queue/Switchboard.py",
line 132, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 28] No
space left on device:
'/local/mailman/teamnet/qfiles/in/1201797128.5856061+c48d781397b95ac8800fb85d888303428baf86e1.pck.tmp'
But there IS space on the disk. Root and regular users can create new files just
fine, but mailman can't. Any clue as to where to look for the culprit, and why
it would just start happening?
mjb.
At 07:28 PM 1/30/2008, you wrote:
>Did it?
>
>--
>Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>San Francisco Bay Area, California better use your sense - B. Dylan
>
Sorry for not getting back to you, I've been unusually busy. Yes, it
did. Thanks.
