Re: [Mailman-Users] Group mismatch returns.

[Bill Christensen]

On 10/11/11 7:01 PM, Mark Sapiro wrote:

Bill Christensen wrote:

   

Recent upgrade borked my setup.
 


[Prior posts indicate this is Mac OS 10.7 server]


   

Group Mismatch error once again, and adding the configure line

 --with-mail-gid=staff

and removing the line

 --with-mail-gid=${mmgroup}

  as suggested doesn't fix it.

What to do?  How can I keep this from happening whenever I do a major
upgrade/reinstall on my server?
 


These are really questions for Apple. I'm not aware of anyone on this
list other than you who is running Mac OS X server Mailman.


I'm using the 'client' version of Mac OSX, not the 'server' version.  
I'm not using the Apple-provided version of Mailman.  I use Macports, 
which downloads the source directly from Sourceforge/lists.org.

I think
most people have had more success by completely ripping out the
supplied Mailman and installing from source. See the FAQ at
.
   
Much of that is ancient history or relates primarily to the OSXserver 
version.


Fortunately, I figured out what the problem was.  Though I had installed 
with  --with-mail-gid=staff, I hadn't also run a check_perms -f.  That 
was apparently the missing puzzle piece.

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Remove Members waiting for Moderator Approval viaCommand Line

[Mark Sapiro]

Phil wrote:
>
>I'm trying to kill a pending subscription to a mailing list via the command
>line because the domain owner forgot to register the main domain of our site
>and we can't approve/deny membership via the web admin interface.
>
>I've tried to remove the e-mail address pending approval via the
>remove_members command and it seem to only react to active and approved
>members of a mailing list.


That's correct. remove_members only removes members. A pending
subscription is not (yet) a member.


>Is there a way to approve / deny a pending user request via shell?


Do you mean a subscription request that is waiting moderator approval
because subscribe_policy is 'Require approval' or 'Confirm and
approve' or one that is waiting user confirmation because
subscribe_policy is 'Confirm' or 'Confirm and approve'? It seems you
mean the former.

Deleting a subscription waiting approval is a multi step process with
existing tools.

First run

/path/to/mailman/bin/dumpdb /path/to/mailman/lists/LISTNAME/pending.pck

This will report something like

[- start pickle file -]
<- start object 1 ->
{   104: (   2,
 (   1318366634.8118629,
 'u...@example.com',
 'User Name',
 'tuufwuge',
 False,
 'en')),
'version': (0, 1)}
[- end pickle file -]


There may be more entries than above, but those other than

'version': (0, 1)

are all pending requests of some kind. Each will have a numeric key,
104 in the above followed by a 2-tuple consisting of a number
indicating the request type (1 for a held message, 2 for a held
subscription or 3 for a held unsubscription) and a tuple of
information the format of which depends on the type.

You are interested in type 2 as above and the information tuple is
(time stamp, e-mail address, real name, password, digest flag,
language). Find the key(s) of the one(s) you want to discard, in the
example above, 104.

Then run 

/path/to/mailman/bin/withlist -l LISTNAME

which will respond

