[Mailman-Users] Weird again!!
One of my lists is discarding messages for some reason. THe vette file looks like the following .. Aug 10 18:52:42 2006 (5414) Message discarded, msgid: [EMAIL PROTECTED] Aug 10 18:55:43 2006 (5414) Message discarded, msgid: [EMAIL PROTECTED] I am subscribed to the list. I suspect someone reset something or set something I do not know about but I cannot find it. ANy ideas? LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weird again!!
Lawrence Bowie wrote: One of my lists is discarding messages for some reason. THe vette file looks like the following .. Aug 10 18:52:42 2006 (5414) Message discarded, msgid: [EMAIL PROTECTED] Aug 10 18:55:43 2006 (5414) Message discarded, msgid: [EMAIL PROTECTED] I am subscribed to the list. I suspect someone reset something or set something I do not know about but I cannot find it. ANy ideas? LDB -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Found it!! A spam rule LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] To: Field is not what it it suppose to be
OK .. I am just now noticing this on my lists. The To: field on all my lists have [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Although, I am sending it to lists.example.org. Is this a postfix or a mailman configuration issue? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] To: Field is not what it it suppose to be
Mark Sapiro wrote: Lawrence Bowie wrote: OK .. I am just now noticing this on my lists. The To: field on all my lists have [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Although, I am sending it to lists.example.org. Is this a postfix or a mailman configuration issue? Assuming you are talking about individual messages and not digests, I don't think Mailman does anything with To: headers except in the case of full personalization. This is probably some canonicalization going on in an MTA because of CNAME DNS records. That is what I thought. Thank you Mark. LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Weird issuee again
Whenever a user sends to my lists from his account he does NOT receive his own post but yet New_members_options - Do not send a copy of member's own post is NOT checked. Could it be that it was once checked? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weird issuee again
Lawrence Bowie wrote: Whenever a user sends to my lists from his account he does NOT receive his own post but yet New_members_options - Do not send a copy of member's own post is NOT checked. Could it be that it was once checked? Thanks, LDB -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Thanks Dan ... http://www.mail-archive.com/mailman-users@python.org/msg39734.html LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Best practices
Excellent .. Thanks guys .. good and informative responses. LDB Christopher Adams wrote: Mostly, I agree with Mark on this. You really have to balance what individual list owners want, how individual lists operate, and the fact that you may host/administer so many lists that the best choice is the same for all. We host over 500 lists. Originally, the default was to 'Hold' messages from non-members. This might include subscribers who's address had changed or individuals who thought they were on the list. This is where we needed to reevaluate the situation. Many list owners are busy and don't want to continually take action on posts from non-members. However, many list owners also don't want messages from 'non-members' to be automatically discarded. Our solution was to make the default to 'Reject', but send a message to the sender, indicating that their message was rejected because either they are not a member or their address has changed. One problem with this solution is that the option for multiple languages becomes a bit of an issue. On 7/23/06, Mark Sapiro [EMAIL PROTECTED] wrote: David Gibbs wrote: Lawrence Bowie wrote: I have been rejecting messages from non-members but I am not sure that is the best practice. Is it better to discard rather than reject non-members messages? It depends on the message ... if the message is topical, then I reject the message indicating that to post a person must be subscribed, and if they are subscribed, then they might be posting from a different email address. If the message isn't topical, then I just discard it (for which the 'discard all messages marked as deferred' check box is a boon), as those are usually just spam. So you have generic_nonmember_action set to 'Hold', and you (or a moderator) make a decision on each post. I think Lawrence is asking a different question, namely, should generic_nonmember_action be 'reject' or 'discard'? This is a controversial question, and the answer really depends on the list. The 'good' answer is that spam should be filtered out ahead of Mailman. Then Mailman and the list owner don't have to worry about 'blowback' and spam forwarding issues, but this solution isn't always available. If you have spam reaching Mailman, it is clearly best to discard the spam without sending any kind of 'reply'. Note that holding and then discarding the message only does this if respond_to_post_requests is set to 'No'. Otherwise, by the time the moderator sees the message, a hold notification reply has already been sent. Unfortunately, once the post gets to Mailman, Mailman applies the generic_nonmember_action in every case. I think we all agree that for spam (if it gets this far), this should be discard, but there are lists for which this is not appropriate if the message is not spam. In the past, Brad has posted examples to this list of situations where silently discarding an attempted post has caused significant problems for the non-member who thought the post had been received. In short, this is a list specific decision. Is your list one where you have non-members attempting to post? What are the consequences if that post is discarded without notice? How do these balance with spam blowback/forwarding considerations to the extent that spam gets this far? -- 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/adamsca%40gmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htphttp://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Best practices
I have been rejecting messages from non-members but I am not sure that is the best practice. Is it better to discard rather than reject non-members messages? Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] list automatically removing users
I do not have bounce processing enabled but yet one morning I have a list of about 15 users unsubscribed from the list. According to logs, they all look like this, [EMAIL PROTECTED] auto-unsubscribed [reason: BYBOUNCE] This obviously says it was removed because of some measure of bounces were exceeded. But once again, I do not have bounce processing enabled. Any explanation would be nice .. Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Mark Sapiro wrote: Lawrence Bowie wrote: I do not have bounce processing enabled but yet one morning I have a list of about 15 users unsubscribed from the list. According to logs, they all look like this, [EMAIL PROTECTED] auto-unsubscribed [reason: BYBOUNCE] This obviously says it was removed because of some measure of bounces were exceeded. But once again, I do not have bounce processing enabled. Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Does not exists anywhere in my config. Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Yes, it did. Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. Bounce process was not enabled at all. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Does not exists anywhere in my config. So new lists are created with bounce_processing on and you manually turn it off. This is an old list. I am referring to and it explicitly turned off via the web interface. Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Yes, it did. So presumably, it was cron/disabled that did the unsubscribes. If Mailman's bounce log (or logs if rotated) goes back a month ago, check for any occurrences of entries for the involved users. Also, try bin/list_members --nomail=bybounce listname and see if you currently have any members disabled by bounce. There were not any users revealed after this command was executed. Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. Bounce process was not enabled at all. As I note above, when the list was first created, bounce_processing was on by default. Are you sure you turned it off immediately after creating the list? Cannot be sure all I know it turned off now and it was NOT recently turned off. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Weird mailing list issues
I have a mailing list that will not accept a specific HTML message from a subscribing user. It will accept other messages but not this particular. I tested the message against a test list and the message posted just fine. So, I can probably conclude that there is something wrong with that particular list. Is that correct? Any ideas? Will rebuilding the archives help? Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Implicit destination
I have a message in the vette directory labeled: Message has implicit destination The user whom sent it subscribes to the list. How do I resolve? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Implicit destination
Lawrence Bowie wrote: I have a message in the vette directory labeled: Message has implicit destination The user whom sent it subscribes to the list. How do I resolve? Thanks, LDB -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Thanks Dan ... LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote:
Lawrence Bowie wrote:
Mark Sapiro wrote:
What does scripts/paths.py now contain?
# -*- python -*-
# Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
# This file becomes paths.py which is installed in may directories. By
# importing this module, sys.path gets `hacked' so that the $prefix/Mailman
# directory is inserted at the start of that list. That directory really
# contains the Mailman modules in package form. This file exports two
# attributes that other modules may use to get the absolute path to the
# installed Mailman distribution.
import sys
import os
import japanese
This (import japanese) needs to be at the end after the sys.path
manipulations. I gave you the wrong info for testing this. It should
have been
python -S scripts/paths.py
# some scripts expect this attribute to be in this module
prefix = '/usr/lib/mailman'
exec_prefix = '${prefix}'
# work around a bogus autoconf 2.12 bug
if exec_prefix == '${prefix}':
exec_prefix = prefix
# Hack the path to include the parent directory of the $prefix/Mailman package
# directory.
sys.path.insert(0, prefix)
# We also need the pythonlib directory on the path to pick up any overrides of
# standard modules and packages. Note that these must go at the front of the
# path for this reason.
sys.path.insert(0, os.path.join(prefix, 'pythonlib'))
# Include Python's site-packages directory.
sitedir = os.path.join(sys.prefix, 'lib', 'python'+sys.version[:3],
'site-packages')
sys.path.append(sitedir)
Since I put it at the end. It is seemingly working now. So I have placed,
import japanese
at the end of sys.path in the files {cron,tests,bin,scripts/paths.py and
it works.
Thanks Mark,
LDB
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: Did you add import japanese to bin/paths.py or was it already there? If you added it, you also have to add it to scripts/paths.py and cron/path.py, and for completeness, tests/paths.py if you have a tests/ directory, but that is only needed if you run any of the tests/* scripts. Also, you needed to do a 'bin/mailmanctl restart' at some point, but I suspect you may have done that. Sorry never answered your question. Yes, i added it. I also added the additional ones as well and restarted. Now, I just the browser error but I get NOTHING in the error log. You may have a syntax error (typo) in scripts/paths.py. Try just running python scripts.paths.py It should exit without printing anything. If there's an error, it will print an exception. No exceptions. Actually, when I added import japanese to cron/paths.py, scripts/paths.py and tests/paths.py, ALL my lists admin. interface links were unaccessible. Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote:
Lawrence Bowie wrote:
Mark Sapiro wrote:
You may have a syntax error (typo) in scripts/paths.py. Try just running
python scripts.paths.py
It should exit without printing anything. If there's an error, it will
print an exception.
No exceptions.
Actually, when I added import japanese to cron/paths.py, scripts/paths.py
and
tests/paths.py, ALL my lists admin. interface links were
unaccessible.
I would be surprised if any of the web interface is now accessible. All
the web Ggi scripts are run through scripts/driver which imports
scripts/paths.py which presumably is the only thing that changed, and
is what's causing the problem.
What does scripts/paths.py now contain?
# -*- python -*-
# Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
# This file becomes paths.py which is installed in may directories. By
# importing this module, sys.path gets `hacked' so that the $prefix/Mailman
# directory is inserted at the start of that list. That directory really
# contains the Mailman modules in package form. This file exports two
# attributes that other modules may use to get the absolute path to the
# installed Mailman distribution.
import sys
import os
import japanese
# some scripts expect this attribute to be in this module
prefix = '/usr/lib/mailman'
exec_prefix = '${prefix}'
# work around a bogus autoconf 2.12 bug
if exec_prefix == '${prefix}':
exec_prefix = prefix
# Hack the path to include the parent directory of the $prefix/Mailman package
# directory.
sys.path.insert(0, prefix)
# We also need the pythonlib directory on the path to pick up any overrides of
# standard modules and packages. Note that these must go at the front of the
# path for this reason.
sys.path.insert(0, os.path.join(prefix, 'pythonlib'))
# Include Python's site-packages directory.
sitedir = os.path.join(sys.prefix, 'lib', 'python'+sys.version[:3],
'site-packages')
sys.path.append(sitedir)
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote: Mark Sapiro wrote: If you have everything but the pythonlib/japanese/ directory, you can unpack the JapaneseCodecs-1.4.11.tar.gz, cd to the unpack directory and run python ./setup.py build This will create a 'build/' subdir which contains a lib*/ subdir which contains a 'japanese/' subdir which you can move to Mailman's pythonlib/ directory. Or you can run python ./setup.py install either after or instead of 'python ./setup.py build', and that will install the codecs in python's site-packages/ directory, and they will be available to Mailman there. Thanks Mark .. LDb -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Lawrence Bowie wrote: Mark Sapiro wrote: Mark Sapiro wrote: If you have everything but the pythonlib/japanese/ directory, you can unpack the JapaneseCodecs-1.4.11.tar.gz, cd to the unpack directory and run python ./setup.py build This will create a 'build/' subdir which contains a lib*/ subdir which contains a 'japanese/' subdir which you can move to Mailman's pythonlib/ directory. Or you can run python ./setup.py install either after or instead of 'python ./setup.py build', and that will install the codecs in python's site-packages/ directory, and they will be available to Mailman there. Thanks Mark .. LDb -- 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/ldb%40example.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Back again .. The posts are working but the admin. interface page is not working and it is displaying the following message in the browser ... Bug in Mailman version 2.1.6 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I tried to cp euc_jp.py EUC-JP then restart mailman but it not work. Any idea? Here are the /var/lib/mailman/logs/errors: Jun 15 17:46:26 2006 admin(17989): admin(17989): [- Mailman Version: 2.1.6 -] admin(17989): [- Traceback --] admin(17989): Traceback (most recent call last): admin(17989): File /usr/lib/mailman/scripts/driver, line 101, in run_main admin(17989): main() admin(17989): File /usr/lib/mailman/Mailman/Cgi/listinfo.py, line 60, in main admin(17989): i18n.set_language(language) admin(17989): File /usr/lib/mailman/Mailman/i18n.py, line 35, in set_language admin(17989): language) admin(17989): File /usr/lib/python2.4/gettext.py, line 465, in translation admin(17989): t = _translations.setdefault(key, class_(open(mofile, 'rb'))) admin(17989): File /usr/lib/python2.4/gettext.py, line 177, in __init__ admin(17989): self._parse(fp) admin(17989): File /usr/lib/python2.4/gettext.py, line 324, in _parse admin(17989): tmsg = unicode(tmsg, self._charset) admin(17989): LookupError: unknown encoding: EUC-JP admin(17989): [- Python Information -] admin(17989): sys.version = 2.4.1 (#1, Sep 13 2005, 00:39:20) [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] admin(17989): sys.executable = /usr/bin/python admin(17989): sys.prefix = /usr admin(17989): sys.exec_prefix = /usr admin(17989): sys.path= /usr admin(17989): sys.platform= linux2 admin(17989): [- Environment Variables -] admin(17989): HTTP_COOKIE: lsb-discuss+admin=28020069c8de914473280062343864343933326463373035613733313266343033633265663830303736393565643264633031 admin(17989): SERVER_SOFTWARE: Apache/2.0.54 (Linux/SUSE) admin(17989): SCRIPT_NAME: /mailman/listinfo admin(17989): SERVER_SIGNATURE: addressApache/2.0.54 (Linux/SUSE) Server at lists.example.org Port 80/address admin(17989): admin(17989): REQUEST_METHOD: GET admin(17989): HTTP_KEEP_ALIVE: 300 admin(17989): SERVER_PROTOCOL: HTTP/1.1 admin(17989): QUERY_STRING: admin(17989): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(17989): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060425 SUSE/1.5.0.3-7 Firefox/1.5.0.3 admin(17989): HTTP_CONNECTION: keep-alive admin(17989): HTTP_REFERER: http://lists.example.org/mailman/listinfo admin(17989): SERVER_NAME: lists.example.org admin(17989): REMOTE_ADDR: 72.21.10.146 admin(17989): PATH_TRANSLATED: /srv/www/htdocs/mylist admin(17989): SERVER_PORT: 80 admin(17989): SERVER_ADDR: admin(17989): DOCUMENT_ROOT: /srv/www/htdocs admin(17989): HTTP_PRAGMA: no-cache admin(17989): PYTHONPATH: /usr/lib/mailman admin(17989): SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/listinfo admin(17989): SERVER_ADMIN: [no address given] admin(17989): HTTP_HOST: lists.example.org admin(17989): HTTP_CACHE_CONTROL: no-cache admin(17989): REQUEST_URI: /mailman/listinfo/mylist admin(17989): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(17989): GATEWAY_INTERFACE: CGI/1.1 admin(17989): REMOTE_PORT: 46417 admin(17989): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 admin(17989): HTTP_ACCEPT_ENCODING: gzip,deflate admin(17989): PATH_INFO: /mylist -- Mailman-Users mailing list Mailman-Users
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote: Lawrence Bowie wrote: Back again .. The posts are working but the admin. interface page is not working and it is displaying the following message in the browser ... Bug in Mailman version 2.1.6 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I tried to cp euc_jp.py EUC-JP then restart mailman but it not work. Any idea? Here are the /var/lib/mailman/logs/errors: Jun 15 17:46:26 2006 admin(17989): admin(17989): [- Mailman Version: 2.1.6 -] admin(17989): [- Traceback --] admin(17989): Traceback (most recent call last): admin(17989): File /usr/lib/mailman/scripts/driver, line 101, in run_main admin(17989): main() admin(17989): File /usr/lib/mailman/Mailman/Cgi/listinfo.py, line 60, in main admin(17989): i18n.set_language(language) admin(17989): File /usr/lib/mailman/Mailman/i18n.py, line 35, in set_language admin(17989): language) admin(17989): File /usr/lib/python2.4/gettext.py, line 465, in translation admin(17989): t = _translations.setdefault(key, class_(open(mofile, 'rb'))) admin(17989): File /usr/lib/python2.4/gettext.py, line 177, in __init__ admin(17989): self._parse(fp) admin(17989): File /usr/lib/python2.4/gettext.py, line 324, in _parse admin(17989): tmsg = unicode(tmsg, self._charset) admin(17989): LookupError: unknown encoding: EUC-JP Did you add import japanese to bin/paths.py or was it already there? If you added it, you also have to add it to scripts/paths.py and cron/path.py, and for completeness, tests/paths.py if you have a tests/ directory, but that is only needed if you run any of the tests/* scripts. Also, you needed to do a 'bin/mailmanctl restart' at some point, but I suspect you may have done that. Sorry never answered your question. Yes, i added it. I also added the additional ones as well and restarted. Now, I just the browser error but I get NOTHING in the error log. Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Japanese Character encoding
Jun 14 20:49:14 2006 (19227) Uncaught runner exception: unknown encoding: japanese.euc-jp Jun 14 20:49:14 2006 (19227) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in _dispose self._func(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Handlers/SMTPDirect.py, line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File /usr/lib/mailman/Mailman/Handlers/SMTPDirect.py, line 356, in bulkdeliver msgtext = msg.as_string() File /usr/lib/mailman/Mailman/Message.py, line 208, in as_string g.flatten(self, unixfrom=unixfrom) File /usr/lib/mailman/pythonlib/email/Generator.py, line 102, in flatten self._write(msg) File /usr/lib/mailman/pythonlib/email/Generator.py, line 130, in _write self._dispatch(msg) File /usr/lib/mailman/pythonlib/email/Generator.py, line 156, in _dispatch meth(msg) File /usr/lib/mailman/pythonlib/email/Generator.py, line 197, in _handle_text payload = cset.body_encode(payload) File /usr/lib/mailman/pythonlib/email/Charset.py, line 386, in body_encode s = self.convert(s) File /usr/lib/mailman/pythonlib/email/Charset.py, line 269, in convert return unicode(s, self.input_codec).encode(self.output_codec) LookupError: unknown encoding: japanese.euc-jp I have the above error in my logs. I need this Japanese encoding but my SuSE 10.0 dist does not stock it. Where can I find it so mailman can work with my Japanese mailing lists? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Japanese Character encoding
Mark Sapiro wrote: Lawrence Bowie wrote: LookupError: unknown encoding: japanese.euc-jp I have the above error in my logs. I need this Japanese encoding but my SuSE 10.0 dist does not stock it. Where can I find it so mailman can work with my Japanese mailing lists? The euc-jp codecs are included in a standard Mailman distribution and installed $prefix/pythonlib/japanese by the standard install. If they are not in your Mailman and you have a SuSE packaged Mailman, this would be a SuSE packaging issue. You can download the current Mailman 2.1.8 tarball which includes JapaneseCodecs-1.4.11 in the misc/ directory. How do i get my current mailman SuSE installation o recognize the JapaneseCodecs-1.4.11? Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Aliases not working
I have been getting rid of lists lately and I need to forward old lists to the new lists. I am using mailman 2.1.6 and the forwards are not working. I also recently upgraded the OS from Debian to SuSE 10.0. Any ideas anyone?? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Aliases not working
Mark Sapiro wrote: Lawrence Bowie wrote: I have been getting rid of lists lately and I need to forward old lists to the new lists. I am using mailman 2.1.6 and the forwards are not working. I also recently upgraded the OS from Debian to SuSE 10.0. How are you forwarding? What's not working? Note that if the new list has require_explicit_destination Yes, you will probably need to put the old list address in acceptable_aliases in order for a post to the old list to not be held for implicit destination by the new list. (These settings are on Privacy options...-Recipient filters.) Thank you Mark. That worked. Do I also have to put the aliases, old-list-admin old-list-bounces old-list-confirm old-list-join old-list-leave old-list-owner old-list-request old-list-subscribe old-list-unsubscribe that point to, new-list-admin new-list-bounces new-list-confirm new-list-join new-list-leave new-list-owner new-list-request new-list-subscribe new-list-unsubscribe ,respectively? Or does just old-list - new-list suffice? Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Changing URLs in mailman after move
In moving from Debian to SuSE 10.0, the mailing lists' links like, http://lists.example.org/cgi-bin/mailman/admindb/test-list do not work anymore because the actual link on the new server is http://lists.example.org/mailman/admindb/test-list I can take care of this via apache but there has to be a way to do it via mailman. Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] After mailing move ....
Jun 6 22:07:21 mailserver postfix/local[3100]: D7F6F580BB: to=[EMAIL PROTECTED], relay=local, delay=1, status=SOFTBOUNCE (Command died with status 1: /var/lib/mailman/mail/mailman post test-list) I keep getting the above in postfix logs and my lists are not working. Is this due to name of the server is mailserver and the name of the SMTP server is lists? Any help would be great ... LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] After mailing move ....
Lawrence Bowie wrote: Jun 6 22:07:21 mailserver postfix/local[3100]: D7F6F580BB: to=[EMAIL PROTECTED], relay=local, delay=1, status=SOFTBOUNCE (Command died with status 1: /var/lib/mailman/mail/mailman post test-list) I keep getting the above in postfix logs and my lists are not working. Is this due to name of the server is mailserver and the name of the SMTP server is lists? Any help would be great ... LDB -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Clearly a path problem .. nevermind .. Thanks for the disk space, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] postfix-to-mail.py
Anyone out there using the above script on SuSE 10.0 to protect their mailing lists? I keep getting the below errors after the mailing lists move. D67F4580B8 2239 Tue Jun 6 22:38:58 [EMAIL PROTECTED] (temporary failure. Command output: exceptions.OSError [Errno 2] No such file or directory Line 122) [EMAIL PROTECTED] -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] postfix-to-mail.py
Lawrence Bowie wrote: Anyone out there using the above script on SuSE 10.0 to protect their mailing lists? I keep getting the below errors after the mailing lists move. D67F4580B8 2239 Tue Jun 6 22:38:58 [EMAIL PROTECTED] (temporary failure. Command output: exceptions.OSError [Errno 2] No such file or directory Line 122) [EMAIL PROTECTED] -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp This is bad .. I am answering my questions .. OK here is what I discovered .. On SuSE 10.0, /var/lib/mailman does contain directory called mail/ so I had to create a soft link, ln -s /usr/lib/mailman/mail and that does the trick. Is there anything else that maybe missing?? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] multi-alternative
Mark Sapiro wrote: Lawrence Bowie wrote: I have a user telling me .. It looks like the pipermail installation is hosed in some interesting way. The emails that I send have both text/html and text/multipart sections. It scrubbed the text/html part, but didn't bother including the text/plain part. But yet ... Default.py: DEFAULT_PASS_MIME_TYPES = ['multipart/mixed', 'multipart/alternative', 'text/plain'] This just determines the defaults for Content filtering-pass_mime_types for a new list. The only thing that means anything is the settings on the Content filtering page. When the user says scrubbed does she mean as in An HTML attachment was scrubbed... URL: url or does she mean removed by content filtering? Yes, removed. There was an upgrade over the weekend. So something unexpected must have happened. Any ideas? I would try to find the message as delivered from the list to message subscribers, or find it in the archives/private/listname.mbox/listname.mbox file and also look at the raw HTML (source) for the archive page to see if there is really an inconsistency. I would also wonder if this was a single occurrence or is repeatable. If it is not repeatable, I think you may find that the message in the .mbox file had no text/plain part. Thank you .. LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] multi-alternative
I have a user telling me .. It looks like the pipermail installation is hosed in some interesting way. The emails that I send have both text/html and text/multipart sections. It scrubbed the text/html part, but didn't bother including the text/plain part. But yet ... Default.py: DEFAULT_PASS_MIME_TYPES = ['multipart/mixed', 'multipart/alternative', 'text/plain'] There was an upgrade over the weekend. So something unexpected must have happened. Any ideas? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Forwarding old lists to new list
Mark Sapiro wrote: Lawrence Bowie wrote: Is it acceptable to forward old lists that are not used anymore to one single list? I'm not sure what you're getting at or what result you want, but if you mean could you set MTA aliases for several different [EMAIL PROTECTED], etc. addresses to all go to the same list as in list1: |/usr/local/mailman/mail/mailman post newlist list1-bounces: |/usr/local/mailman/mail/mailman bounces newlist etc. list2: |/usr/local/mailman/mail/mailman post newlist list2-bounces: |/usr/local/mailman/mail/mailman bounces newlist etc. there should be no problem doing that. You would probably either want to set newlist for require_explicit_destination - No or add all the old list posting addresses to acceptable_aliases Perfect .. thank you ... LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Forwarding old lists to new list
Is it acceptable to forward old lists that are not used anymore to one single list? Thanks, LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Filtering Email Marked SPAM
What is the easist way to globally filter email marked SPAM? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Filtering Email Marked SPAM
Mark Sapiro wrote:
Lawrence Bowie wrote:
What is the easist way to globally filter email marked SPAM?
Assuming you mean in Mailman, use the KNOWN_SPAMMERS list in mm_cfg.py,
e.g.
KNOWN_SPAMMERS = [('subject', '^.*spam'), ('x-spam-flag', 'yes')]
This is a list of tuples of (header, regexp) where header is the name
of a header and regexp is a pattern to search the contents of the
header. These are case insensitive. Any match will discard the message.
But, why not have whatever process marks the message as spam discard it.
Good quesiton ... I like to see some of the SPAM to understand patterns. :)
Thanks Mark,
LDB
--
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=showamp;file=faq01.027.htp
[Mailman-Users] Not a list member notification email
I am having trouble figuring why when a message from a non-member sent to my lists does not immediately bounce back to the sender saying, You are not a member. Also, I have a lot of held messages in qfiles/*/* and data/*. How can I manually process those? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: I am having trouble figuring why when a message from a non-member sent to my lists does not immediately bounce back to the sender saying, You are not a member. If that's what you want, you need to set Privacy options...-Sender filters-generic_nonmember_action) to Reject. Does not work? I was hoping there was something I was missing but apparently not. I do not receive the reject messag until about 4 or 6 hours later. Which is what led into the below question. Also, I have a lot of held messages in qfiles/*/* and data/*. How can I manually process those? The data/heldmsg-list_name-*.pck files are messages for list_name that are waiting moderator approval. Go to the list's admindb page and accept/reject/discard them as appropriate. In which qfiles/ directory do you find messages. Other than messages currently in process, there should only be messages in qfiles/shunt/ and maybe qfiles/retry/. If there are old messages in other queues, not all your qrunners are running. Messages in the retry queue are failed deliveries that will be periodically retried until DELIVERY_RETRY_PERIOD (default 5 days) elapses. if there are messages older than that, RetryRunner isn't running. Messages in the shunt queue were placed there because of some error which will have been logged in the 'error' log. They can be reprocessed with bin/unshunt, but if the underlying error hasn't been addressed, they will just be shunted again. Also bin/dumpdb and bin/show_qfiles are useful for looking at these files. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: If that's what you want, you need to set Privacy options...-Sender filters-generic_nonmember_action) to Reject. Does not work? I was hoping there was something I was missing but apparently not. I do not receive the reject messag until about 4 or 6 hours later. Which is what led into the below question. So it actually does work, but you have a problem with delayed deliveries. This is probably not a Mailman issue per se, but looking into the qfiles/ entries may indicate a Mailman problem. Otherwise, this may be a Mailman/MTA integration issue or it may be strictly in the outgoing MTA or beyond. Does your outgoing mail go through your ISP and if so, does the ISP limit outgoing mail somehow? Note that this can be the case even if you have your own outgoing MTA. Some ISPs intercept ALL port 25 connects and route them through their own server. Thank you Mark... I have full control of the MTA and I am using PostFix. I should tell you that ... 1) I do not have bounce processing enabled within Mailman 2) The mailing lists have been migrated from older versions mailman and have been cleaned up. 3) When typing, mailq, on the server, it does not list the corresponding held messages. These are message Mailman has in its qfiles that PostFix does not know about. Thanks .. LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: 3) When typing, mailq, on the server, it does not list the corresponding held messages. These are message Mailman has in its qfiles that PostFix does not know about. In which qfiles? If it is qfiles/retry/*, then the message has been queued for retry because the original MTA delivery attempt resulted in a transient error. The reason is logged in Mailman's smtp-failure log. If it is some other queue, that that queue's runner is not doing its job. Have you set QRUNNER_SLEEP_TIME in mm_cfg.py to some large value? No, that has been modified. LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote: Lawrence Bowie I have not tried the above but it is asking for confirmation because the posts are from legitimate automatic engines that send email. The list does not know how to distinguish between SPAM and a legitimate automatic post. Any ideas on resolving this dilemma? Posts which are held because of being from a non-member are only held based on the calculated 'sender' of the message which in turn is based on only a few message headers which all looked OK in your sample message. I can understand your reluctance to patch the code, but at least look in the 'vette' log and see what the entry there reports as the sender of the held post. In the vette log, I am seeing these messages from the automatic posts ... Feb 06 06:13:14 2006 (17698) mail-list post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Message has implicit destination -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: Lawrence Bowie wrote: These are message Mailman has in its qfiles that PostFix does not know about. In which qfiles? If it is qfiles/retry/*, then the message has been queued for retry because the original MTA delivery attempt resulted in a transient error. The reason is logged in Mailman's smtp-failure log. If it is some other queue, that that queue's runner is not doing its job. Have you set QRUNNER_SLEEP_TIME in mm_cfg.py to some large value? No, that has been modified. So let's see if I get the situation. A nonmember send a post to a list. A reject message is generated and is queued within Mailman and takes several hours to be delivered, meanwhile it sits in some queue in mailman. Is that correct? Yes, that is correct. In which queue do you find it? the out queue Are there any relevant messages in any of Mailman's logs, particularly 'locks', 'qrunner', 'error' and 'smtp-failure'? Nothing good in qrunner, locks or error. smtp-failure has legitimate failures of domain not found or rejected remote delivery (due to non-existent recipient) -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: In which queue do you find it? the out queue Are there any relevant messages in any of Mailman's logs, particularly 'locks', 'qrunner', 'error' and 'smtp-failure'? Nothing good in qrunner, locks or error. smtp-failure has legitimate failures of domain not found or rejected remote delivery (due to non-existent recipient) So are there multiple messages in the out queue? Is there a backlog? Does the 'smtp' log indicate that processing is going as fast as it can, i.e. for sequential entries in the 'smtp' log is the time between the time stamp of one entry and that of the next roughly equal to the processing time in the first entry? And, do these times seem long. See the 'performance' related FAQ entries. These may be out of date (6.6 in particular), but 4.11 and 6.4 may be useful. Here is a recent post to a test list and it NEVER hit my mail server as reject. It never even hit the postfix mailq. --===0209451863==-- qfiles/out/1139292738.257997+63ebc154352008cb297bd321d3651ab6f813ff18.pck Subject: test is From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary0562359899== Message-ID: [EMAIL PROTECTED] Date: Mon, 06 Feb 2006 22:12:18 -0800 Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.5 List-Id: test-list.lists.mydomain.org X-List-Administrivia: yes --===0562359899== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] --===0562359899== Content-Type: message/rfc822 MIME-Version: 1.0 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from localhost (localhost.localdomain [127.0.0.1]) by lists.mydomain.org (Postfix) with ESMTP id 7692A678114 for [EMAIL PROTECTED]; Mon, 6 Feb 2006 22:12:17 -0800 (PST) Received: from lists.mydomain.org ([127.0.0.1]) by localhost (lists.mydomain.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09593-02 for [EMAIL PROTECTED]; Mon, 6 Feb 2006 22:12:17 -0800 (PST) Received: by lists.mydomain.org (Postfix, from userid 1005) id 4FD33678118; Mon, 6 Feb 2006 22:12:17 -0800 (PST) Received: from master.otherdomain.org (v757223.fromhere.com [xxx.xxx.xx.xxx]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.mydomain.org (Postfix) with ESMTP id CD97A678114 for [EMAIL PROTECTED]; Mon, 6 Feb 2006 22:12:15 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by master.otherdomain.org (Postfix) with ESMTP id BD3BF46890D for [EMAIL PROTECTED]; Tue, 7 Feb 2006 00:12:14 -0600 (CST) Received: from master.otherdomain.org ([127.0.0.1]) by localhost (master.ldb-jab.org [209.135.157.157]) (amavisd-new, port 10024) with ESMTP id 18443-08 for [EMAIL PROTECTED]; Tue, 7 Feb 2006 00:12:13 -0600 (CST) Received: by master.otherdomain.org (Postfix, from userid 51) id 978E0469253; Tue, 7 Feb 2006 00:12:13 -0600 (CST) Received: from [10.3.3.7] (pool-70-105-21-105.rich.east.verizon.net [70.105.21.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by master.otherdomain.org (Postfix) with ESMTP id 0467946890D for [EMAIL PROTECTED]; Tue, 7 Feb 2006 00:12:11 -0600 (CST) Message-ID: [EMAIL PROTECTED] Date: Tue, 07 Feb 2006 01:13:07 -0500 From: LDB [EMAIL PROTECTED] User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050715) X-Accept-Language: en-us, en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: test is Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at ldb-jab.org X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on lists.mydomain.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham version=3.0.3 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lists.mydomain.org sd --===0562359899==-- -- 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
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: In which queue do you find it? the out queue Are there any relevant messages in any of Mailman's logs, particularly 'locks', 'qrunner', 'error' and 'smtp-failure'? Nothing good in qrunner, locks or error. smtp-failure has legitimate failures of domain not found or rejected remote delivery (due to non-existent recipient) So are there multiple messages in the out queue? Is there a backlog? Does the 'smtp' log indicate that processing is going as fast as it can, i.e. for sequential entries in the 'smtp' log is the time between the time stamp of one entry and that of the next roughly equal to the processing time in the first entry? And, do these times seem long. nothing in the mailq at all for postfix. no backlog at all. Hardly anything is running this time of night. The mail and list server are two different servers. See the 'performance' related FAQ entries. These may be out of date (6.6 in particular), but 4.11 and 6.4 may be useful. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not a list member notification email
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: In which queue do you find it? the out queue Are there any relevant messages in any of Mailman's logs, particularly 'locks', 'qrunner', 'error' and 'smtp-failure'? Nothing good in qrunner, locks or error. smtp-failure has legitimate failures of domain not found or rejected remote delivery (due to non-existent recipient) So are there multiple messages in the out queue? Is there a backlog? Does the 'smtp' log indicate that processing is going as fast as it can, i.e. for sequential entries in the 'smtp' log is the time between the time stamp of one entry and that of the next roughly equal to the processing time in the first entry? And, do these times seem long. See the 'performance' related FAQ entries. These may be out of date (6.6 in particular), but 4.11 and 6.4 may be useful. It just flushed like you crazy!! I changed my SMTP port in Mailman from the default to 10025 (for amavisd). That was the only real change. I hope that did it ... LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote: Lawrence Bowie wrote: In the vette log, I am seeing these messages from the automatic posts ... Feb 06 06:13:14 2006 (17698) mail-list post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Message has implicit destination So the post is held because the list posting address is not in a To: or Cc: header of the post, not because [EMAIL PROTECTED] is not a member. If you want these posts to go to the list without being held for moderator approval, here are your choices. 1)Arrange for the automated sender to put the list posting address in a To: or Cc: header in the message, or 2)go to the list's Privacy options...-Recipient filters page and either set require_explicit_destination to No or add the actual To: address of the message or a regular expression that matches it to acceptable_aliases. Perfect .. Thank you sir .. LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote:
Lawrence Bowie wrote:
[EMAIL PROTECTED] is the subscribed address.
The headers are as follows:
From [EMAIL PROTECTED] Fri Jan 27 19:25:04 2006
Return-Path: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost.localdomain [127.0.0.1])
by lists.domain.org (Postfix) with ESMTP id 990FD6780B0
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: from lists.domain.org ([127.0.0.1])
by localhost (lists.domain.org [127.0.0.1]) (amavisd-new,
port 10024) with ESMTP id 11514-08
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: by lists.domain.org (Postfix, from userid 1005)
id 51999678112; Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: from mail.domain.org (mail.domain.org [216.93.165.132])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by lists.domain.org (Postfix) with ESMTP id 395866780A9
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Received: by mail.domain.org (Postfix)
id 1D7E0128004; Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.domain.org (Postfix) with ESMTP id 0F527850439
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Received: from mail.domain.org ([127.0.0.1])
by localhost (mail.domain.org [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id 11298-09 for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:02 -0800 (PST)
Received: by mail.domain.org (Postfix, from userid 1005)
id ED9CE850E5C; Fri, 27 Jan 2006 19:25:02 -0800 (PST)
Received: from base2.domain.org (gforge.domain.org
[207.235.77.148])
by mail.domain.org (Postfix) with ESMTP id 6EA40850439
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:01 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=base2.domain.org)
by hostname.domain.org with esmtp (Exim 3.36 #1 (Debian))
id 1F2ghw-0001Qk-00 for [EMAIL PROTECTED];
Fri, 27 Jan 2006 22:25:00 -0500
From: User Name [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
It certainly looks as though that should have been accepted.
What is in Mailman's 'vette' log for this post? If that doesn't provide
the answer, I would try the following:
In Mailman/Handlers/Moderate.py, find the following:
else:
sender = msg.get_sender()
# From here on out, we're dealing with non-members.
Change the this to:
else:
sender = msg.get_sender()
# From here on out, we're dealing with non-members.
syslog('vette',
'Non member post. get_senders() = %s get_sender() = %s',
str(msg.get_senders()), sender)
-
This will create an entry in the 'vette' log (preceding the normal held
post entry) for every non-member post. which in addition to the
'sender' from get_sender() also contains the list of senders from
get_senders(). It is this list that is validated for membership. The
post is considered from a list member if any of the get_senders()
addresses is a list member.
I have not tried the above but it is asking for confirmation because the posts
are from legitimate automatic engines that send email. The list does not know
how to distinguish between SPAM and a legitimate automatic post.
Any ideas on resolving this dilemma?
Thanks,
LDB
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote:
Lawrence Bowie wrote:
OK .. Here is the reason it says ..
Reason: Post by non-member to a members-only list
but he is a member of the list. Are headers necessary for you guys to see?
What is the subscribed address?
What are the following headers in the message
From:
Reply-To:
Sender:
Return-Path:
and the From_ separator in a mailbox file if any.
And have you made any changes to the default
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
(above from Defaults.py)
Here are my settings .. USE_ENVELOPE_SENDER description is seemingly the
problem
I am having. But I have it set to, No. ... Maybe I am interpreting it wrong ..
# When allowing only members to post to a mailing list, how is the sender of
# the message determined? If this variable is set to Yes, then first the
# message's envelope sender is used, with a fallback to the sender if there is
# no envelope sender. Set this variable to No to always use the sender.
#
# The envelope sender is set by the SMTP delivery and is thus less easily
# spoofed than the sender, which is typically just taken from the From: header
# and thus easily spoofed by the end-user. However, sometimes the envelope
# sender isn't set correctly and this will manifest itself by postings being
# held for approval even if they appear to come from a list member. If you
# are having this problem, set this variable to No, but understand that some
# spoofed messages may get through.
USE_ENVELOPE_SENDER = No
# Membership tests for posting purposes are usually performed by looking at a
# set of headers, passing the test if any of their values match a member of
# the list. Headers are checked in the order given in this variable. The
# value None means use the From_ (envelope sender) header. Field names are
# case insensitive.
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
LDB
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Lawrence Bowie wrote:
Mark Sapiro wrote:
Lawrence Bowie wrote:
OK .. Here is the reason it says ..
Reason: Post by non-member to a members-only list
but he is a member of the list. Are headers necessary for you guys to see?
What is the subscribed address?
What are the following headers in the message
From:
Reply-To:
Sender:
Return-Path:
and the From_ separator in a mailbox file if any.
And have you made any changes to the default
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
(above from Defaults.py)
Here are my settings .. USE_ENVELOPE_SENDER description is seemingly the
problem
I am having. But I have it set to, No. ... Maybe I am interpreting it wrong
..
# When allowing only members to post to a mailing list, how is the sender of
# the message determined? If this variable is set to Yes, then first the
# message's envelope sender is used, with a fallback to the sender if there is
# no envelope sender. Set this variable to No to always use the sender.
#
# The envelope sender is set by the SMTP delivery and is thus less easily
# spoofed than the sender, which is typically just taken from the From: header
# and thus easily spoofed by the end-user. However, sometimes the envelope
# sender isn't set correctly and this will manifest itself by postings being
# held for approval even if they appear to come from a list member. If you
# are having this problem, set this variable to No, but understand that some
# spoofed messages may get through.
USE_ENVELOPE_SENDER = No
# Membership tests for posting purposes are usually performed by looking at a
# set of headers, passing the test if any of their values match a member of
# the list. Headers are checked in the order given in this variable. The
# value None means use the From_ (envelope sender) header. Field names are
# case insensitive.
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
LDB
--
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/ldb%40freestandards.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
I forgot to mention that the posts are coming from the local servers on the
network within the same domain.
Thanks,
LDB
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Daan Hoogland wrote: I've seen a similar thing. I've got allow regexpes like [EMAIL PROTECTED] I have to approve post from those addresses as well. I tried putting the list of addresses that match the regexp in the allow, but no change noticeable. On 28 Jan,2006, at 1:32 AM, Lawrence Bowie wrote: Mark Sapiro wrote: Lawrence Bowie wrote: I have users subscribe to a list but yet I always have to approve their posts for some reason. For what reason? Every hold has a reason, what is this one? And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? The check box to accept future posts only applies to non-members. I'm guessing that your new members are moderated because Privacy options...-Sender filters-default_member_moderation is set to Yes. If this is not what you want, set it to No and then on Membership Management...-Membership List under Additional Member Tasks - Set everyone's moderation bit, including those members not currently visible, select No and click Set. Thanks for replying. That has already been done. There is something wrong. Everyone is subscribed to the list as memebers and they are posting with the same email as on the membership list. Has anyone seen this before. Very weird ... LDB -- 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/ mailman-owner%40hobby.nl Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? req=showamp;file=faq01.027.htp Yep .. I tried that as well to no avail at all. LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote:
Lawrence Bowie wrote:
OK .. Here is the reason it says ..
Reason: Post by non-member to a members-only list
but he is a member of the list. Are headers necessary for you guys to see?
What is the subscribed address?
What are the following headers in the message
From:
Reply-To:
Sender:
Return-Path:
and the From_ separator in a mailbox file if any.
And have you made any changes to the default
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
(above from Defaults.py)
[EMAIL PROTECTED] is the subscribed address.
The headers are as follows:
From [EMAIL PROTECTED] Fri Jan 27 19:25:04 2006
Return-Path: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost.localdomain [127.0.0.1])
by lists.domain.org (Postfix) with ESMTP id 990FD6780B0
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: from lists.domain.org ([127.0.0.1])
by localhost (lists.domain.org [127.0.0.1]) (amavisd-new,
port 10024) with ESMTP id 11514-08
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: by lists.domain.org (Postfix, from userid 1005)
id 51999678112; Fri, 27 Jan 2006 19:25:04 -0800 (PST)
Received: from mail.domain.org (mail.domain.org [216.93.165.132])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by lists.domain.org (Postfix) with ESMTP id 395866780A9
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Received: by mail.domain.org (Postfix)
id 1D7E0128004; Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.domain.org (Postfix) with ESMTP id 0F527850439
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:03 -0800 (PST)
Received: from mail.domain.org ([127.0.0.1])
by localhost (mail.domain.org [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id 11298-09 for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:02 -0800 (PST)
Received: by mail.domain.org (Postfix, from userid 1005)
id ED9CE850E5C; Fri, 27 Jan 2006 19:25:02 -0800 (PST)
Received: from base2.domain.org (gforge.domain.org
[207.235.77.148])
by mail.domain.org (Postfix) with ESMTP id 6EA40850439
for [EMAIL PROTECTED];
Fri, 27 Jan 2006 19:25:01 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=base2.domain.org)
by hostname.domain.org with esmtp (Exim 3.36 #1 (Debian))
id 1F2ghw-0001Qk-00 for [EMAIL PROTECTED];
Fri, 27 Jan 2006 22:25:00 -0500
From: User Name [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
--
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=showamp;file=faq01.027.htp
[Mailman-Users] Weirdness
Team: I have some issues with my mailing list. I have users subscribe to a list but yet I always have to approve their posts for some reason. And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote: Lawrence Bowie wrote: I have users subscribe to a list but yet I always have to approve their posts for some reason. For what reason? Every hold has a reason, what is this one? And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? The check box to accept future posts only applies to non-members. I'm guessing that your new members are moderated because Privacy options...-Sender filters-default_member_moderation is set to Yes. If this is not what you want, set it to No and then on Membership Management...-Membership List under Additional Member Tasks - Set everyone's moderation bit, including those members not currently visible, select No and click Set. Thanks for replying. That has already been done. There is something wrong. Everyone is subscribed to the list as memebers and they are posting with the same email as on the membership list. Has anyone seen this before. Very weird ... LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote: Lawrence Bowie wrote: I have users subscribe to a list but yet I always have to approve their posts for some reason. For what reason? Every hold has a reason, what is this one? And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? The check box to accept future posts only applies to non-members. I'm guessing that your new members are moderated because Privacy options...-Sender filters-default_member_moderation is set to Yes. If this is not what you want, set it to No and then on Membership Management...-Membership List under Additional Member Tasks - Set everyone's moderation bit, including those members not currently visible, select No and click Set. The next time someone posts I can give you that reason. :) So hang a while, please. In the meantime, I have data in /var/lib/mailman/data/ starting with heldmsg-*. Most of it, if not all is SPAM. I can safely get rid of it without adversely affecting the lists, right? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Lawrence Bowie wrote: Mark Sapiro wrote: Lawrence Bowie wrote: I have users subscribe to a list but yet I always have to approve their posts for some reason. For what reason? Every hold has a reason, what is this one? And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? The check box to accept future posts only applies to non-members. I'm guessing that your new members are moderated because Privacy options...-Sender filters-default_member_moderation is set to Yes. If this is not what you want, set it to No and then on Membership Management...-Membership List under Additional Member Tasks - Set everyone's moderation bit, including those members not currently visible, select No and click Set. The next time someone posts I can give you that reason. :) So hang a while, please. In the meantime, I have data in /var/lib/mailman/data/ starting with heldmsg-*. Most of it, if not all is SPAM. I can safely get rid of it without adversely affecting the lists, right? Thanks, LDB -- 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/ldb%40freestandards.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp nevermind .. dumb question .. LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Weirdness
Mark Sapiro wrote: Lawrence Bowie wrote: I have users subscribe to a list but yet I always have to approve their posts for some reason. For what reason? Every hold has a reason, what is this one? And when I do have it accept this address for future posts, it still emails me to apporove it. Any ideas??? The check box to accept future posts only applies to non-members. I'm guessing that your new members are moderated because Privacy options...-Sender filters-default_member_moderation is set to Yes. If this is not what you want, set it to No and then on Membership Management...-Membership List under Additional Member Tasks - Set everyone's moderation bit, including those members not currently visible, select No and click Set. OK .. Here is the reason it says .. Reason: Post by non-member to a members-only list but he is a member of the list. Are headers necessary for you guys to see? Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] additional accounts
Glenn Sieb wrote: Lawrence Bowie said the following on 1/20/2006 7:26 PM: If create a mailing list called test-list, then do I have to create aliases like this Hey Lawrence! If you take a look in $PREFIX/mailman/data/aliases, you'll see that Mailman's nice enough to do it for you :-) Just make sure you include $PREFIX/mailman/data/aliases in your main /etc/aliases file. (Refer to your MTA's documenation for how to do this.) However, if you're using Postfix, you have two options that I know of: At the end of /etc/aliases: :include: $PREFIX/mailman/data/aliases ...or go here: http://www.gurulabs.com/goodies/downloads.php and grab a copy of postfix-to-mailman-2.1.py and read the instructions within. :) Best! --Glenn Thank you for the help Glenn .. LDB -- 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=showamp;file=faq01.027.htp
[Mailman-Users] additional accounts
If create a mailing list called test-list, then do I have to create aliases like this mailman: |/var/lib/mailman/mail/mailman post mailman mailman-admin:|/var/lib/mailman/mail/mailman admin mailman mailman-bounces: |/var/lib/mailman/mail/mailman bounces mailman mailman-confirm: |/var/lib/mailman/mail/mailman confirm mailman mailman-join: |/var/lib/mailman/mail/mailman join mailman mailman-leave:|/var/lib/mailman/mail/mailman leave mailman mailman-owner:|/var/lib/mailman/mail/mailman owner mailman mailman-request: |/var/lib/mailman/mail/mailman request mailman mailman-subscribe:|/var/lib/mailman/mail/mailman subscribe mailman mailman-unsubscribe: |/var/lib/mailman/mail/mailman unsubscribe mailman for test-list ... test-list: |/var/lib/mailman/mail/mailman post test-list test-list-admin:|/var/lib/mailman/mail/mailman admin test-list test-list-bounces: |/var/lib/mailman/mail/mailman bounces test-list test-list-confirm: |/var/lib/mailman/mail/mailman confirm test-list test-list-join: |/var/lib/mailman/mail/mailman join test-list test-list-leave:|/var/lib/mailman/mail/mailman leave test-list test-list-owner:|/var/lib/mailman/mail/mailman owner test-list test-list-request: |/var/lib/mailman/mail/mailman request test-list test-list-subscribe:|/var/lib/mailman/mail/mailman subscribe test-list test-list-unsubscribe: |/var/lib/mailman/mail/mailman unsubscribe test-list Thanks, LDB -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.db and config.db.last
Excellent!!! That is the answer I was expecting. Thank you very much for the clear explanation. LDB Mark Sapiro wrote: Lawrence Bowie wrote: The above are missing for several of my mailing lists. How do I remedy this dilemma? Do I HAVE to recreate the lists? If you do anything, it should be deletion of them from the lists that contain them. config.db files are an older format that was changed to the current config.pck format in Mailman 2.1. When your Mailman was first upgraded to 2.1.x, the config.db files were converted to config.pck files. New lists won't have them and they can be safely deleted from old lists as long as the config.pck files are there, and if the config.pck files aren't there, the list hasn't been accessed since pre 2.1. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] config.db and config.db.last
The above are missing for several of my mailing lists. How do I remedy this dilemma? Do I HAVE to recreate the lists? Thanks, LDB -- 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=showamp;file=faq01.027.htp
