Mailman 3 June 2005 - Mailman-Users

Getting a single list of all members?
by Paul Hoffman 22 Jun '05

22 Jun '05

Greetings. I didn't see this in the FAQ, although I'm surprised it isn't more frequently asked. Under 2.1.5, is there a way to see the whole list of users at once, instead of by first letter of their name? If not, is there a way of telling the admin interface to gang more letters together in the display?

2 2

Two questions about Mailman
by Michael Linval 22 Jun '05

22 Jun '05

Testing out Mailman to replace our old Majordomo lists. 1. When sending out digests it places all the messages into attachments instead of in the body of the message. Is this my email system or is it Mailman? I am running on Redhat Enterprise 3 system. 2. I dont want passwords for each subscriber. In fact I dont want the subscribers to even know about the web interface. How do I subscribe people without the use of passwords? Thanks

3 2

Member cannot post
by PeteBell 22 Jun '05

22 Jun '05

I have a member whose emails to my list address are being returned to him with the following message... > Remote host said: 550 Administrative prohibition I have NOT blocked his address and there doesn't seem to be anything wrong, or wrongly setup, with his subscription. What possible reasons could there be for this, where do I look for any clues (I do NOT have access to the installation), and how is it rectified? Cheers Pete Bell, UK

2 1

Postfix, Amavis and mailhost
by Jan Kohnert 22 Jun '05

22 Jun '05

Hello, I'm using Mailman and Postfix with Amavis and it works quite good. But I have one performance problem: If a message arrives at my server, it is checked by amavis. If the recipient is the list, it it passed to mailman, which the message puts back to postfix and then it is checked twice by amavis... So my question: Is it possible to tell mailman to deliver to the postfix instance, which delivers finally? Something like adding the port of my final delivery instance to the mailhost variable (mail.relay.tld:Port instead of mail.relay.tld)? TIA Best regards Jan -- OpenPGP Public-Key Fingerprint: 0E9B 4052 C661 5018 93C3 4E46 651A 7A28 4028 FF7A

3 2

Privacy options
by kalin mintchev 21 Jun '05

21 Jun '05

hi all... i just upgraded to 2.1.5... in the 2.0.... version i had before in the Privacy options there was a setting for every single message to be approved - doesn't matter if the member was new or not. now i can't find this... i see that there is a way to turn that behavior for posts per member but that means that i'd have to do it one by one?!? can i do that for all the members at once in 2.1.5? looked at the bin but nothing looked like it... thanks...

3 3

sender restrictions
by Jardar Eggesbø Abrahamsen 21 Jun '05

21 Jun '05

I want to deny a certain local user (testbrukar) the ability to send e-mail to destinations outside the local domain. I have tried this: http://www.postfix.org/RESTRICTION_CLASS_README.html The result here is exactly the same as when I tried to deny the user _all_ sending abilities (using check_sender_access only, without any smtpd_restriction_classes): If I telnet to port 25, access is denied to the sender. But if the user uses pine, the e-mail is accepted Examples from the configuration where the user "testbrukar" is allowed to send e-mail to his own domain but not to other domains: With pine: Jun 21 22:34:59 ludde postfix/smtpd[15600]: connect from localhost[127.0.0.1] Jun 21 22:34:59 ludde postfix/smtpd[15600]: 3BE72FA10: client=localhost[127.0.0.1] Jun 21 22:34:59 ludde postfix/cleanup[15597]: 3BE72FA10: message-id=<Pine.LNX.4.62.0506212234440.15567(a)ludde.domain.tld> Jun 21 22:34:59 ludde postfix/qmgr[15594]: 3BE72FA10: from=<testbrukar(a)domain.tld>, size=1099, nrcpt=1 (queue active) Jun 21 22:34:59 ludde postfix/smtpd[15600]: disconnect from localhost[127.0.0.1]Jun 21 22:34:59 ludde amavis[15549]: (15549-01) Passed CLEAN, <testbrukar(a)domain.tld> -> <jardar(a)otherdomain.tld>, Message-ID: <Pine.LNX.4.62.0506212234440.15567(a)ludde.domain.tld>, Hits: -1.25, 2162 ms With telnet localhost 25: Jun 21 22:35:55 ludde postfix/smtpd[15614]: connect from localhost[127.0.0.1] Jun 21 22:36:16 ludde postfix/smtpd[15614]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 554 <testbrukar(a)domain.tld>: Sender address rejected: Access denied; from=<testbrukar(a)domain.tld> to=<jardar(a)otherdomain.tld> proto=SMTP helo=<localhost> postconf -n: alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases command_directory = /usr/sbin/ config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix debug_peer_level = 2 disable_vrfy_command = yes html_directory = /usr/doc/postfix-2.2.3/html mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/man mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, www.$mydomain, 127.0.0.1 mydomain = domain.tld myhostname = ludde.domain.tld mynetworks_style = host myorigin = $mydomain newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/doc/postfix-2.2.3/README_FILES recipient_delimiter = + relayhost = sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_client_restrictions = permit_mynetworks, reject_unauth_pipelining, check_sender_access hash:/etc/postfix/sender_ikkje_rbl, reject_rbl_client cbl.abuseat.org, reject_rbl_client opm.blitzed.org, reject_rbl_client list.dsbl.org, reject_rbl_client combined.njabl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client rbl-plus.mail-abuse.org, reject_rbl_client relays.ordb.org, check_client_access hash:/etc/postfix/client_access permit smtpd_error_sleep_time = 10 smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, reject_unauth_pipelining, check_helo_access hash:/etc/postfix/helo_checks, permit smtpd_recipient_restrictions = check_sender_access hash:/etc/postfix/restricted_senders permit_mynetworks, reject_unauth_destination, reject_non_fqdn_recipient, check_recipient_access hash:/etc/postfix/recipient_access check_policy_service inet:127.0.0.1:10023 permit smtpd_restriction_classes = local_only smtpd_sender_restrictions = reject_unknown_sender_domain, reject_non_fqdn_sender, permit smtpd_soft_error_limit = 1 transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550

