On 12/2/2012 1:20 PM, Alex wrote:
> Thanks for the explanation. Trying to do too many things at once. You
> probably think I'm an idiot by now.
You're welcome. I understand that completely. No, not at all.
>> Dropping SMTP packets should be done with care. If you FP on an email
>> to the CEO
Hi,
>>> Again, the IP in question will never be listed in the PBL. SBL maybe,
>>> PBL no. Might be time to brush up on Spamhaus various lists and their
>>> criteria.
>>
>> Yes, I didn't fully understand that dynamics aren't listed in the PBL.
...
> The SBL is where you'll find snowshoe IPs liste
On 11/27/2012 2:51 PM, Alex wrote:
> Stan,
>
>>> Right, that makes sense. A spammer wouldn't have access to a
>>> consecutive block of dynamic IPs, like from a cable company or
>>> Verizon. It still could mean that it's listed in the PBL by now,
>>> though.
>>
>> Again, the IP in question will nev
Stan,
>> Right, that makes sense. A spammer wouldn't have access to a
>> consecutive block of dynamic IPs, like from a cable company or
>> Verizon. It still could mean that it's listed in the PBL by now,
>> though.
>
> Again, the IP in question will never be listed in the PBL. SBL maybe,
> PBL no
On 11/22/2012 12:39 PM, Alex wrote:
> Hi,
>
>>> I'm sure by now it's in the PBL or SBL.
>>
>> This is a bad assumption. The PBL lists dynamics/etc, not snowshoe IPs.
>
> Right, that makes sense. A spammer wouldn't have access to a
> consecutive block of dynamic IPs, like from a cable company or
Hi,
>> I'm sure by now it's in the PBL or SBL.
>
> This is a bad assumption. The PBL lists dynamics/etc, not snowshoe IPs.
Right, that makes sense. A spammer wouldn't have access to a
consecutive block of dynamic IPs, like from a cable company or
Verizon. It still could mean that it's listed in
On 11/22/2012 2:24 AM, Jamie Paul Griffin wrote:
> Hi Stan, can I ask: what is a "Snowshoe" domain?
It's a domain that wears these:
http://blog.mlive.com/outdoors_impact/2009/03/large_1snowshoe07.jpg
--
Stan
On Thu, Nov 22, 2012 at 08:24:16AM +, Jamie Paul Griffin wrote:
> Hi Stan, can I ask: what is a "Snowshoe" domain?
http://blog.wordtothewise.com/2009/10/spamhaus-vs-snowshoe-spammers/
--
Michael P. Demelbauer
Systemadministration
WSR
Arsenal, Objekt 20
1030 Wien
--
[ Stan Hoeppner Wrote On Thu 22.Nov'12 at 8:19:21 GMT ]
> On 11/21/2012 7:01 PM, Alex wrote:
>
> > I pulled the IPs out of the logs for these 'lost connection' errors
> > over the last 24hrs, and it does appear that there are multiple IPs in
> > the same network losing the connection. This also
On 11/21/2012 7:01 PM, Alex wrote:
> I pulled the IPs out of the logs for these 'lost connection' errors
> over the last 24hrs, and it does appear that there are multiple IPs in
> the same network losing the connection. This also doesn't really prove
> much, but there are cases where there are doz
Alex:
> Nov 21 19:39:14 mail01 postfix/postscreen[9111]: PASS OLD
> [198.41.120.10]:47864
>
> They were later all tagged as spam, but it would definitely be nice to
> be blocking these outright with postscreen. I've now added an iptables
Postscreen "forgets" DNSBL lookup results after one hour.
Hi,
>>> Nov 19 20:39:03 mail01 postfix/smtpd[19820]: lost connection after
>>> CONNECT from listserver.translateplanmulti.info[198.41.120.7]
>>
>> Your server is too slow, so that connections pile up in front of
>> it.
>
> translateplanmulti.info is a snowshoe domain, 198.41.120.0/24, and
> everyo
On 11/20/2012 6:06 AM, Wietse Venema wrote:
> Alex:
>> Nov 19 20:39:03 mail01 postfix/smtpd[19820]: lost connection after
>> CONNECT from listserver.translateplanmulti.info[198.41.120.7]
>
> Your server is too slow, so that connections pile up in front of
> it.
translateplanmulti.info is a snows
Alex:
> Nov 19 20:39:03 mail01 postfix/smtpd[19820]: lost connection after
> CONNECT from listserver.translateplanmulti.info[198.41.120.7]
Your server is too slow, so that connections pile up in front of
it.
Find out where the bottle neck is by SYSTEMATICALLY MEASURING latency
(not: manual "teln
Hi,
I have a postfix-2.8.10 server on fc15 that is having a problem with
slow connections to port 25 before receiving the initial 220 greeting.
I actually had a similar problem back in February on this same system,
and implementing postscreen seemed to have resolved it.
If I run "telnet localhost
15 matches
Mail list logo
