Mailman 3 June 2008 - Mailman-Users

newlist list creation error
by Vidiot 30 Jun '08

30 Jun '08

To wit: ./bin/newlist mailman Traceback (most recent call last): File "./bin/newlist", line 99, in <module> from Mailman import mm_cfg File "/usr/local/mailman/Mailman/mm_cfg.py", line 45, in <module> DEFAULT_URL_HOST = mrvideo.vidiot.com NameError: name 'mrvideo' is not defined OK, where is it supposed to be defined? I really want it to be just vidiot.com. But that didn't work either, with the error replacing mrvideo with vidiot. MB -- e-mail: vidiot(a)vidiot.com /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email

3 4

exim testing error
by Vidiot 30 Jun '08

30 Jun '08

Mark Sapiro responded: >Also note in the howto, the following > > # Domains that your lists are in - colon separated list > # you may wish to add these into local_domains as well > domainlist mm_domains=list.example.com I have the following set in my configure: domainlist mm_domains=vidiot.com domainlist local_domains = vidiot.com The 2nd was already in the configure file. >and the reference to > > domains = +mm_domains > >in the router definition. This is alluded to much more subtly in sec >6.2.1 of the manual. Section 6.2.1 doesn't exist. But I have the following: begin routers mailman_router: driver = accept domains = +mm_domains require_files = MM_LISTCHK [...] I get the following error when I try and test: /usr/exim/bin/exim -bt testlist-users 2008-06-29 20:53:47 Exim configuration error in line 563 of /usr/exim/configure: option setting expected: {eq{$sender_host_address}{::1}}}{yes}{no}} It didn't complain about this line: condition = ${if or{{eq{$sender_host_address}{127.0.0.1}} So, I'm guessing it isn't complaining about $sender_host_address, instead it is complaining about the {::1} part. My complete configure file is below, less comments and blank lines. I'd say about half of the configuration is mailman related :-) MB -- e-mail: vidiot(a)vidiot.com /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email MM_HOME=/usr/local/mailman MM_WRAP=MM_HOME/mail/mailman MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck MM_USER=mailman MM_GROUP=mailman domainlist mm_domains=vidiot.com domainlist local_domains = vidiot.com domainlist relay_to_domains = hostlist relay_from_hosts = 127.0.0.1 : mrvideo.vidiot.com acl_smtp_rcpt = acl_check_rcpt acl_smtp_data = acl_check_data never_users = root host_lookup = * rfc1413_hosts = * rfc1413_query_timeout = 5s ignore_bounce_errors_after = 2d timeout_frozen_after = 7d begin acl acl_check_rcpt: accept hosts = : accept hosts = 127.0.0.1 deny message = Restricted characters in address domains = +local_domains local_parts = ^[.] : ^.*[@%!/|] deny message = Restricted characters in address domains = !+local_domains local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./ accept local_parts = postmaster domains = +local_domains endpass message = unknown user verify = recipient require verify = sender accept hosts = +relay_from_hosts control = submission accept authenticated = * control = submission require message = relay not permitted domains = +local_domains : +relay_to_domains require verify = recipient warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes condition = \ ${if and {{match{$local_part}{(.*)-bounces\+.*}} \ {exists {MM_HOME/lists/$1/config.pck}}} \ {yes}{no}} deny message = "Recipient never sends mail so cannot cause bounces" senders = : domains = +mm_domains condition = ${if exists{MM_LISTCHK} {yes}{no}} deny message = "Recipient never sends mail so cannot cause bounces" senders = : domains = +mm_domains local_parts = \N^.*-(admin|join|leave|owner|request)$\N deny message = "Recipient never sends mail so cannot cause bounces" senders = : domains = +mm_domains local_parts = \N^.*-(subscribe|unsubscribe)$\N accept condition = \ ${if and {{match{$local_part}{(.*)-bounces\+.*}} \ {exists {MM_HOME/lists/$1/config.pck}}} \ {yes}{no}} deny !local_parts = *-bounces : *-bounces+* !verify = sender/callout=30s,defer_ok accept acl_check_data: deny !condition = $header_X-WhitelistedRCPT-nohdrfromcallback: !verify = header_sender/callout=90s accept begin routers mailman_router: driver = accept domains = +mm_domains require_files = MM_LISTCHK local_part_suffix_optional local_part_suffix = -admin : \ -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -owner : -request : \ -subscribe : -unsubscribe transport = mailman_transport mailman_verp_router: driver = dnslookup condition = ${if or{{eq{$sender_host_address}{127.0.0.1}} {eq{$sender_host_address}{::1}}}{yes}{no}} domains = !+local_domains:!+mm_domains ignore_target_hosts = <; 0.0.0.0; \ 64.94.110.11; \ 127.0.0.0/8; \ ::1/128;fe80::/10;fe \ c0::/10;ff00::/8 senders = "*-bounces@*" transport = mailman_verp_smtp dnslookup: driver = dnslookup domains = ! +local_domains transport = remote_smtp ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 no_more system_aliases: driver = redirect allow_fail allow_defer data = ${lookup{$local_part}lsearch{/etc/aliases}} file_transport = address_file pipe_transport = address_pipe userforward: driver = redirect check_local_user file = $home/.forward no_verify no_expn check_ancestor file_transport = address_file pipe_transport = address_pipe reply_transport = address_reply localuser: driver = accept check_local_user transport = local_delivery cannot_route_message = Unknown user begin transports mailman_transport: driver = pipe command = MM_WRAP \ '${if def:local_part_suffix \ {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \ {post}}' \ $local_part current_directory = MM_HOME home_directory = MM_HOME user = MM_USER group = MM_GROUP mailman_verp_smtp: driver = smtp return_path = \ ${local_part:$return_path}+$local_part=$domain@${domain:$return_path} max_rcpt = 1 headers_remove = Errors-To headers_add = Errors-To: ${return_path} remote_smtp: driver = smtp local_delivery: driver = appendfile file = /var/mail/$local_part delivery_date_add envelope_to_add return_path_add address_pipe: driver = pipe return_output address_file: driver = appendfile delivery_date_add envelope_to_add return_path_add address_reply: driver = autoreply begin retry begin rewrite begin authenticators

