On Thu, 25 Jun 2009, Arvid Picciani wrote:
I still welcome suggestions for handling the few remaining cases where my
procmail chokes on a mailbox limit. Probably more of a PM question than an
SA question, but seeing how the cause for concern is backscatter from
'full mailbox' DSN's I'm
Is anybody else getting bounces on mail they send to the list from
cas...@snigelpost.org?
If so, can we get him unsubscribed?
--
John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 --
John Hardin wrote:
Is anybody else getting bounces on mail they send to the list from
cas...@snigelpost.org?
Yep. I wish backscatter.org had a reporting and educating form. Ie
automaticaly inform the postmaster of that system of the listing
incuding educational material how to fix it.
On Thu, June 25, 2009 19:09, John Hardin wrote:
Is anybody else getting bounces on mail they send to the list from
cas...@snigelpost.org?
If so, can we get him unsubscribed?
here i have seen 25 of this bouncers, i have added his sender ip into postfwd
client_address until its resolved, i
On Thu, 2009-06-25 at 10:09 -0700, John Hardin wrote:
Is anybody else getting bounces on mail they send to the list from
cas...@snigelpost.org?
Taking care of that, already poked the almighty admins.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char
On Thu, 25 Jun 2009, Benny Pedersen wrote:
On Thu, June 25, 2009 19:09, John Hardin wrote:
Is anybody else getting bounces on mail they send to the list from
cas...@snigelpost.org?
If so, can we get him unsubscribed?
here i have seen 25 of this bouncers, i have added his sender ip into
On Thu, June 25, 2009 19:34, John Hardin wrote:
Sure, but that doesn't help anybody else that posts to the list.
it will if admins at remote read there logs, but yes we can only wait now
--
xpoint
On Thu, 2009-06-25 at 19:32 +0200, Karsten Bräckelmann wrote:
Taking care of that, already poked the almighty admins.
FYI, they took care about this issue. Quite speedy. :)
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char
On Thu, June 25, 2009 19:48, Karsten Bräckelmann wrote:
On Thu, 2009-06-25 at 19:32 +0200, Karsten Bräckelmann wrote:
Taking care of that, already poked the almighty admins.
FYI, they took care about this issue. Quite speedy. :)
so now thay using postfix ?, fixing valid recipient maps is
FYI, they took care about this issue. Quite speedy. :)
so now thay using postfix ?, fixing valid recipient maps is dangerous :)
What are you talking about, Benny? The ASF admins have removed the
offending address from the list's subscribers.
Anyway, this horse is now dead. Please stop
On Thu, 25 Jun 2009, Arvid Picciani wrote:
I started blocking some backscattering hosts and would like to inform
them how to fix the issue.
I still welcome suggestions for handling the few remaining cases where my
procmail chokes on a mailbox limit. Probably more of a PM question than an
SA
On Thu, 25 Jun 2009, Benny Pedersen wrote:
On Thu, June 25, 2009 19:34, John Hardin wrote:
Sure, but that doesn't help anybody else that posts to the list.
it will if admins at remote read there logs, but yes we can only wait now
If they do, they don't act very quickly. I've been rejecting
Charles Gregory wrote:
On Thu, 25 Jun 2009, Arvid Picciani wrote:
I started blocking some backscattering hosts and would like to inform
them how to fix the issue.
I still welcome suggestions for handling the few remaining cases where
my procmail chokes on a mailbox limit. Probably more of a
13 matches
Mail list logo
