Mark Sapiro wrote:
Mark Sapiro wrote:
You can still do it, but your Approved: line must be in a message sent
to the listname-request and with the subject of the sub-part
message, i.e. confirm 40 digit hex token (perhaps preceded by Re
:, but not by Re : .
I think I fumble
This one has me completely baffled. Whenever a mail is hitting one of my
lists, I'm getting an undeliverable bounce message. The message comes
from [EMAIL PROTECTED], and the body of the mail states:
The message that you sent was undeliverable to the following:
bhaggett (UNUSED)
Many thanks for the good and informational answer. I'll be upgrading to
2.1.9 soon so will check it out as well
thanks
Mark Sapiro wrote:
martin moriarty wrote:
We're running mailman 2.1.5 successfully here. Weve a particular problem
with viewing attachments from arhives in a moderated
Martin Dennett writes:
There is no other information in the bounce message, so how do I
find out who the message is really trying to be delivered to?
You can start by tracing the headers in the bounce message, but they
probably don't help. Then you'll have to reconfigure your list to use
i'm using mailman 2.1.7 on fedora core 5
i want to know where does the mailman save the email adresses of the
members? (the location of the file if it saves it in a file?)
thanks
--
Mailman-Users mailing list
Mailman-Users@python.org
How can I as a list administrator re-enable or more correctly re-set a
given users bounce score. In this case the causes of the bounces is out
of the users hands. I cannot see a way to do this in the web interface
of on the FAQ/googling etc.
Regards
Hi there
We run a multitude ( 20+) of mailman lists, some moderated, and some
unmoderated. In each case we would like to discard those previously
identified as spam by spam assassin. We run Mailman Version 2.1.5. Ive
added in spam filter rules/expression: X-SPAM-FLAG:YES . Seems to work
for a
I must have messed up a setting on my mailman server because none of the
requests sent by email are being processed.
When I send a subscribe request to: [EMAIL PROTECTED] I see
my Postfix server relaying the message to the mailman server,
How? Is it piping the message to |
At 7:23 AM +0100 10/4/06, Martin Dennett wrote:
There is no other information in the bounce message, so how do I
find out who the message is really trying to be delivered to?
This kind of problem is what VERP was designed to make much easier to
detect. Check the relevant FAQ entries on
If the message is being piped correctly, see if it is sitting in
qfiles/commands/. If so, then as Glen suggests in another reply, make
sure CommandRunner is running.
There are a bunch of files sitting in the qfiles/commands directory.
How do I make sure CommandRunner is running?
Got it. I
Thanks, Mark,
Mark Sapiro wrote:
I assume you are using header_filter_rules, not bounce_matching_headers.
Correct.
Since by default, membership tests are done before
bounce_matching_headers, you could use bounce_matching_headers to hold
the spam and the test will be done after
Mohamed Mostafa wrote:
i'm using mailman 2.1.7 on fedora core 5
i want to know where does the mailman save the email adresses of the
members? (the location of the file if it saves it in a file?)
Mailman saves all list configuration information as a Python pickle in
the file
Robert Bannocks wrote:
How can I as a list administrator re-enable or more correctly re-set a
given users bounce score. In this case the causes of the bounces is out
of the users hands. I cannot see a way to do this in the web interface
of on the FAQ/googling etc.
Go to the admin Membership
Hello,
I'm trying to move our current nfs-based mailman setup (where we have
separate mail and web servers and mailman files on nfs) to a dedicated
mailman machine (where our mail and web servers will forward and
proxy, respectively, mailman requests to the mailman machine).
For mail, I have set
Ki Song wrote:
Got it. I just restarted mailmanctl and it is running smoothly.
How come this process is not running by default?
How can I make sure that the next time the system is rebooted, that
mailmanctl starts on boot?
It probably does. If not, you probably want to install the
Here's a related question:
I run a list of about 2300 subscribers, of whom perhaps a third are using
Comcast services. Lately, Comcast has been blocking messages from this
list, probably because someone reported the list as spam once. All our
efforts to persuade Comcast that the 2300
Peter Davis wrote:
Is there a fast way? Is there a way to automatically un-bounce all bouncing
members?
Without command line access which I gather you don't have, you can do
it by scripting the web interface which leads to the answer below.
I realize this won't solve the Comcast problem.
Mark Sapiro wrote:
In any case, the '^' was not the
critical change to your pattern; it is changing '\s' to '\s*' (which
will also allow '\r' at the end that is critical.
Just to be sure there's no misunderstanding, the above should have said
In any case, the '^' was not the
critical change to
martin moriarty wrote:
We run Mailman Version 2.1.5. Ive
added in spam filter rules/expression: X-SPAM-FLAG:YES . Seems to work
for a while, then stops working.
This is a bug in 2.1.5, partially fixed in 2.1.6 and completely fixed
in 2.1.7. See
K. Clair wrote:
For mail, I have set up virtual domain aliases on our mail servers to
forward mail to lists at virtual domains to the local list aliases on
the mailman machine, for example:
[EMAIL PROTECTED] - [EMAIL PROTECTED]
[EMAIL PROTECTED] - [EMAIL PROTECTED]
etc...
When I try to submit a
On 10/4/06, Mark Sapiro [EMAIL PROTECTED] wrote:
K. Clair wrote:
For mail, I have set up virtual domain aliases on our mail servers to
forward mail to lists at virtual domains to the local list aliases on
the mailman machine, for example:
[EMAIL PROTECTED] - [EMAIL PROTECTED]
[EMAIL
K. Clair wrote:
Oh, ok! So there was a second problem with my installation, which I
was going to send in a separate email, which seems to be the only real
problem. Which is that the email addresses in subscribe requests are
being altered as such:
[EMAIL PROTECTED] becomes [EMAIL PROTECTED]
I am getting permission issues when trying to create a new list. There is no
authentication to prove my access status, any advice?
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
The League CA Cities wrote:
I am getting permission issues when trying to create a new list. There is no
authentication to prove my access status, any advice?
Are you providing List creator's (authentication) password: at the
bottom of the list create form? This must be Mailman's site password
At 12:21 PM -0700 10/2/06, Mark Sapiro wrote:
Mailman's archives are threaded based on the Message-ID: of one post
being in either the In-Reply-To: or References: header (or both) of a
subsequent post.
This is an incomplete solution fo a number of reasons including:
1) Not all MUAs include
Mark Sapiro writes:
Then each subsequent mail found a 'cached' block and was itself
blocked and also updated the cache expiration. When I stopped
sending for over a week, the cached entry finally expired.
This would be a serious violation of cache semantics, though. If the
bug occurred at
Brad Knowles wrote:
At 7:23 AM +0100 10/4/06, Martin Dennett wrote:
There is no other information in the bounce message, so how do I
find out who the message is really trying to be delivered to?
This kind of problem is what VERP was designed to make much easier to
detect. Check the
27 matches
Mail list logo