1 1

Re: [Mailman-Users] Need assistance trouble shooting problem after moving Mailman from one box to another
by Thomas Waters 21 Jun '05

21 Jun '05

On Jun 21, 2005, at 2:10 PM, JC Dill wrote: > What about alises? There are no aliases > > >> edit mm_cfg.py to show correct host name >> ran fix_url.py although told me to run as bin/withlist -l -r >> fix_url listname >> >> This appeared to all run successfully. >> What to do next? >> > > Look at the list archives. > > If the message makes it to the archive, then mailman is getting the > message, so the problem would be with mailman sending the message > back out. They do not get to the archives. I think maybe I have a permissions problem with the transferred files. I;'m looking at that first. > Check to make sure the new mailman server has permission to send > thru your mail server etc. > > If the message doesn't get to the archives then the problem is with > the message getting to mailman, or with mailman processing the > message on the incoming side, e.g. broken alises not delivering the > mail to mailman or mailman treating the message as spam and > discarding it. > > Also look at the mailman logs and the mail server logs. > >

2 1

character errors
by Jean Touma 21 Jun '05

21 Jun '05

hello all, i am using the english language and all messages go using plain text using english font as well and some email addesses bounced and the bounced message says "The user does not accept email in non-Western (non-Latin) character sets." any help? thx PS I am using mailman 2.1.5

2 1

personolized email address
by Jean Touma 21 Jun '05

21 Jun '05

Hello all, Actually i do know how to personolize the header and the footer of the messages through none digest option but i didn't find how to personolize the email address sent to, most of the email filters are rejecting the messages or transferring them to the junk and bulk email folders and the only way to get rid of that is to presonolise the email address in stead of sending all emails to list(a)mydomain.com it should be going to subsrciberemail(a)hisdomain.com, subsrciberemail1(a)hisdomain.com, subsrciberemail2(a)hisdomain.com, subsrciberemail3(a)hisdomain.com etc... i am using mailman 2.1.5 thank you in advance

2 1

Need assistance trouble shooting problem after moving Mailman from one box to another
by Thomas Waters 21 Jun '05

21 Jun '05

I posted last week before moving our distribution lists from a Panther Server (Mailman 2.1.3) to Tiger Server (Mailman 2.1.5). Instructioins, esp those from Mark Sapiro were very helpful. I was able to move the lists, and the archives. Everything in the OS X Server Admin UI looks fine and the Mailman Web UI looks fine. I can add members, delete members. But none of the transfered lists appear to work- mail sent to any of them seems lost. I can add a new list, add members, and that list works fine, so Mailman is functioning. On the transfered lists- I did these steps: Stop mailman on old server Stop mailman on new server copy lists and archives edit mm_cfg.py to show correct host name ran fix_url.py although told me to run as bin/withlist -l -r fix_url listname This appeared to all run successfully. What to do next? Thx, NOTE: new email address -- Thomas Waters Director of Information and Communication Services University of Pittsburgh School of Pharmacy 412-383-7471 waterstc(a)pitt.edu http://www.pharmacy.pitt.edu

1 0