[users] Does the list work?

[David Hrbáč]

Just test. Please ignore.
David Hrb??

[Dag Wieers]

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

[Karanbir Singh]

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

speaking of which, it would be quite nice to get this under monitoring -
but apart from sending an email to the list every 6 hrs from different
places, whats a good way to test that the lists still work ?

At the moment, I've got an age check in /var/mailman/ - but that failed
to spot this problem, since the svn list was indeed getting traffic. So,
the monitoring would need to be per-list.

ideas anyone ?

[Ned Slider]

Post by Karanbir Singh

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

[Karanbir Singh]

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).

the svn list has always had random forged from's spam.

- KB

[Karanbir Singh]

Post by Karanbir Singh
Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

Because of the very nature of lists, perhaps greylisting and uribl might
be worth plumbing in, and.or some form of 'receive' ip BL.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.
I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).
the svn list has always had random forged from's spam.
- KB

My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

[Karanbir Singh]

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.

ideas ?

- KB

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

I'm reluctant to subscribe to the commits list right now, because I
already receive enough spam ATM :-)

[Karanbir Singh]

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)

I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

Thanks!

[Dries Verachtert]

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)

Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.

What do you think?
Karanbir: you think we could use such a solution on the mailman server?

kind regards,
Dries

[Yury V. Zaytsev]

Hi!

So, is there anything that can be done about this now?

I think that by far the easiest solution just to drop everything that is
not coming from svn.rpmforge.net is acceptable, because I've not seen
anybody replying to the commits yet and forwarding the message to the
packagers list is not that much of a hassle, but is actually quite
appropriate.

Karanbir... please?

Thanks!
--
Sincerely yours,
Yury V. Zaytsev

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?
kind regards,
Dries

[Yury V. Zaytsev]

Hi!

So, is there anything that can be done about this now?

I think that by far the easiest solution just to drop everything that is
not coming from svn.rpmforge.net is acceptable, because I've not seen
anybody replying to the commits yet and forwarding the message to the
packagers list is not that much of a hassle, but is actually quite
appropriate.

Karanbir... please?

Thanks!
--
Sincerely yours,
Yury V. Zaytsev

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?
kind regards,
Dries

[Yury V. Zaytsev]

Hi!

So, is there anything that can be done about this now?

I think that by far the easiest solution just to drop everything that is
not coming from svn.rpmforge.net is acceptable, because I've not seen
anybody replying to the commits yet and forwarding the message to the
packagers list is not that much of a hassle, but is actually quite
appropriate.

Karanbir... please?

Thanks!
--
Sincerely yours,
Yury V. Zaytsev

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?
kind regards,
Dries

[Yury V. Zaytsev]

Hi!

So, is there anything that can be done about this now?

I think that by far the easiest solution just to drop everything that is
not coming from svn.rpmforge.net is acceptable, because I've not seen
anybody replying to the commits yet and forwarding the message to the
packagers list is not that much of a hassle, but is actually quite
appropriate.

Karanbir... please?

Thanks!
--
Sincerely yours,
Yury V. Zaytsev

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?
kind regards,
Dries

[Yury V. Zaytsev]

Hi!

So, is there anything that can be done about this now?

I think that by far the easiest solution just to drop everything that is
not coming from svn.rpmforge.net is acceptable, because I've not seen
anybody replying to the commits yet and forwarding the message to the
packagers list is not that much of a hassle, but is actually quite
appropriate.

Karanbir... please?

Thanks!
--
Sincerely yours,
Yury V. Zaytsev

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?
kind regards,
Dries

[Dag Wieers]

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?

Dries hinted this message to me and I have implemented this.

I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

[Yury V. Zaytsev]

Post by Dag Wieers
I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

WOW!!! YAY!!! TADAM!!! Finally, they are usable again!

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.

P.S. One minor glitch though: the following URL from a recent commit
message does not work -

http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/

http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base

Maybe a change to viewvc caused view=auto not to work anymore. I cannot
find this in the ChangeLog though. I will investigate further...

Thanks for reporting !

[Dag Wieers]

