By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,660 Members | 1,102 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,660 IT Pros & Developers. It's quick & easy.

To the python-list moderator

P: n/a
For a couple of years, I have been reading and posting and posting to
python-list and c.l.p via gmane.news.orgs gmane.comp.python.general group.
Today I got this from 'python-list-bounces', which I presume is a 'machine'
rather than a 'human' address.

---------------------------
Your mail to 'Python-list' with the subject

Re: how to join two Dictionary together?

Is being held until the list moderator can review it for approval.

The reason it is being held:

Message has a suspicious header

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.
-----------------------------

Since I had nothing to do with the headers, the problem is between gmane's
sending (perhaps when responding to a message from a particular site) and
your review. I hope this can be fixed.

Terry J. Reedy
Aug 31 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
This is probably a fairly bad way of contacting the python-list
admins...

"Terry Reedy" <tj*****@udel.edu> writes:
For a couple of years, I have been reading and posting and posting to
python-list and c.l.p via gmane.news.orgs gmane.comp.python.general group.
Today I got this from 'python-list-bounces', which I presume is a 'machine'
rather than a 'human' address.

---------------------------
Your mail to 'Python-list' with the subject

Re: how to join two Dictionary together?

Is being held until the list moderator can review it for approval.

The reason it is being held:

Message has a suspicious header

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.
-----------------------------

Since I had nothing to do with the headers, the problem is between gmane's
sending (perhaps when responding to a message from a particular site) and
your review. I hope this can be fixed.


It's probably been flagged as UNSURE by spambayes.

Cheers,
mwh

--
You owe The Oracle a TV with an 'intelligence' control - I've
tried 'brightness' but that didn't work.
-- Internet Oracularity #1192-01
Aug 31 '05 #2

P: n/a

"Michael Hudson" <mw*@python.net> wrote in message
news:m2************@82-33-185-193.cable.ubr01.azte.blueyonder.co.uk...
This is probably a fairly bad way of contacting the python-list
admins...
Perhaps. Feel free to forward if you know a better way.

As I noted ...
"Terry Reedy" <tj*****@udel.edu> writes:
For a couple of years, I have been reading and posting and posting to
python-list and c.l.p via gmane.news.orgs gmane.comp.python.general
group.
Today I got this from 'python-list-bounces', which I presume is a
'machine'
rather than a 'human' address.
If there had been an address that I thought would reach the appropriate
person, I would have used it. But public posting allows comments by others
as to similar problems, like Gregory's.
---------------------------
Your mail to 'Python-list' with the subject

Re: how to join two Dictionary together?

Is being held until the list moderator can review it for approval.

The reason it is being held:

Message has a suspicious header

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.
-----------------------------
This has a distinct 'don't call us, we'll maybe call you flavor. As of
now, my post seems to still be in limbo (not on c.l.p and no notification).
Since I had nothing to do with the headers, the problem is between
gmane's
sending (perhaps when responding to a message from a particular site)
and
your review. I hope this can be fixed.


It's probably been flagged as UNSURE by spambayes.


As I said, I hope the mismatch between legitimate senders and reviewer can
be fixed.

Terry J. Reedy

Aug 31 '05 #3

P: n/a
On Wednesday 31 August 2005 11:29 am, Terry Reedy wrote:
For a couple of years, I have been reading and posting and posting to
python-list and c.l.p via gmane.news.orgs gmane.comp.python.general group.
Today I got this from 'python-list-bounces', which I presume is a 'machine'
rather than a 'human' address.


I got one of these too, recently. Maybe somebody is turning up the
screws to get rid of spam that's been appearing on the list?

--
Terry Hancock ( hancock at anansispaceworks.com )
Anansi Spaceworks http://www.anansispaceworks.com

Aug 31 '05 #4

P: n/a
> > This is probably a fairly bad way of contacting the python-list
admins...
Perhaps. Feel free to forward if you know a better way.


I tried sending a question to py***************@python.org, and got
another 'don't call us, we'll maybe call you'. Maybe
po********@python.org?
But public posting allows comments by others
as to similar problems, like Gregory's.


And mine. FWIW, I'm posting direct to the mailing list with
mutt/postfix. Since I *do* have concrol over my headers, it would be
nice to see what header is 'suspicious', so I could possibly modify it.

It'll be interesting to see if this post makes it to the list...

-John
Aug 31 '05 #5

