Dov Oxenberg wrote:

Hi Mark, Thanks for your prompt reply. It seems you are right on target. Below is the relevant data from my main.cf: [some hotmail running together edited below] myhostname = mydomainname.com alias_maps = hash:/etc/aliases;hash:/etc/mail/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = mydomainname.com, localhost.com, localhost relayhost = mailserver.mydomainname.com mynetworks = 127.0.0.0/8 mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = 127.0.01 all transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1

Not sure what you mean by "dbm" but my understanding is I should modify the alias_maps variable to "hash:/etc/aliases, hash:/etc/mail/aliases?"

'dbm' was an erroneous assumption on my part. You are correct. It should be

alias_maps = hash:/etc/aliases, hash:/etc/mail/aliases

What about the alias_database variable? Do I need to add "/etc/mail/" to that as well?

No.

But if you enable Mailman-Postfix integration per http://www.list.org/mailman-install/node13.html, you will need to add

hash:/usr/local/mailman/data/aliases

(or whatever the correct path is) to alias_maps as discussed in the above reference

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Dov Oxenberg wrote:

Hi, Actually this is probably the fourth or fifth time I am revisiting "Chapter 6." But I seem to be making better progress now than in my previous attempts. I am at the part where I am trying to make sure data/aliases* have the correct ownership, GID, etc. When I issue "genaliases" it seems to work...at least I get the command prompt back with no reported errors. Then, I try to do "chown mailman:mailman..." and am receiving the error message "chown: cannot access 'data/aliases*' : No such file or directory"

Have you set

MTA = 'Postfix'

in mm_cfg.py? Probably you have since genaliases would report a lot of aliases if it were the default MTA = 'Manual'.

I should point out in my installation the path to the mailman bin is /usr/lib/mailman/bin in case that makes any difference. But I thought by running the "genaliases" (from the mailman "bin" directory) the script would create the aliases for me??? Obviously I am mistaken...but what am I doing wrong now????

Assuming that you do have MTA = 'Postfix', you need to be in the right directory when you do the chown. This certainly isn't /usr/lib/mailman/bin. It may be /usr/lib/mailman/data, or something else depending on how the Mailman you are installing was configured. The name of the directory id data/ and it will be in whatever was configured as var-prefix which may be /usr/lib/mailman/ or something in /var.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Dov Oxenberg wrote:

Apparently the target files/folders on my system are under /var/lib/mailman/. So, thanks to your help I have now overcome this hurdle. And yes, I had postfix set as the value for MTA. I am now stepping through all the troubleshooting steps in the mailman FAQ here http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp as I am not able to see pending requests in the web interface and not receiving mail from the list, any kind of mail (also not seeing the logo images, just the placeholders).

Did you add hash:/var/lib/mailman/date/aliases to the alias_maps setting in your Postfix main.cf?

What is strange is that in the graphical web based administration interface to my VPS, all the permissions appear set correctly, as far as I know, on /var/lib/mailman because I am seeing list as the group and root as the user on all the directories. As far as the user, list is only on locks and qfiles. When I originally ran check_perms it returned something like 80 "errors" so I ran it again with the -f flag and am now getting 11 errors, but only in the command line! When I again run check_perms -f it still reports back the same 11 "errors" as in: /var/lib/mailman/logs bad group (has: root; expected list) (fixing) and so forth through the remaining 10 directories. I have rebooted the machine but still appear to be stuck in the loop....any ideas???

I have no idea why your file management GUI would show you one thing and check_perms something else. what does command line "ls -l" show?

Are you running check_perms as root? If so, and for whatever reason, check_perms doesn't fix it, you can always do

