Re: [Mailman-Users] Mailman no longer processing one mailing list

[Mark Sapiro]

Diana Kirk wrote:
>
>I just spent some time going through the searchable archives at 
>mail-archive.com, but didn't see my question (or its answer). I sent 
>a support ticket to my web host (via cpanel) and they are looking 
>into it, but basically they've asked me if there isn't anything else 
>I can tell them.
>
>I have two mailing lists with this web host for the same domain name 
>([EMAIL PROTECTED] and [EMAIL PROTECTED]). Both are active and were 
>working as programmed to work. Some time between Friday afternoon and 
>Saturday morning, [EMAIL PROTECTED], no longer processed any mail. 
>[EMAIL PROTECTED] continues to work as expected.
>
>I'm the list administrator and only moderator currently, as well as a 
>subscriber to the list. I have my subscription set up to send an 
>acknowledgment from Mailman that my posts have been received. I'm not 
>getting any acknowledgments. The posts are not being archived, nor 
>were they distributed to the mailing list, or sent to the list admin 
>or moderator's mailboxes for approval. As the list admin, I should 
>receive any unhandled bounces, and the posts didn't do that either. 
>I've pinged the mail address -- that's fine. And, in fact, the other 
>mailing list continues to receive, send out acknowledgments, archive, 
>and distribute the mail without problems.
>
>Does this ring a bell with anybody? Any clues as to what the web 
>hosting people should be looking for in the logs? Which logs should 
>they look in? Any guidance you can offer is appreciated.

See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp
concentrating on those things that could affect only a single list
plus the logs, i.e., items 2), 6), 7) and 8)

See also
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp

You might find something useful in the recent posts at
http://mail.python.org/pipermail/mailman-users/2005-July/045929.html
and
http://mail.python.org/pipermail/mailman-users/2005-July/045969.html

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

[Mailman-Users] Mailman no longer processing one mailing list

[Diana Kirk]

Hi all,

I just spent some time going through the searchable archives at 
mail-archive.com, but didn't see my question (or its answer). I sent 
a support ticket to my web host (via cpanel) and they are looking 
into it, but basically they've asked me if there isn't anything else 
I can tell them.

I have two mailing lists with this web host for the same domain name 
([EMAIL PROTECTED] and [EMAIL PROTECTED]). Both are active and were 
working as programmed to work. Some time between Friday afternoon and 
Saturday morning, [EMAIL PROTECTED], no longer processed any mail. 
[EMAIL PROTECTED] continues to work as expected.

I'm the list administrator and only moderator currently, as well as a 
subscriber to the list. I have my subscription set up to send an 
acknowledgment from Mailman that my posts have been received. I'm not 
getting any acknowledgments. The posts are not being archived, nor 
were they distributed to the mailing list, or sent to the list admin 
or moderator's mailboxes for approval. As the list admin, I should 
receive any unhandled bounces, and the posts didn't do that either. 
I've pinged the mail address -- that's fine. And, in fact, the other 
mailing list continues to receive, send out acknowledgments, archive, 
and distribute the mail without problems.

Does this ring a bell with anybody? Any clues as to what the web 
hosting people should be looking for in the logs? Which logs should 
they look in? Any guidance you can offer is appreciated.

Thanks,
Diana

--
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/archive%40jab.org

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

Re: [Mailman-Users] No mbox / No Archives

[Mark Sapiro]

Michael J McCafferty wrote:

> I have created the directories and run check_perms -f  to make 
>sure it's all ok. now all I gotta do is wait for some posts to the lists 
>(they are not my lists) to see if it works.
>
>At 05:11 PM 7/31/2005 -0700, Mark Sapiro wrote:

>>Normally, the list creation process creates the
>>archives/private/listname/listname.mbox/ directory and the first
>>archived message creates the
>>archives/private/listname/listname.mbox/listname.mbox file.

Perhaps you noticed the error in the above and weren't misled by it,
but I gave the wrong path for the .mbox files.

The archive directory structure is in archives/private/listname, but
the cumulative mbox file is in
archives/private/listname.mbox/listname.mbox, NOT in
archives/private/listname/listname.mbox/listname.mbox.