Post by Dag Wieers

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/
http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base
Maybe a change to viewvc caused view=auto not to work anymore. I cannot find
this in the ChangeLog though. I will investigate further...

I changed svn-mailer to always use &view=markup in this case (although I
assume that &view=auto was used for newly added files while the default
is &view=diff).

I also reported this to upstream so they are notified of this problem.

Thanks again for reporting !

[Dag Wieers]

Post by Dag Wieers

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/
http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base
Maybe a change to viewvc caused view=auto not to work anymore. I cannot find
this in the ChangeLog though. I will investigate further...

I changed svn-mailer to always use &view=markup in this case (although I
assume that &view=auto was used for newly added files while the default
is &view=diff).

I also reported this to upstream so they are notified of this problem.

Thanks again for reporting !

[Dag Wieers]

Post by Dag Wieers

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/
http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base
Maybe a change to viewvc caused view=auto not to work anymore. I cannot find
this in the ChangeLog though. I will investigate further...

I changed svn-mailer to always use &view=markup in this case (although I
assume that &view=auto was used for newly added files while the default
is &view=diff).

I also reported this to upstream so they are notified of this problem.

Thanks again for reporting !

[Dag Wieers]

Post by Dag Wieers

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/
http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base
Maybe a change to viewvc caused view=auto not to work anymore. I cannot find
this in the ChangeLog though. I will investigate further...

I changed svn-mailer to always use &view=markup in this case (although I
assume that &view=auto was used for newly added files while the default
is &view=diff).

I also reported this to upstream so they are notified of this problem.

Thanks again for reporting !

[Dag Wieers]

Post by Dag Wieers

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/
http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base
Maybe a change to viewvc caused view=auto not to work anymore. I cannot find
this in the ChangeLog though. I will investigate further...

I changed svn-mailer to always use &view=markup in this case (although I
assume that &view=auto was used for newly added files while the default
is &view=diff).

I also reported this to upstream so they are notified of this problem.

Thanks again for reporting !

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/

http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base

Maybe a change to viewvc caused view=auto not to work anymore. I cannot
find this in the ChangeLog though. I will investigate further...

Thanks for reporting !

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/

http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base

Maybe a change to viewvc caused view=auto not to work anymore. I cannot
find this in the ChangeLog though. I will investigate further...

Thanks for reporting !

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/

http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base

Maybe a change to viewvc caused view=auto not to work anymore. I cannot
find this in the ChangeLog though. I will investigate further...

Thanks for reporting !

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.
P.S. One minor glitch though: the following URL from a recent commit
message does not work -
http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

Ouch, that is ugly. Especially since there seems no way to influence the
view-type. According to the documentation it should be using view=diff :-/

http://opensource.perlig.de/svnmailer/doc-1.0/#groups-browser-base

Maybe a change to viewvc caused view=auto not to work anymore. I cannot
find this in the ChangeLog though. I will investigate further...

Thanks for reporting !

[Yury V. Zaytsev]

Post by Dag Wieers
I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

WOW!!! YAY!!! TADAM!!! Finally, they are usable again!

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.

P.S. One minor glitch though: the following URL from a recent commit
message does not work -

http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

[Yury V. Zaytsev]

Post by Dag Wieers
I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

WOW!!! YAY!!! TADAM!!! Finally, they are usable again!

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.

P.S. One minor glitch though: the following URL from a recent commit
message does not work -

http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

[Yury V. Zaytsev]

Post by Dag Wieers
I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

WOW!!! YAY!!! TADAM!!! Finally, they are usable again!

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.

P.S. One minor glitch though: the following URL from a recent commit
message does not work -

http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

[Yury V. Zaytsev]

Post by Dag Wieers
I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

WOW!!! YAY!!! TADAM!!! Finally, they are usable again!

Post by Dag Wieers
So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

Dag, this is really, really, really cool! Thank you very much for your
efforts. Now I am subscribed to the list and it seems to work great.

P.S. One minor glitch though: the following URL from a recent commit
message does not work -