P: n/a
Terry Hancock wrote:
I got one of these too, recently. Maybe somebody is turning up the
screws to get rid of spam that's been appearing on the list?


I've been getting these about once a day lately. at first, I suspected
some kind of "you're posting to quickly"-filter with a manual "okay,
you're whitelisted for another 24 hours" setup, but it seems to block
messages mostly by random. and some messages don't seem to get
through at all. slightly annoying.

</F>

Sep 1 '05 #6

P: n/a

Fredrik> Terry Hancock wrote:
I got one of these too, recently. Maybe somebody is turning up the
screws to get rid of spam that's been appearing on the list?


Fredrik> I've been getting these about once a day lately. at first, I
Fredrik> suspected some kind of "you're posting to quickly"-filter with
Fredrik> a manual "okay, you're whitelisted for another 24 hours" setup,
Fredrik> but it seems to block messages mostly by random. and some
Fredrik> messages don't seem to get through at all. slightly annoying.

I think it's just that the SpamBayes training database used to check the
list's messages is perhaps getting a little tired.

Skip

Sep 2 '05 #7

P: n/a
Fredrik Lundh <fr*****@pythonware.com> wrote:
Terry Hancock wrote:
I got one of these too, recently. Maybe somebody is turning up the
screws to get rid of spam that's been appearing on the list?

In the future, sending a message to po********@python.org is
suggested rather than posting to only to python-list. What's
happening is that Spambayes is marking the message as UNSURE. The
message that mailman sends to the sender is unfortunate. The
"Message has a suspicious header" notice is misleading because the
user did not have any header in their message that caused it to be
held (at least normally not).

I'm not sure why many legitimate messages are being flagged as
UNSURE. I'll look into it.
I've been getting these about once a day lately. at first, I suspected
some kind of "you're posting to quickly"-filter with a manual "okay,
you're whitelisted for another 24 hours" setup, but it seems to block
messages mostly by random. and some messages don't seem to get
through at all. slightly annoying.


Hmm, the message should eventually get through since it ends up
getting moderated by a person. Maybe they are getting overwhelmed
and are making some mistakes.

Neil
Sep 2 '05 #8

P: n/a

"Neil Schemenauer" <na*@arctrix.com> wrote in message
news:6HZRe.355752$s54.266548@pd7tw2no...
In the future, sending a message to po********@python.org is
suggested rather than posting to only to python-list.
Thank you information. Since python.org is mostly stuff other than the
mailing lists, I did not think of that. Adding it to the CC line for this
reply.
What's
happening is that Spambayes is marking the message as UNSURE. The
message that mailman sends to the sender is unfortunate. The
"Message has a suspicious header" notice is misleading because the
user did not have any header in their message that caused it to be
held (at least normally not).
Is that hardwired into Spambayes or can it be edited.
I'm not sure why many legitimate messages are being flagged as
UNSURE. I'll look into it.
Then my 'misdirected' query will have worked anyway. Thank you.
Hmm, the message should eventually get through since it ends up
getting moderated by a person.
My embargoed reply, which I believe I sent Sunday, was released
mid-Thursday.
Maybe they are getting overwhelmed and are making some mistakes.


Fewer false positives would make life easier for everyone. Perhaps a
whitelist of regular and long-terms posters would help. I think most or
all of the 4 people who responed 'me too' would also qualify.

What still puzzles me is why the spamblocker that embargoed me and others
did not catch such obvious spam as Subject: Re: The penis is way too
delicate for masturbation (and occasional others like this). If you need a
regular c.l.p reader to forward missed spam for addition to the training
base, I would volunteer.

Terry J. Reedy


Sep 2 '05 #9

P: n/a
Terry Reedy wrote:
What's
happening is that Spambayes is marking the message as UNSURE. The
message that mailman sends to the sender is unfortunate. The
"Message has a suspicious header" notice is misleading because the
user did not have any header in their message that caused it to be
held (at least normally not).


Is that hardwired into Spambayes or can it be edited.


it's a mailman thing. I suspect that they run things through spambayes,
and use mailman filters to look for "UNSURE" in the "X-Spam-Status"
header added by spambayes. see e.g.

http://www.python.org/cgi-bin/faqw-m...=faq03.059.htp

I'm pretty sure the python.org administrators have the mailman source
code, so it shouldn't be that hard to fix the message...

</F>

Sep 3 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.