chgrp list /var/lib/mailman/*

Also, if your Mailman user:group is list:list, that is what you should set the user:group of /var/lib/mailman/data/aliases* to.

See the section just below the warning box at http://www.list.org/mailman-install/node10.html for some information on icons, although the default setting IMAGE_LOGOS = '/icons/' seems to be correct for many apache installations.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Dov Oxenberg wrote:

Here is the line from my main.cf: alias_maps = hash:/etc/aliases, hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases The results of my ls -l, which by the way I had looked at earlier also and neglected to mention, are illustrated in the attached screen shot. I see the system thinks the group membership is root rather than list, is that about right?

[Note: the screenshot was output from ls -l of /var/lib/mailman showing 7 actual subdirectories and 11 symlinks to to directories in other places.]

The /var/lib/mailman/* things whose ownership you can't change are symlinks to other directories. The fact that chgrp doesn't 'work' is normal because it changes the group of the target, not that of the symlink itself.

This is an unusual way of installing Mailman, but it should be OK. You can just ignore the errors from check_perms in this case. But, this all indicates your Mailman is an unusual package, so our installation manual, FAQ, etc. may not be completely relevant.

The real issue appears to be the fact that there is a /var/lib/mailman/messages directory, and it appears from its link count to have 32 subdirectories. This suggests that your package might be setup to use Mailman's 'Maildir' delivery instead of aliases (but again in a non-standard way). I'm guessing that that's where your messages are, and MaildirRunner or whatever is supposed to process them on the Mailman side is not running.

You need to do one of two things. Either, go to documentation and support resources specific to your OS and Mailman package for help, or rip it all out and install a standard Mailman distribution.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Dov Oxenberg wrote:

I think I just spent too long in front of the computer yesterday :-) Under /var/lib/mailman/messages folder are directories with what appear to be country abbreviations?

No. It is I who spent too much time doing whatever. The messages/ directory has nothing to do with Maildir. It is the normal localization message catalog. Ignore everything in my prior post about Maildir.

I am not 100% positive, but I could swear I installed mailman by running configure>make>make install

That process would not have created all those /var/lib/mailman symlinks nor would it have put the locks and logs directories in /var/lock/mailman and /var/log/mailman unless the package you configured was non-standard to begin with.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Before I go on a wild goose chase...here are the contents of my master.cf file - does this look normal? What I mean is, does it appear as though I am missing anything?

# # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - - - - smtpd #submission inet n - - - - smtpd # -o smtpd_enforce_tls=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject #smtps inet n - - - - smtpd # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject #628 inet n - - - - qmqpd pickup fifo n - - 60 1 pickup cleanup unix n - - - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - - 300 1 oqmgr tlsmgr unix - - - 1000? 1 tlsmgr rewrite unix - - - - - trivial-rewrite bounce unix - - - - 0 bounce defer unix - - - - 0 bounce trace unix - - - - 0 bounce verify unix - - - - 1 verify flush unix n - - 1000? 0 flush proxymap unix - - n - - proxymap smtp unix - - - - - smtp # When relaying mail as backup MX, disable fallback_relay to avoid MX loops relay unix - - - - - smtp -o fallback_relay= # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - - - - showq error unix - - - - - error discard unix - - - - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - - - - lmtp anvil unix - - - - 1 anvil scache unix - - - - 1 scache # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

I ran into the same problem with postfix and mailman-2.1.9-r3 on Gentoo. You are already on a wild goose chase. But that master.cf seems good. Check your postfix logs for

[local] fatal: execvp /usr/lib/mailman/mail/mailman: Permission denied

reverting to gentoo's 2.1.9 did nothing. chmod does nothing. I think my problem may be a postfix setgid problem but is more likely a more complicated system problem.

I'm solving the problem with new iron and something other than my current MTA and OS.

Dov Oxenberg wrote:

Before I go on a wild goose chase...here are the contents of my master.cf file - does this look normal? What I mean is, does it appear as though I am missing anything?

# # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - - - - smtpd #submission inet n - - - - smtpd # -o smtpd_enforce_tls=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject #smtps inet n - - - - smtpd # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject #628 inet n - - - - qmqpd pickup fifo n - - 60 1 pickup cleanup unix n - - - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - - 300 1 oqmgr tlsmgr unix - - - 1000? 1 tlsmgr rewrite unix - - - - - trivial-rewrite bounce unix - - - - 0 bounce defer unix - - - - 0 bounce trace unix - - - - 0 bounce verify unix - - - - 1 verify flush unix n - - 1000? 0 flush proxymap unix - - n - - proxymap smtp unix - - - - - smtp # When relaying mail as backup MX, disable fallback_relay to avoid MX loops relay unix - - - - - smtp -o fallback_relay= # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - - - - showq error unix - - - - - error discard unix - - - - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - - - - lmtp anvil unix - - - - 1 anvil scache unix - - - - 1 scache # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

---

Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rvaughn%40amigostecnico...

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp