headers
Mark Sapiro | 1 Jan 2011 02:20
Favicon

Re: Archives heading without domain name


"Danny hendrawan" <danny <at> puterakembara.org> wrote:

>How to set the headings as per your Searchable Archives: 
>http://www.mail-archive.com/mailman-users%40python.org/   ? i.e. only
>shows 
>member's name with domain name

Use mail-archive.com as your list's archiver.

--

-- 
Mark Sapiro - mark <at> msapiro.net

Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Permalink | Reply | 0 comments |
headers
Umarzuki Mochlis | 2 Jan 2011 15:09
Picon
Gravatar

Re: User unknown in virtual mailbox table

i set in mm_cfg.py like below

POSTFIX_STYLE_VIRTUAL_DOMAINS   = ['mail-server.mydomain.my']

from socket import *
try:
    fqdn = getfqdn()
except:
    fqdn = 'mm_cfg_has_unknown_host_domains'

DEFAULT_URL_HOST   = "mail-server.mydomain.my"
DEFAULT_EMAIL_HOST = "mail-server.mydomain.my"
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, )
MTA = 'Postfix'

and ran

# /usr/lib/mailman/bin/withlist -l -a -r fix_url
# /usr/lib/mailman/bin/genaliases

with the same result as before

postconf -n output:

alias_database = hash:/etc/postfix/aliases
alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases
allow_min_user = no
biff = no
bounce_queue_lifetime = 1d
(Continue reading)

Permalink | Reply | 17 comments |
headers
Umarzuki Mochlis | 2 Jan 2011 17:50
Picon
Gravatar

Re: User unknown in virtual mailbox table

after a check on /usr/lib/mailman/Mailman/Defaults.py

VAR_PREFIX      = '/var/lib/mailman'
DATA_DIR        = os.path.join(VAR_PREFIX, 'data')

so the /path/to/data must be /var/lib/mailman/data which led me to

1. change main.cf
-----------
alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf,
proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf,
hash:/var/lib//mailman/data/transport-mailman

2. move virtual_to_transport to /var/lib/mailman/data

3. virtual_to_transport
#!/bin/sh
sed -r -e 's/(^[^#][^ ]+[ ]+).+$/\1local/' $1 \
 > /var/lib/mailman/data/transport-mailman
/usr/sbin/postmap /var/lib/mailman/data/transport-mailman

4. ran
# postalias /var/lib/mailman/data/aliases
# postalias /etc/postfix/aliases
# service postfix reload
# /usr/lib/mailman/bin/genaliases

but virtual-mailman and transport-mailman does not appear in data folder
(Continue reading)

Permalink | Reply | 16 comments |
headers
Chris Arnold | 2 Jan 2011 20:48

List on a different domain name?

Just upgraded to 2.1.14 on sles 10 sp3 with oes2. We use to have a domain that mailman was used on, this domain
has since expired. We have a couple of other domains that I would like to use mailman on. Maybe I don't fully
understand mailman but is there a way to use mailman on other domains?
Internal users can still access the expired domain and access mailman but external users can not access
mailman from valid domains (did that make sense?).

Sent from my iPhone
Permalink | Reply | 9 comments |
headers
Mark Sapiro | 2 Jan 2011 21:30
Favicon

Re: User unknown in virtual mailbox table

Umarzuki Mochlis wrote:

>i set in mm_cfg.py like below
>
>POSTFIX_STYLE_VIRTUAL_DOMAINS   = ['mail-server.mydomain.my']
>
>from socket import *
>try:
>    fqdn = getfqdn()
>except:
>    fqdn = 'mm_cfg_has_unknown_host_domains'
>
>DEFAULT_URL_HOST   = "mail-server.mydomain.my"
>DEFAULT_EMAIL_HOST = "mail-server.mydomain.my"
>VIRTUAL_HOSTS.clear()
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, )
>MTA = 'Postfix'
>
>and ran
>
># /usr/lib/mailman/bin/withlist -l -a -r fix_url
># /usr/lib/mailman/bin/genaliases
>
>with the same result as before

This should have ensured that all lists had host_name
"mail-server.mydomain.my" and since this name is in
POSTFIX_STYLE_VIRTUAL_DOMAINS, genaliases should have created aliases
and virtual-mailman for all lists.
(Continue reading)

Permalink | Reply | 15 comments |
headers
Mark Sapiro | 2 Jan 2011 21:44
Favicon

Re: List on a different domain name?

Chris Arnold wrote:

>Just upgraded to 2.1.14 on sles 10 sp3 with oes2. We use to have a domain that mailman was used on, this domain
has since expired. We have a couple of other domains that I would like to use mailman on. Maybe I don't fully
understand mailman but is there a way to use mailman on other domains?

You can use Mailman on any number of domains. The only restriction with
standard GNU Mailman 2.1.x is tha list names must be globally unique
in the installation.

There are 3 components to this.

1) The web server must recognize the appropriate Mailman ScriptAlias,
Alias, etc. directives in all the domains.

2) The MTA must know how to deliver the mail to Mailman for all the
list addresses.

3) There should be appropriate add_virtualhost() directives and for
Postfix integration with Postfix virtual domains, appropriate
POSTFIX_STYLE_VIRTUAL_DOMAINS entries in mm_cfg.py.