http://svn.rpmforge.net/viewvc/rpmforge/trunk/tools/perl-stuff/gen-rpmforge-rss.pl?rev=8743&view=auto

[Dag Wieers]

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?

Dries hinted this message to me and I have implemented this.

I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

[Dag Wieers]

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?

Dries hinted this message to me and I have implemented this.

I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

[Dag Wieers]

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?

Dries hinted this message to me and I have implemented this.

I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

[Dag Wieers]

Post by Dries Verachtert

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)
Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.
What do you think?
Karanbir: you think we could use such a solution on the mailman server?

Dries hinted this message to me and I have implemented this.

I also implemented svn-mailer with proper From-addresses, set up viewvc
(as it used to be) and recreated the svn-commits archive after I removed
all the SPAM.

So now we get proper commits coming from the commiter, if you reply you
put the packagers-list and the original commiter in copy. The commits now
include a URL to ViewVC. Exactly how I configure it for my customers.

[Dries Verachtert]

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)

Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.

What do you think?
Karanbir: you think we could use such a solution on the mailman server?

kind regards,
Dries

[Dries Verachtert]

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)

Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.

What do you think?
Karanbir: you think we could use such a solution on the mailman server?

kind regards,
Dries

[Dries Verachtert]

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)

Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.

What do you think?
Karanbir: you think we could use such a solution on the mailman server?

kind regards,
Dries

[Dries Verachtert]

Post by Yury V. Zaytsev

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)
I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

First i don't know much about mailman, i've just been searching in
their FAQs and docs :-)

Please have a look at
http://wiki.list.org/pages/viewpage.action?pageId=4030685 (the
paragraph "How to post to the announcement list:") and maybe also
http://wiki.list.org/pages/viewpage.action?pageId=4030556
I guess we could use this for the svn-commits list: no one is allowed
to post to this list (everyone gets moderated) and we change the
hooks/commit-email.pl of the subversion repository so it adds this
'Approved:' header with a password. The drawbacks: the script needs to
contain the mailman password and if you want to reply to an svn commit
mail, then you'll have to forward this to the packagers list.

What do you think?
Karanbir: you think we could use such a solution on the mailman server?

kind regards,
Dries

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)

I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

Thanks!

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)

I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

Thanks!

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)

I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

Thanks!

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

Ah, I see, I'm sorry for misidentifying the problem. Well, then defer
anything except the autogenerated messages by svn.rpmforge.net (local
traffic) sounds like a good idea to me. Please please do :-)

I'd really like to watch the commits lists, but I'm already getting too
much spam for my Bayesian filter to cope with.

Thanks!

[Karanbir Singh]

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

[Karanbir Singh]

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

[Karanbir Singh]

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

[Karanbir Singh]

Post by Yury V. Zaytsev

Post by Karanbir Singh
the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

the spam uses email' addys of people who are subscribed to the list :)

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

I'm reluctant to subscribe to the commits list right now, because I
already receive enough spam ATM :-)

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

I'm reluctant to subscribe to the commits list right now, because I
already receive enough spam ATM :-)

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

I'm reluctant to subscribe to the commits list right now, because I
already receive enough spam ATM :-)

[Yury V. Zaytsev]

Post by Karanbir Singh

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.
ideas ?

Why wouldn't you simply disable posting for non-members of the list?

I'm reluctant to subscribe to the commits list right now, because I
already receive enough spam ATM :-)

[Karanbir Singh]

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.

ideas ?

- KB

[Karanbir Singh]

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.

ideas ?

- KB

[Karanbir Singh]

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.

ideas ?

- KB

[Karanbir Singh]

Post by Ned Slider
My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

the svn commit msgs are generated on the same machine, is it possible to
have mailman only accept emails that have a local origin ? Just changing
the from: will not work since thats the bit which is being forged in the
spam.

ideas ?

- KB

[Karanbir Singh]

Post by Karanbir Singh
Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

Because of the very nature of lists, perhaps greylisting and uribl might
be worth plumbing in, and.or some form of 'receive' ip BL.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.
I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).
the svn list has always had random forged from's spam.
- KB

My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