Loading list LISTNAME (locked)
The variable `m' is the LISTNAME MailList instance
>>>

at the >>> prompts, type

>>> from Mailman.mm_cfg import DISCARD
>>> m.HandleRequest(104, DISCARD)

(Use the key from your request instead of 104 - this should not print
any error. You can repeat the above multiple times with other keys if
you have more that one request to discard.)

>>> m.Save()

(This is important to save the state of the list.)

>>>   <- at this prompt type control-D to exit which should respond
Unlocking (but not saving) list: LISTNAME
Finalizing

The discards will be logged in Mailman's vette log.

The above method can be used to discard a held message, but Mailman's
bin/discard is simpler.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Group mismatch returns.

[Mark Sapiro]

Bill Christensen wrote:

>Recent upgrade borked my setup.


[Prior posts indicate this is Mac OS 10.7 server]


>Group Mismatch error once again, and adding the configure line
>
> --with-mail-gid=staff
>
>and removing the line
>
> --with-mail-gid=${mmgroup}
>
>  as suggested doesn't fix it.
>
>What to do?  How can I keep this from happening whenever I do a major 
>upgrade/reinstall on my server?


These are really questions for Apple. I'm not aware of anyone on this
list other than you who is running Mac OS X server Mailman. I think
most people have had more success by completely ripping out the
supplied Mailman and installing from source. See the FAQ at
.

Note that making changes to configure options (at least in standard
Mailman) don't do anything unless you actually run configure and make
install.

What is your MTA? If it is Postfix and uses aliases for delivery to
Mailman, what is the owner of the aliases.db file that contains the
Mailman aliases.

What is the text of the group mismatch error message?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Merging List Administrator with List membership

[Mark Sapiro]

On 10/10/2011 7:21 PM, Syafril Hermansyah wrote:
> 
> I wish when member (who also act as List-Administrator/moderator) login
> on their membership page (http://%s/mailman/listinfo/) there is
> link to administrative page (or held page) and s/he can reach the page
> without authenticate first.
> That way any list-administrator which also member of the list only need
> to remember single password/authentication, no need to notify other
> list-administrators/moderators about new password.


The web UI will be different in MM 3 and may not work exactly as you
state above, but the function you look for will be there. No changes are
contemplated for Mailman 2.1.x.


> The list-administrative page still exist though, this page need it for
> super admin (or list maintainer) to help list administrator changes some
> setting (just in case).
> 
> And then when any list-administrator/moderators make approval (of held
> messages) or add/remove any member, there is mail notification to
> listname-owner/listname-moderators that message has been approved or new
> member has been added or membership has been removed by
> , that way other list-administrators
> know that someone has been did the job, no further action required.


These actions are currently logged, but no notices are sent. Notices
would be difficult to implement in Mailman 2.1.x because there is no
list method for notifying all owners/moderators except one.

This seems like a reasonable request for MM 3 if it isn't already planned.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Setting defaults for new mailing lists

[Mark Sapiro]

C. Marcerawrote:

>Is it possible to change the default settings for new mailing lists when you 
>create them? For example, whenever I create new lists, send_welcome_msg and 
>send_goodbye_msg are on by default. For our internal purposes, I don't 
>want/need those messages going out so I keep turning them off. I've forgotten 
>once or twice and that leads to "What's this email mean?".
>
>Is there a way to make the default setting Off instead of On?


Put

DEFAULT_SEND_WELCOME_MSG = No
DEFAULT_SEND_GOODBYE_MSG = No

in mm_cfg.py.

It would serve you well to read Defaults.py to find out what other
settings exist that you may find useful.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Integrating mailman with postfix, using virtual domains

[Mark Sapiro]

On 10/10/2011 5:40 PM, Nick Bright wrote:
> 
> I've followed the mailman documentation for integrating mailman with
> postfix, according to
> http://www.list.org/mailman-install/postfix-virtual.html as well as
> various mailing list posts on this list.
> 
> Note that I am attempting to configure a virtual_mailbox_domain with
> mailman (not a virtual_alias_domain).
> 
> mm_cfg.py contains:
> 
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['valnet.net']
> MTA = 'Postfix'
> DEFAULT_URL_HOST   = 'mail.valnet.net'
> DEFAULT_EMAIL_HOST = 'valnet.net'
> VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'valnet.net'


The above line is wrong. Normally you shouldn't need to specify
VIRTUAL_MAILMAN_LOCAL_DOMAIN at all, but if it is specified, it should
be something like 'localhost' or 'some.other.postfix.local.domain'. It
must not be the list domain because if it is it will result in
virtual-mailman mappings like

testl...@valnet.nettestl...@valnet.net

which tell Postfix to map the virtual domain address testl...@valnet.net
to the address testl...@valnet.net which is the same address and doesn't
tell Postfix what real address to actually deliver to.


[...]
> Unfortunately, when I send an email to testl...@valnet.net I receive a
> bounce back of:
> 
> : unknown user: "testl...@valnet.net"
> 
> With an associated postfix log entry of:
> 
> Oct 10 19:22:47 mail postfix/virtual[22090]: DBF7241F5F:
> to=, relay=virtual, delay=0.39,
> delays=0.36/0/0/0.03, dsn=5.1.1, status=bounced (unknown user:
> "testl...@valnet.net")


Because you are mapping testl...@valnet.net to testl...@valnet.net
instead of to testlist or testlist@localhost


> When I test the alias maps I see:
> 
> [root@mail postfix]# postmap -q testl...@valnet.net
> hash:/etc/mailman/virtual-mailman
> testlist


This is the puzzling part as it says that the mapping in virtual-mailman
is to testlist and not to testl...@valnet.net, so it should be working ???

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest Delivery question...

[Mark Sapiro]

Chuck Johnson wrote:
>
>I am curious if anyone has found a way to specify the time(s) that the digest 
>message is sent rather than depending upon a size condition being met?
>
>I'm thinking that it can be done via a cron job and a mailman command, but I'm 
>not familiar enough with the mailman specific commands to know if it is 
>possible or not.


A standard Mailman installation runs several cron jobs either via a
'system' crontab or the Mailman user's crontab. One of these jobs is
cron/senddigests which by default runs at noon for all lists.

cron/senddigests sends a digest for every list whose Digest options ->
digest_send_periodic is Yes and which has messages pending for the
digest.

If you want only periodic digests, set digest_send_periodic to Yes and
set digest_size_threshhold large enough that you don't get digests
triggered on size in between.

You can edit Mailman's crontab to run cron/senddigests on any schedule
you want, and if you want different schedules for different lists, you
can specify one or more list names for cron/senddigests with one or
more -l LISTNAME options and have multiple commands run on different
schedules for different lists.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Group mismatch returns.

[Bill Christensen]

Recent upgrade borked my setup.

Group Mismatch error once again, and adding the configure line

--with-mail-gid=staff

and removing the line

--with-mail-gid=${mmgroup}

 as suggested doesn't fix it.

What to do?  How can I keep this from happening whenever I do a major 
upgrade/reinstall on my server?

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] missing post for moderation

[Mark Sapiro]

Andrew Watson wrote:

>I have a list which has been functioning fine for many years.
>This morning I found a standard email to me, as moderator, asking that I 
>authorize a posting.
>The "Date" field says it was sent 6 hours ago.
>When I go to the administrative page, no message appears for my approval.
>If I test the system by sending a new message, it does appear in my moderator 
>queue, so
>otherwise the list appears to be working fine.
>
>How can this happen, and is there some way to find the missing message, or 
>should
>I just chalk it up to the mysteries of mailman, and ask the poster to send 
>again?


What's in Mailman's vette log? Possibly the poster cancelled it
herself. If so the disposition will be in the vette log.

If there is nothing in the vette log about either the holding or the
reject/discard of the post, check the Received: headers of the notice
to see what server it came from.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Digest Delivery question...

[Chuck Johnson]

Greetings,

I am curious if anyone has found a way to specify the time(s) that the digest 
message is sent rather than depending upon a size condition being met?

I'm thinking that it can be done via a cron job and a mailman command, but I'm 
not familiar enough with the mailman specific commands to know if it is 
possible or not.

Any input would be greatly appreciated.

Thanks!

Chuck

Chuck Johnson
Academic Software Specialist
Simpson College
Indianola, Iowa
direct: 515-961-1866 * optional: 515-961-1681
www.simpson.edu

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Invisible message for approval [SOLVED]

[Narcis Garcia - GiLUG]

Production and mirror are ready to work, and the only difference is the 
public DNS pointer. The design is planned to make only 1 change on a DNS 
record to change the role of a server.


I'll study the best point to make check if it's production or not, and 
then run crontab actions or not.


Thanks.


Al 11/10/11 21:18, En/na Mark Sapiro ha escrit:

Narcis Garcia - GiLUG wrote:


The matter I don't know how to solve is to have a mirror (available for
production) but not sending mails while doesn't become the production one.
(Server can know if it's main or mirror with a DNS query: ListServer IP
=? My IP)



Presumably, you are not actually running Mailman on the mirror. The nn
held messages waiting notices com from a Mailman cron job.  You have
several choices.

1) Don't mirror Mailman's crontab.

2) Don't run crond on the mirror server (probably the best option).

3) Update the mirror frequently enough so that changes on the
production server are reflected on the mirror before Mailman's crons
run (this won't avoid duplicate notices when there are held messages
on the production server).

4) modify Mailman's crontab to only run the jobs on the production
server.


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Invisible message for approval [SOLVED]

[Mark Sapiro]

Narcis Garcia - GiLUG wrote:
>
>The matter I don't know how to solve is to have a mirror (available for 
>production) but not sending mails while doesn't become the production one.
>(Server can know if it's main or mirror with a DNS query: ListServer IP 
>=? My IP)


Presumably, you are not actually running Mailman on the mirror. The nn
held messages waiting notices com from a Mailman cron job.  You have
several choices.

1) Don't mirror Mailman's crontab.

2) Don't run crond on the mirror server (probably the best option).

3) Update the mirror frequently enough so that changes on the
production server are reflected on the mirror before Mailman's crons
run (this won't avoid duplicate notices when there are held messages
on the production server).

4) modify Mailman's crontab to only run the jobs on the production
server.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Setting defaults for new mailing lists

[C. Marcera]

Is it possible to change the default settings for new mailing lists when you 
create them? For example, whenever I create new lists, send_welcome_msg and 
send_goodbye_msg are on by default. For our internal purposes, I don't 
want/need those messages going out so I keep turning them off. I've forgotten 
once or twice and that leads to "What's this email mean?".

Is there a way to make the default setting Off instead of On?

Thanks in advance.


Chris Marcera
System Administrator
Press Enterprise, Inc.

Phone:  888.231.9767 x1352
Fax:570.784.3057
E-Mail: chris.marc...@pressenterprise.net

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with Mailman on Mac OS X Snow Leopard client

[Larry Stone]

On Mon, 10 Oct 2011, Graham Young wrote:

Mail generated by Mailman hangs in my dedicated, on-board MTA's queue 
unless I remove a certain bit of custom Postfix configuration that I 
entered following instructions kindly posted here by one Larry Stone.


I guess I'm best to answer this.


The bit of custom Postfix configuration that I've experimented with 
removing is exactly as follows: "hash:/etc/postfix/aliases"


The context in which this bit is supposed to appear is as follows:
"alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases".

I just remove the bit, leaving: "alias_maps = 
hash:/usr/local/mailman/data/aliases". Again, with just this as remnant 
of my custom Postscript configuration, Mailman-generated mail gets sent.


alias_maps is this list of aliases, local addresses which do not get 
delivered locally but rather get sent elsewhere. That could be another 
address (for instance, on my system, postmaster is an alias for me so I 
get all postmaster mail) or for Mailman, a pipe to the Mailman mail input 
script.


The error message that Postfix repeatedly issues when I don't have the 
suspect portion of this bit of custom Postscript configuration removed 
is as follows:
"Oct 10 21:10:05 email postfix/local[75578]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory


It means exactly what it says. /etc/postfix/aliases.db does not exist.

Finally, inasmuch as it may be relevant, I next post feedback that I get 
from a certain "postconf" command, specifically "postconf alias_maps": 
"alias_maps = hash:/etc/aliases"


That should be the outpust of "postconf -d alias_maps". -d means the 
default value. On my system (and I have never touched this part), 
/etc/aliases is a softlink to /etc/postfix/aliases (in other words, just a 
pointer to that file).


So the real is why does /etc/postfix/aliases.db not exist. It's not really 
required and it isn't part of Mailman. I had assumed it was past of the 
standard Postfix installation on OS X client but perhaps not (or maybe it 
was and no longer is but I didn't realize that because I've been upgrading 
or moving all the way from 10.3.


(a digression as to how aliases.db is created. aliases is a text file in a 
prescribed format. To turn it into the hash table Postfix wants to use, 
it's run through postmap. postmap hash:aliases created aliases.db)


The purpose of that customization is to append Mailman's alias file to the 
existing alias file.


If you don't have /etc/postfix/aliases.db, then don't include it in 
alias_maps. It's that simple. If you have a different aliases file, use 
that in place of /etc/postfix/aliases in alias_maps.


The best way to do this is to look in your Postfix main.cf for an earlier 
definition of alias_maps. So if you find

alias_maps = hash:foo, then replace my instructions with
alias_maps = hash:foo,
  hash:/usr/local/mailman/data/aliases

If there is no prior definition of alias_maps in main.cf, then do
postconf -d alias_maps and then:
alias_maps = (whatever postconf -d alias_maps returned),
  hash:/usr/local/mailman/data/aliases

However, please note that my instructions assume and expect familiarity 
with Postfix. If you don't understand Postfix, you will almost certainly 
have other problems in the future.


-- Larry Stone
   lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Integrating mailman with postfix, using virtual domains

[Nick Bright]

I'm sure this has been covered many times; however nothing I've found so 
far in the mailing list archives has alleviated this problem.


I've followed the mailman documentation for integrating mailman with 
postfix, according to 
http://www.list.org/mailman-install/postfix-virtual.html as well as 
various mailing list posts on this list.


Note that I am attempting to configure a virtual_mailbox_domain with 
mailman (not a virtual_alias_domain).


mm_cfg.py contains:

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['valnet.net']
MTA = 'Postfix'
DEFAULT_URL_HOST   = 'mail.valnet.net'
DEFAULT_EMAIL_HOST = 'valnet.net'
VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'valnet.net'

A mailing list was created with the newlist, which created 
/etc/mailman/aliases and /etc/mailman/virtual-mailman (and their 
associated db files).


I've added /etc/mailman/virtual-mailman to my virtual_alias_maps, and 
added /etc/mailman/aliases to my alias_maps and alias_database in main.cf:


alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases
alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases
virtual_alias_maps = hash:/etc/mailman/virtual-mailman

If I'm reading all of the documentation correctly, that should be all 
that is necessary to make it work.


Unfortunately, when I send an email to testl...@valnet.net I receive a 
bounce back of:


: unknown user: "testl...@valnet.net"

With an associated postfix log entry of:

Oct 10 19:22:47 mail postfix/virtual[22090]: DBF7241F5F: 
to=, relay=virtual, delay=0.39, 
delays=0.36/0/0/0.03, dsn=5.1.1, status=bounced (unknown user: 
"testl...@valnet.net")


When I test the alias maps I see:

[root@mail postfix]# postmap -q testl...@valnet.net 
hash:/etc/mailman/virtual-mailman

testlist
[root@mail postfix]# postmap -q testlist hash:/etc/mailman/aliases 


"|/usr/lib/mailman/mail/mailman post testlist"

That output *seems* correct, but I don't know if that's really correct 
or not.


In case it's worth noting, the list administrator specified in newlist 
does receive an email about the list being created.


I really think I've just missed something simple in the documentation, 
but the documentation for how to do this is strung out in so many 
different places and is a bit difficult to find, that I'm not entirely 
certain I've read it all.


Any tips or things to check would be appreciated.

Thanks,
 Nick

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] problem with Mailman on Mac OS X Snow Leopard client

[Graham Young]

Mail generated by Mailman hangs in my dedicated, on-board MTA's queue unless I 
remove a certain bit of custom Postfix configuration that I entered following 
instructions kindly posted here by one Larry Stone. The instruction in question 
are those for building Mailman on above platform directly from code downloaded 
from a source referenced on list.org and the configuration in question is one 
involving alias maps. 

Everything about this build of Mailman seems to be working fine. I can create 
lists and add or remove members. New members receive the expected mail--but 
here's the catch: only if I remove the above mentioned bit of custom Postscript 
configuration.

I came to suspect this bit of custom Postscript configuration exactly because 
Postfix reported an error involving it. Therefore I removed the bit of custom 
Postscript configuration to see if the queue would clear and it did. 

Everyone got their mail.  

However and of course, I question whether I can just remove this bit of custom 
Postscript configuration without consequences. Mailman-users may seem unlikely 
as a place to inquire about this; but, again, the instruction to use this bit 
of custom Postfix configuration came from a poster to this list whose 
particular posting is cited on list.org as authoritative. 

I am running Mailman on an Intel Mac mini with the client version of Mac OS X 
Snow Leopard installed. I will gladly post more details about my platform 
although I am not sure what might be needed.

The bit of custom Postfix configuration that I've experimented with removing is 
exactly as follows:
"hash:/etc/postfix/aliases"

The context in which this bit is supposed to appear is as follows:
"alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases".

I just remove the bit, leaving:
"alias_maps = hash:/usr/local/mailman/data/aliases".
Again, with just this as remnant of my custom Postscript configuration, 
Mailman-generated mail gets sent. 

The error message that Postfix repeatedly issues when I don't have the suspect 
portion of this bit of custom Postscript configuration removed is as follows:
"Oct 10 21:10:05 email postfix/local[75578]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:10:06 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75578 exit status 1
Oct 10 21:10:06 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:11:06 email postfix/local[75583]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:11:07 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75583 exit status 1
Oct 10 21:11:07 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:12:07 email postfix/local[75584]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:12:08 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75584 exit status 1
Oct 10 21:12:08 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:13:08 email postfix/local[75593]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:13:09 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75593 exit status 1
Oct 10 21:13:09 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling"

One can see why I investigated Postscript alias maps upon seeing these log 
entries. I obviously don't understand them, though. 

Finally, inasmuch as it may be relevant, I next post feedback that I get from a 
certain "postconf" command, specifically "postconf alias_maps":
"alias_maps = hash:/etc/aliases"

Seeing this as the feedback to said command, makes we wonder: Wouldn't the 
correct feedback here include reference to Mailman's own "aliases" file given 
what remains of my custom Postscript configuration? 

Anyway, something is certainly wrong. Assistance, if offered, will be much 
appreciated. Indeed thanks for even reading this since its the first thing I 
hope for that people read about my problem. 

Hopefully, I have posted well for starters but i am more than happy to take 
hints about what else I need to submit. I am a first time poster. 

Graham

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] missing post for moderation

[Andrew Watson]

I have a list which has been functioning fine for many years.
This morning I found a standard email to me, as moderator, asking that I 
authorize a posting.
The "Date" field says it was sent 6 hours ago.
When I go to the administrative page, no message appears for my approval.
If I test the system by sending a new message, it does appear in my moderator 
queue, so
otherwise the list appears to be working fine.

How can this happen, and is there some way to find the missing message, or 
should
I just chalk it up to the mysteries of mailman, and ask the poster to send 
again?

-Andrew
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Remove Members waiting for Moderator Approval via Command Line

[Phil]

I'm sorry if this was posted elsewhere - I've been unable to find an answer.

I also realized I originated this e-mail from an account not associated with
the mailing list.  This e-mail is from a subscribed mailman-user account.



I'm trying to kill a pending subscription to a mailing list via the command
line because the domain owner forgot to register the main domain of our site
and we can't approve/deny membership via the web admin interface.

I've tried to remove the e-mail address pending approval via the
remove_members command and it seem to only react to active and approved
members of a mailing list.

Is there a way to approve / deny a pending user request via shell?


Thanks for the help




Phil / w2lie
Monitor Long Island, Inc.  |
W2LIE.net|
LongIslandFirePhotos.com 
 
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org