See the FAQ at http://wiki.list.org/x/gIA9 for more, particularly the
part about fix_url.

>Internal users can still access the expired domain and access mailman but external users can not access
mailman from valid domains (did that make sense?).

Maybe. You need to make sure the web server will apply the Mailman
related configuration directives to the host(s) yoiu want to use.
(Continue reading)

Permalink | Reply | 8 comments |
headers
yahoo | 3 Jan 2011 05:02

A basic filtering MIME question

I've been reading the FAQ's etc and asking local advice; but I must be
doing something stoopid.

MM2.1.3 under Linux, 2.6.18-164.el5

My goal is:

a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers 
& archives.

b) /dev/null the attachments, both in delivery and archives.

FAQ 1.8 says:

> In Mailman 2.1, on the admin page, go to the Content Filtering section.
> Change "Should Mailman filter ..." to Yes. If you leave the rest at
> default values, including Yes for "Should Mailman convert text/html
> parts to plain text?", your list will only distribute plain text
> messages with no attachments.

And I did so, but I suspect that filter_mime_types &/or pass mime type 
originally had values that before/in my muddling, have been lost; both are 
empty now.

Suggestions?
Permalink | Reply | 6 comments |
headers
Jim Wright | 3 Jan 2011 07:15
Favicon

Problem with Postfix/virtual setup, unknown user

Hi, all.  I'm a new user, but I've searched the archives and so far haven't been able to find a fix for my issue. 
I've set up mailman with postfix and I'm using virtual domains.  I've created a test mailing list, and
Mailman has successfully emailed me that the list was created.  However, I cannot send email to this list
without the mail being rejected back as being to an unknown user.

Based on all of my reading, I think I've done everything correctly.  From my Postfix log, it doesn't appear
that the aliases file is being consulted at all, but I am seeing a line indicating that the virtual-mailman
file was referenced.

Here are the relevant Mailman files:

From mm_cfg.py:

# Put YOUR site-specific settings below this line.
MTA = "Postfix"
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['wrightthisway.com', 'themailshack.com']
add_virtualhost('wrightthisway.com', 'wrightthisway.com')
add_virtualhost('themailshack.com', 'themailshack.com')

sh-3.2# cat aliases
# This file is generated by Mailman, and is kept in sync with the
# binary hash file aliases.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE
# unless you know what you're doing, and can keep the two files properly
# in sync.  If you screw it up, you're on your own.

# The ultimate loop stopper address
mailman-loop: /usr/local/mailman/data/owner-bounces.mbox

# STANZA START: test
# CREATED: Sat Dec 25 18:26:51 2010
(Continue reading)

Permalink | Reply | 7 comments |
headers
Jim Wright | 3 Jan 2011 18:18
Favicon

Re: Problem with Postfix/virtual setup, unknown user

On Jan 3, 2011, at 12:15 AM, Jim Wright wrote:

> Jan  2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF:
to=<test <at> wrightthisway.com>, relay=virtual, delay=0.1, delays=0.08/0.01/0/0.02, dsn=5.1.1,
status=bounced (unknown user: "test <at> wrightthisway.com")

Hi, just a followup to my previous message, I have confirmed that the 'test' mailing list I created seems to
be listed correctly in the virtual-mailman db, using the following command:

sh-3.2# postmap -q test <at> wrightthisway.com hash:/usr/local/mailman/data/virtual-mailman
test

sh-3.2# postmap -s hash:/usr/local/mailman/data/virtual-mailman
test-confirm <at> wrightthisway.com	test-confirm
test-join <at> wrightthisway.com	test-join
test-subscribe <at> wrightthisway.com	test-subscribe
mailman-loop <at> wrightthisway.com	mailman-loop
test <at> wrightthisway.com	test
test-admin <at> wrightthisway.com	test-admin
test-bounces <at> wrightthisway.com	test-bounces
test-leave <at> wrightthisway.com	test-leave
test-owner <at> wrightthisway.com	test-owner
test-request <at> wrightthisway.com	test-request
test-unsubscribe <at> wrightthisway.com	test-unsubscribe
Permalink | Reply | 2 comments |
headers
Mark Sapiro | 3 Jan 2011 20:06
Favicon

Re: A basic filtering MIME question

yahoo <yahoo <at> 8es.com> wrote:

>I've been reading the FAQ's etc and asking local advice; but I must be
>doing something stoopid.
>
>MM2.1.3 under Linux, 2.6.18-164.el5

2.1.3? This is quite old. Current is 2.1.14.

>My goal is:
>
>a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers 
>& archives.
>
>b) /dev/null the attachments, both in delivery and archives.

filter_content - Yes
filter_mime_types - empty
pass_mime_types -
  multipart
  message/rfc822 (allows plain text and converted HTML from attached
                  messages. Remove to filter attached messages)
  text/plain
  text/html
filter_filename_extensions -
  exe bat cmd com pif scr vbs cpl
  (these are defaults - this setting doesn't exist in 2.1.3)
pass_filename_extensions - empty; default; this setting doesn't exist
  in 2.1.3)
collapse_alternatives - Yes (this setting doesn't exist in 2.1.3)
(Continue reading)

Permalink | Reply | 5 comments |

Gmane