[Karanbir Singh]

Post by Karanbir Singh
Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

Because of the very nature of lists, perhaps greylisting and uribl might
be worth plumbing in, and.or some form of 'receive' ip BL.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.
I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).
the svn list has always had random forged from's spam.
- KB

My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

[Karanbir Singh]

Post by Karanbir Singh
Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

Because of the very nature of lists, perhaps greylisting and uribl might
be worth plumbing in, and.or some form of 'receive' ip BL.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.
I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).
the svn list has always had random forged from's spam.
- KB

My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

[Karanbir Singh]

Post by Karanbir Singh
Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

Because of the very nature of lists, perhaps greylisting and uribl might
be worth plumbing in, and.or some form of 'receive' ip BL.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.
I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).
the svn list has always had random forged from's spam.
- KB

My apologies Karanbir - it was the svn commit list that looks the main
culprit, not this [users] list.

[Karanbir Singh]

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).

the svn list has always had random forged from's spam.

- KB

[Karanbir Singh]

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).

the svn list has always had random forged from's spam.

- KB

[Karanbir Singh]

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).

the svn list has always had random forged from's spam.

- KB

[Karanbir Singh]

Post by Ned Slider
Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

Its considered bad practice to need sa on mailing lists, and I dont know
of any where it's used. And I dont think its ever been used for the rf
lists.

I dont seem to have hit any spam into my mailfolders, what do you see
where ? ( urls to the archieve would be good ).

the svn list has always had random forged from's spam.

- KB

[Ned Slider]

Post by Karanbir Singh

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

[Ned Slider]

Post by Karanbir Singh

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

[Ned Slider]

Post by Karanbir Singh

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

[Ned Slider]

Post by Karanbir Singh

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

Did something happen to the spam filtering too? Since it's come back
online we seem to be getting more than our fair share of spam, all of
which look trivial to filter. Did someone forget to kick start
SpamAssassin or something?

[Karanbir Singh]

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

speaking of which, it would be quite nice to get this under monitoring -
but apart from sending an email to the list every 6 hrs from different
places, whats a good way to test that the lists still work ?

At the moment, I've got an age check in /var/mailman/ - but that failed
to spot this problem, since the svn list was indeed getting traffic. So,
the monitoring would need to be per-list.

ideas anyone ?

[Karanbir Singh]

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

speaking of which, it would be quite nice to get this under monitoring -
but apart from sending an email to the list every 6 hrs from different
places, whats a good way to test that the lists still work ?

At the moment, I've got an age check in /var/mailman/ - but that failed
to spot this problem, since the svn list was indeed getting traffic. So,
the monitoring would need to be per-list.

ideas anyone ?

[Karanbir Singh]

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

speaking of which, it would be quite nice to get this under monitoring -
but apart from sending an email to the list every 6 hrs from different
places, whats a good way to test that the lists still work ?

At the moment, I've got an age check in /var/mailman/ - but that failed
to spot this problem, since the svn list was indeed getting traffic. So,
the monitoring would need to be per-list.

ideas anyone ?

[Karanbir Singh]

Post by Dag Wieers

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

thanks yes, the backup MX should have the last few days backlog so we
*should* not have lost any emails.

speaking of which, it would be quite nice to get this under monitoring -
but apart from sending an email to the list every 6 hrs from different
places, whats a good way to test that the lists still work ?

At the moment, I've got an age check in /var/mailman/ - but that failed
to spot this problem, since the svn list was indeed getting traffic. So,
the monitoring would need to be per-list.

ideas anyone ?

[David Hrbáč]

Just test. Please ignore.
David Hrb??

[Dag Wieers]

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

[David Hrbáč]

Just test. Please ignore.
David Hrb??

[Dag Wieers]

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

[David Hrbáč]

Just test. Please ignore.
David Hrb??

[Dag Wieers]

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)

[David Hrbáč]

Just test. Please ignore.
David Hrb??

[Dag Wieers]

Post by David Hrbáč
Just test. Please ignore.

It works now, thanks for reporting it privately so Karanbir could fix it
;-)