Sorry for any confusion.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

Re: [Mailman-Users] No mbox / No Archives

[Michael J McCafferty]

Mark,
 Thanks for the rapid reply.
 I am not using SELinux (doesn't come in RHEL3 or CentOS 3.x)
 The lists were recovered from only partial backups (the customer 
only provided the /var/mailman/lists directory, and nothing else.) So, if 
the place for the mbox files were created only during list creation, that 
could account for it. The error log does indicate that the mbox file or 
directory is missing. I should have looked there (slaps forehead).
 I have created the directories and run check_perms -f  to make 
sure it's all ok. now all I gotta do is wait for some posts to the lists 
(they are not my lists) to see if it works.

Thanks !!!
Mike

At 05:11 PM 7/31/2005 -0700, Mark Sapiro wrote:
>Michael J McCafferty wrote:
>
> >   I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My 
> problem
> >is that I have no archives. They are not being created.
> >
> >   Each list is set to archive, and to make the archives public. I 
> do have
> >Apache set to follow symlinks.  I also do not have any mbox directories or
> >files being kept. I don't know why. I figure that I have no archives
> >because I have no mboxes.  I have checked the permissions (check_perms).
> >
> >   Any thoughts on how to remedy or what to check next ?
>
>Are you using SELinux? There might be a security policy issue.
>
>Normally, the list creation process creates the
>archives/private/listname/listname.mbox/ directory and the first
>archived message creates the
>archives/private/listname/listname.mbox/listname.mbox file. It seems
>that you have neither the directory or file for your lists. If you
>create the directories by hand (in the 'mailman' group and group
>writable and searchable and normally setgid although I don't think
>that setgid is really necessary), that may allow messages to be
>archived, but it doesn't answer the question of why the directories
>weren't created in the first place.
>
>There may be relevant messages in Mailman's 'error' log. Also, the
>unarchived posts may be in the shunt queue such that creating the
>directories and running bin/unshunt will archive those posts.
>
>--
>Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

Re: [Mailman-Users] No mbox / No Archives

[Mark Sapiro]

Michael J McCafferty wrote:

>   I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My 
> problem 
>is that I have no archives. They are not being created.
>
>   Each list is set to archive, and to make the archives public. I do have 
>Apache set to follow symlinks.  I also do not have any mbox directories or 
>files being kept. I don't know why. I figure that I have no archives 
>because I have no mboxes.  I have checked the permissions (check_perms).
>
>   Any thoughts on how to remedy or what to check next ?

Are you using SELinux? There might be a security policy issue.

Normally, the list creation process creates the
archives/private/listname/listname.mbox/ directory and the first
archived message creates the
archives/private/listname/listname.mbox/listname.mbox file. It seems
that you have neither the directory or file for your lists. If you
create the directories by hand (in the 'mailman' group and group
writable and searchable and normally setgid although I don't think
that setgid is really necessary), that may allow messages to be
archived, but it doesn't answer the question of why the directories
weren't created in the first place.

There may be relevant messages in Mailman's 'error' log. Also, the
unarchived posts may be in the shunt queue such that creating the
directories and running bin/unshunt will archive those posts.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

[Mailman-Users] No mbox / No Archives

[Michael J McCafferty]

All,
I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My 
problem 
is that I have no archives. They are not being created.

Each list is set to archive, and to make the archives public. I do have 
Apache set to follow symlinks.  I also do not have any mbox directories or 
files being kept. I don't know why. I figure that I have no archives 
because I have no mboxes.  I have checked the permissions (check_perms).

Any thoughts on how to remedy or what to check next ?

Thanks,
Mike

--
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/archive%40jab.org

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

Re: [Mailman-Users] arch + EXTERNAL_ARCHIVER + lock files

[Mark Sapiro]

Jean-Philippe GIOLA wrote:
>
>In my mm_cfg.py, Y have this line :
> PUBLIC_EXTERNAL_ARCHIVER = 'cat > /tmp/mail_tmp ; 
>/home/mailman/bin/arch %(listname)s /tmp/mail_tmp'
>
>So, when a mail is sent to a list, it is store in a temporary file and 
>then this command is execute :
>/home/mailman/bin/arch %(listname)s /tmp/mail_tmp
>
>The problem I have is that the execution of this last command create 
>lock's files in the locks directory :
>listname.lock ...
>and so arch can't re-create the archives from /tmp/mail_tmp.
>then, when I remove the lock files, the execution of the arch script go on.
>
>Does someone has a idea to resolve my problem ?

ArchRunner locks the list prior to calling the ArchiveMail() method.
Thus the list is locked when the external archiver is invoked. Thus,
if the external archiver needs to lock the list, it needs to run in
the background so the external archiver command can return and the
list can be unlocked.

Try something like

'cat >/tmp/mail_tmp;/home/mailman/bin/arch %(listname)s /tmp/mail_tmp &'

for the external archiver. Note however that this could result in a
race condition if two posts arrive close enough together, the second
instance of 'cat' could be overwriting /tmp/mail_tmp before the first
instance of 'arch' is done reading it. It is better to create a unique
name.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

Re: [Mailman-Users] Problem running sync_members under cpanel

[Mark Sapiro]

Brad Knowles wrote:

>At 8:22 PM +0200 2005-07-31, Hilton wrote:
>
>>   File "/usr/local/cpanel/3rdparty/mailman/Mailman/LockFile.py", line 422, in
>>  __write
>> fp = open(self.__tmpfname, 'w')
>>
>>  IOError: [Errno 13] Permission denied:
>>  '/usr/local/cpanel/3rdparty/mailman/locks/test_landrover.org.za.lock.s53.tm.
>>  crucialx.net.13496.0'
>>  ---
>>
>>  Any pointers please? As I said before, I don't have root access.
>
>   That's a file permissions problem.  You need to talk to your 
>CPanel hosting provider.

To elaborate, the user under which the cron is running does not have
permission to create/write the lock file to lock the list. The cron
probably needs to run as root or as a user in the 'mailman' group
(usually 'mailman').

Also see
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

Re: [Mailman-Users] Problem running sync_members under cpanel

[Brad Knowles]

At 8:22 PM +0200 2005-07-31, Hilton wrote:

>   File "/usr/local/cpanel/3rdparty/mailman/Mailman/LockFile.py", line 422, in
>  __write
> fp = open(self.__tmpfname, 'w')
>
>  IOError: [Errno 13] Permission denied:
>  '/usr/local/cpanel/3rdparty/mailman/locks/test_landrover.org.za.lock.s53.tm.
>  crucialx.net.13496.0'
>  ---
>
>  Any pointers please? As I said before, I don't have root access.

That's a file permissions problem.  You need to talk to your 
CPanel hosting provider.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
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/archive%40jab.org

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

[Mailman-Users] Installation Questions

[Bob Cohen]

Hi. I'm getting ready to install Mailman and have a few questions. The 
procedures outlined in the Installation Manual at list.org seem odd. 
Other software that I've installed from source usually does things like 
creating the necessary user, setting permissions, creating the 
installation directory.  Also, the documentation says not to install 
Mailman as root.  Am I following this right? Or am I missing something?

Bob
--
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/archive%40jab.org

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

[Mailman-Users] Problem running sync_members under cpanel

[Hilton]

I'm using a hosting company that runs cpanel.
CentOS 4.1, cPanel 10.2.0-S83, Mailman 2.1.5p1

I don't have access to root, but what I'm trying to do is synchronise the
membership database via an uploaded text file.

This is the command that I've setup in the cron.

/usr/local/cpanel/3rdparty/mailman/bin/sync_members -w=no -g=no -a=yes -f
/home/lrocorg/mailman/export-lists/test.txt test_landrover.org.za

'lrocorg' is my username on the system and 'test_landrover.org.za' is the
mailman list that is assigned. The actual list name is just 'test'.

So I FTP the 'test.txt' to the respective directory under my home directory
and then run the cron job.

I then get this error message;

--
Ignore  :
Traceback (most recent call last):
 File "/usr/local/cpanel/3rdparty/mailman/bin/sync_members", line 286, in ?
   main()
 File "/usr/local/cpanel/3rdparty/mailman/bin/sync_members", line 220, in
main
   mlist = MailList.MailList(listname)
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 126, in
__init__
   self.Lock()
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 159, in
Lock
   self.__lock.lock(timeout)
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/LockFile.py", line 243, in
lock
   self.__write()
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/LockFile.py", line 422, in
__write
   fp = open(self.__tmpfname, 'w')

IOError: [Errno 13] Permission denied:
'/usr/local/cpanel/3rdparty/mailman/locks/test_landrover.org.za.lock.s53.tm.
crucialx.net.13496.0'
---

Any pointers please? As I said before, I don't have root access.


Regards
___
Hilton J Ralphs

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.7/60 - Release Date: 28/07/2005
 

--
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/archive%40jab.org

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

Re: [Mailman-Users] BIG trouble: mailman does not work withpostfix+maildrop+mysql

[Mark Sapiro]

Alex wrote:
>
>Yesterday, i tried to add mailman (mailman-2.1.5-33.rhel4) to above 
>comination (i want to setup some inernal mailing lists) but all the time 
>when somebody wants to subscribe via email, i get the following error in 
>/var/log/maillog file:
>
>Jul 31 10:15:29 lists postfix/pickup[12500]: 341DD48D0D: uid=12346 
>from=<[EMAIL PROTECTED]>
>Jul 31 10:15:29 lists postfix/cleanup[12551]: 341DD48D0D: 
>message-id=<[EMAIL PROTECTED]>
>Jul 31 10:15:29 lists postfix/qmgr[12501]: 341DD48D0D: 
>from=<[EMAIL PROTECTED]>, size=429, nrcpt=1 (queue active)
>Jul 31 10:15:29 lists maildrop[12561]: Invalid user specified or account 
>temporary disabled.
>Jul 31 10:15:29 lists postfix/pipe[12560]: 341DD48D0D: 
>to=<|/usr/lib/mailman/mail/mailman post [EMAIL PROTECTED]>, 
>orig_to=<[EMAIL PROTECTED]>, relay=maildrop, delay=0, 
>status=bounced (user unknown. Command output: maildrop: Invalid user 
>specified. )

It looks like Postfix is trying to send the 'pipe' command (plus
@mydoom.ro) to maildrop as an e-mail address and maildrop is rejecting
it because it's not a valid address.

This seems to be a postfix/maildrop configuration issue. I don't think
mailman-users can be of much help here.

Note that if Postfix directly executes the pipe instead of passing it
to maildrop as an address, it should work.


>so, it looks like maildrop is tring to deliver email from 
>[EMAIL PROTECTED] to one inexistent mailbox named: 
>"|/usr/lib/mailman/mail/mailman post [EMAIL PROTECTED]" and is not 
>makeing the correct redirection, redirecting incomming message to 
>/usr/lib/mailman/mail/mailman PIPE  Practically, sintax above is 
>interpreted like a string and not like a command!

Exactly. Again, this is a Postfix/maildrop issue, not a Mailman issue.


>Subscriptions via WEB are ok, but nobody can send email to other members 
>([EMAIL PROTECTED]) due to reason above! Message is bounced and 
>returned to sender!
>
>Here comes relevant parts of:
>postfix main.cf
>### Alias specific settings ###
>alias_database = hash:/etc/aliases
>alias_maps = hash:/etc/aliases
>newaliases_path = /usr/bin/newaliases
>virtual_alias_domains = $virtual_alias_maps
>virtual_alias_maps = mysql:redirections.cf, $alias_maps, 
>hash:/etc/mailman/aliases
>### Mailman specific settings ###
>owner_request_special = no
>recipient_delimiter = +
>unknown_local_recipient_reject_code = 550
>
>and last lines in /etc/mailman/mm_cfg.py looks like
>##
># Put YOUR site-specific configuration below, in mm_cfg.py . #
># See Defaults.py for explanations of the values.
>MTA = 'Postfix'
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydoom.ro']
>
>I created a new mailing list named maildrop, and /etc/mailman/aliases 
>look like below:


Actually, it looks like the list is named mailman, not maildrop


>
>mailman: "|/usr/lib/mailman/mail/mailman post mailman"
>mailman-admin:   "|/usr/lib/mailman/mail/mailman admin mailman"
>mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman"
>mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman"
>mailman-join:"|/usr/lib/mailman/mail/mailman join mailman"
>mailman-leave:   "|/usr/lib/mailman/mail/mailman leave mailman"
>mailman-owner:   "|/usr/lib/mailman/mail/mailman owner mailman"
>mailman-request: "|/usr/lib/mailman/mail/mailman request mailman"
>mailman-subscribe:   "|/usr/lib/mailman/mail/mailman subscribe mailman"
>mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
>
>I think the problem is caused by redirections above due to incompatible 
>sintax between mailman and standard postfix+maildrop+mysql redirections. 
>Can somebody clarify me sintax:
>mailman: "|/usr/lib/mailman/mail/mailman post mailman"
>
>In my opinion it mean:
>REDIRECT all emails comming to address: [EMAIL PROTECTED] into mailman 
>pipe (|/usr/lib/mailman/mail/mailman) with 2 arguments (post and 
>mailman). What i don't know, is what represent FIRST (post) and SECOND 
>(mailman) ARGUMENTS in this pipe? I tried to find and explanation in 
>mailman docs to this question but it seems that answer is missing!!!


The first argument is the action to take with this mail and in all
cases except post is the same as the suffix part of the
listname-suffix address. post is used when there is no suffix, i.e.,
when a post is sent to the listname address. The second argument is
the name of the list - 'mailman' in this case.

>PS: No errors are reported in /var/log/mailman/error!

Mailman never sees the message.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40

Re: [Mailman-Users] Archive list with date stamp

[Mark Sapiro]

Ricciotti Jr.,Anthony R. wrote:

>I have a group of users that have requested that the archive lists
>include the date/time of the email in the list. 
>
>In other words:
>
>[Mailman-Users] wrapper error   Wayne Sitton
>
>Would show up as this:
>
>[Mailman-Users] wrapper error   Wayne Sitton   Thu Apr 4 17:56:59 EST
>2024
>
>Is there a patch that I am missing? I thought I saw it in the feature
>list, but now cannot find it anywhere.  I am running 2.1.6 as I thought
>it was there, and needed the security patches also.

It's an RFE at
http://sourceforge.net/tracker/index.php?func=detail&aid=843141&group_id=103&atid=350103

I'm not aware of a patch.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

Re: [Mailman-Users] REQ: show member names as well as email addresses

[Mark Sapiro]

Daevid Vincent wrote:

>I'm using version 2.1.5 (Gentoo) and when a member views the member list, it
>only shows the email addresses. I request that it also (or have the option
>for the moderator to allow this) to show the Names of the members too. It
>shows the full name when you click on the hyperlinked obscured email, but
>that is tedious if you're trying to find someone but don't know their email
>address.

RFEs are best submitted at
http://sourceforge.net/tracker/?group_id=103&atid=350103 so they can
be properly tracked, commented, found, etc.

In fact, if you look, you'll find
http://sourceforge.net/tracker/index.php?func=detail&aid=983002&group_id=103&atid=350103
which addresses this issue. Feel free to add your own comment.

In the mean time, your users can get a member list including real name
via the e-mail 'who' command sent to the listname-request address.
This is not as convenient as the web roster for looking up a single
address, but it beats clicking every address looking for a specific
name.

The format of the 'who' command depends on whether the roster is
'public' or not. Send a 'help' command to the listname-request address
for list specific help.

--
Mark Sapiro <[EMAIL PROTECTED]>   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://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/archive%40jab.org

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

[Mailman-Users] Mailman Cron Jobs on Tiger OSX Server Solved

[David Scribner]

I want to thank everyone that has helped with this problem.

What i discovered is that if you UPGRADE to Tiger Server from a 
Panther Server install the Mailman Cron jobs don't get enabled or 
run.  However, if you install a clean fresh version of Tiger Server 
and set-up Mailman from scratch the Cron Jobs are enabled and happen 
as they are supposed to.

Luckily, in my case i was able to do a clean install of Tiger Server 
and everything is running fine now.  And it had the added benefit 
that I was able to clean out some other things from the previous 
Panther install.

I just wanted to pass along this note in case someone runs into this 
same problem.

Again, Thanks

David Scribner
BI Consulting
--
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/archive%40jab.org

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

[Mailman-Users] BIG trouble: mailman does not work with postfix+maildrop+mysql

[Alex]

Hello mailman experts,

I am comming here because i have problems makeing mailman working with 
postfix+maildrop (used as local delivery agent) and mysql as bakend.

First i want to mention on our mailserver everything is virtualized and 
postfix is working like a charm with mysql and maildrop for our 
virtualized domains. I am using RHEL4 + postfix-2.1.5-4.2.RHEL4

Yesterday, i tried to add mailman (mailman-2.1.5-33.rhel4) to above 
comination (i want to setup some inernal mailing lists) but all the time 
when somebody wants to subscribe via email, i get the following error in 
/var/log/maillog file:

Jul 31 10:15:29 lists postfix/pickup[12500]: 341DD48D0D: uid=12346 
from=<[EMAIL PROTECTED]>
Jul 31 10:15:29 lists postfix/cleanup[12551]: 341DD48D0D: 
message-id=<[EMAIL PROTECTED]>
Jul 31 10:15:29 lists postfix/qmgr[12501]: 341DD48D0D: 
from=<[EMAIL PROTECTED]>, size=429, nrcpt=1 (queue active)
Jul 31 10:15:29 lists maildrop[12561]: Invalid user specified or account 
temporary disabled.
Jul 31 10:15:29 lists postfix/pipe[12560]: 341DD48D0D: 
to=<|/usr/lib/mailman/mail/mailman post [EMAIL PROTECTED]>, 
orig_to=<[EMAIL PROTECTED]>, relay=maildrop, delay=0, 
status=bounced (user unknown. Command output: maildrop: Invalid user 
specified. )

so, it looks like maildrop is tring to deliver email from 
[EMAIL PROTECTED] to one inexistent mailbox named: 
"|/usr/lib/mailman/mail/mailman post [EMAIL PROTECTED]" and is not 
makeing the correct redirection, redirecting incomming message to 
/usr/lib/mailman/mail/mailman PIPE  Practically, sintax above is 
interpreted like a string and not like a command!
Subscriptions via WEB are ok, but nobody can send email to other members 
([EMAIL PROTECTED]) due to reason above! Message is bounced and 
returned to sender!

Here comes relevant parts of:
postfix main.cf
### Alias specific settings ###
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
newaliases_path = /usr/bin/newaliases
virtual_alias_domains = $virtual_alias_maps
virtual_alias_maps = mysql:redirections.cf, $alias_maps, 
hash:/etc/mailman/aliases
### Mailman specific settings ###
owner_request_special = no
recipient_delimiter = +
unknown_local_recipient_reject_code = 550

and last lines in /etc/mailman/mm_cfg.py looks like
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydoom.ro']

I created a new mailing list named maildrop, and /etc/mailman/aliases 
look like below:

mailman: "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:   "|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join:"|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:   "|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:   "|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:   "|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"

I think the problem is caused by redirections above due to incompatible 
sintax between mailman and standard postfix+maildrop+mysql redirections. 
Can somebody clarify me sintax:
mailman: "|/usr/lib/mailman/mail/mailman post mailman"

In my opinion it mean:
REDIRECT all emails comming to address: [EMAIL PROTECTED] into mailman 
pipe (|/usr/lib/mailman/mail/mailman) with 2 arguments (post and 
mailman). What i don't know, is what represent FIRST (post) and SECOND 
(mailman) ARGUMENTS in this pipe? I tried to find and explanation in 
mailman docs to this question but it seems that answer is missing!!!

Any fix will be wellcome.

Regards,
Alex

PS: No errors are reported in /var/log/mailman/error!


--
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/archive%40jab.org

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