2 1

make install failure
by Vidiot 29 Jun '08

29 Jun '08

OK, the Solaris 10 box is operational, in that root is the only user and I'm getting things up and running. While my user account exists, none of my personal stuff is there yet, as it is in a state of flux. Once I bring the system on line, then I copy over all the home directory files, etc. In the meantime, I'm getting programs like mailman up and running. I've already replaced sendmail with exim, even getting it hooked into Solaris 10 smf control. Based on the previous discussion, I've replaced the stock python 2.4.4 on the box with a freshly compiled and installed 2.5.2 version. The configure script runs without error, as does the initial make. BTW, the install manual has an error: Page 4: % cd mailman-<version> % ./configure % make install The "make install" should be just "make". Gotta make it before you can install it. :-) In any event, the following error occurs when trying to install: (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /usr/local/src/mailman-2.1.11rc2/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' MB -- e-mail: vidiot(a)vidiot.com /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email

2 5

Re: [Mailman-Users] virtual domain
by Jeffrey Goldberg 27 Jun '08

27 Jun '08

On Jun 27, 2008, at 9:25 AM, Dony Tata wrote: > I don't include doma.ac.id in DNS, must i include doma.ac.id in DNS? > doma.ac.id is virtual domain in server xxx.mod..ac.id..... If you want to people or other machines to be able to mail to @doma.ac.id, then there will need to be an MX record in DNS for doma.ac.id. The MX record can point to your server. I strongly recommend that work with someone at your university who is familiar with SMTP and DNS. You need to have some understanding of each to set up mailman and virtual domains. Cheers, -j

1 0

virtual domain
by Dony Tata 27 Jun '08

27 Jun '08

how to configure virtual domain in postfix + mailman? in my mm_cfg.py i configure like this MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['doma.ac.id','domb.ac.id'] in postfix/main.cf, configure like this virtual_alias_maps = hash:/etc/mailman/virtual-mailman alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases i have sucsess create new mailing list "abc(a)doma.ac.id " i have sucsess subscribe member,but if a member send mail to abc(a)doma.ac.id, i have got error <abd(a)doma.ac.id>"Host or domain name not found. Name service error for name=doma.ac.id type=A: Host not found> ___________________________________________________________________________ Yahoo! sekarang memiliki alamat Email baru. Dapatkan nama yang selalu Anda inginkan di domain baru @ymail dan @rocketmail. Cepat sebelum diambil orang lain! http://mail.promotions.yahoo.com/newdomains/id/

3 2

Any way to disable wrapping of the subject header?
by Adam Nielsen 27 Jun '08

27 Jun '08

Hi all, Mailman seems to like wrapping the e-mail subject when it gets too long (78 chars I think.) Because this causes problems with many common e-mail clients (Outlook, Thunderbird, etc.) is there any way to disable the wrap? The problem is that after "folding" the line (as RFC822 puts it) Mailman uses a tab character to indent the line below. The RFC states that the CRLF+whitespace combination should be replaced by just the whitespace character used - and since Mailman uses CRLF+tab, after unfolding we end up with a tab character in the middle of the e-mail subject. Thunderbird displays this using ASCII encoding (so you get a little round circle in the middle of the subject) whereas Outlook displays nothing at all (so you get people pointing out that you forgot to put a space in between those words.) Some MTAs seem to expand the tab into eight spaces, leaving a large gap in the middle of the subject instead. You can see examples of these in the messages posted to the list yesterday, e.g. "Apache,<tab>mailman and ScriptAlias - not as documented" The easiest solution (for me) would be to just disable folding of that header, or alternatively to replace the tab with a space, so that e-mail clients display a single space as originally intended by the author instead of doing something funny with the tab character. Does anyone know if there's a way to do this, or whereabouts in the code I should start looking? Thanks, Adam.

2 2

mailing list filtered as spam
by jeff zemla 27 Jun '08

27 Jun '08

Hi all, I tried searching the archives for a solution to my problem but couldn't find anything. My apologies if this has been answered 100 times before. I bought a new domain through hostgator.com and they have Mailman installed so I can set up a mailing list. I've used mailman before through my University and never had a problem with requests being filtered as spam. Basically, when I try to add an e-mail account to the mailing list, it goes into my Gmail spam box. I don't know why this would happen, as my domain has never been used for anything before, so no one could have possibly reported it as spam. The header is as follows: from: artists-request(a)domain.com to: invited(a)address.com date: Wed, Jun 25, 2008 at 2:16 PM subject: Welcome to the "Artists" mailing list mailing list: <artists_domain.com.> mailed-by: domain.com Where domain.com is my domain, artists is the name of the list, and invited(a)address.com is the person I add to the list. I have tried altering the content of the message, but nothing seems to work, which leads me to believe it is being flagged as spam based on where it originates from. But seeing as the website has no content on it (just a line of text that says "Things will be here shortly") i dont know why gmail would have a preconceived notion that it's a spamming site. Any ideas? Thanks! Jeff

4 8

Re: [Mailman-Users] mailing list filtered as spam
by Dragon 26 Jun '08

26 Jun '08

jeff zemla sent the message below at 08:05 6/26/2008: >Hi all, >I tried searching the archives for a solution to my problem but couldn't >find anything. My apologies if this has been answered 100 times before. > >I bought a new domain through hostgator.com and they have Mailman installed >so I can set up a mailing list. I've used mailman before through my >University and never had a problem with requests being filtered as spam. > >Basically, when I try to add an e-mail account to the mailing list, it goes >into my Gmail spam box. I don't know why this would happen, as my domain >has never been used for anything before, so no one could have possibly >reported it as spam. The header is as follows: > >from: artists-request(a)domain.com >to: invited(a)address.com >date: Wed, Jun 25, 2008 at 2:16 PM >subject: Welcome to the "Artists" mailing list >mailing list: <artists_domain.com.> >mailed-by: domain.com > >Where domain.com is my domain, artists is the name of the list, and >invited(a)address.com is the person I add to the list. > >I have tried altering the content of the message, but nothing seems to work, >which leads me to believe it is being flagged as spam based on where it >originates from. But seeing as the website has no content on it (just a >line of text that says "Things will be here shortly") i dont know why gmail >would have a preconceived notion that it's a spamming site. > >Any ideas? ---------------- End original message. --------------------- It is quite possible that the ISP you are using has hosted domains that were a problem and gmail is filtering on the fact that your domain is hosted in their IP address block. It is also quite possible that they are being quite draconian about the content of the message. Either way, the only way you will know for certain what is happening is if you contact their technical support (if you can actually get an answer out of them, they may well ignore your request too). Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

feature request
by Karen R McArthur 26 Jun '08

26 Jun '08

Is there a way to add the web membership management module to the moderator without giving the moderator admin web access? -- Karen R. McArthur <kmcarthu(a)bates.edu> Systems Administrator Information and Library Services, Bates College Lewiston, Maine 04240 USA ph:(207)786-8236 fax:(207)786-6057 If you find that everybody else is right and you're wrong, it might just be that you're thinking outside the box. The world is yet to catch up.

2 1

The admin web interface is not saving my changes and keeps asking me to re-enter my password
by Taner Tas 26 Jun '08

26 Jun '08

I choose same title of Mailman FAQ 4.45 which describes my problem exactly. I checked every suggestion on this FAQ but no one seems suitable for fix my problem. I need a helpful trick for tracing the connections and authentication steps on mailman. How can i use detailed debug level logging facilities of mailman, if there is something like user configurable logging options. Mailman's own error log file seems far away to get usable information at the moment. Taner

3 3