Re: [Sqlgrey-users] early reconnect issue

[Robert S. <ro...@sc...>]

Am 07.12.2011 09:31, schrieb Kevin Wincott:
> thank you for the suggestions, the problem is that these are legitimate
> connections, one thats causing an issue is a certain Yorkshire based ISP
> in the UK. They only way we have of knowing there is an issue is when
> some raises a support ticket to say they havent received an email

thats not unusual
as i said ,if this is legitim mail, and they penetrate your mailserver ,
problem must dealed at the source first
ask them to slow down their deliver rate to you, at last
dont let them running into greylist if you allready know that they are
legitim mail

> 
> 
> On 06/12/11 19:18, Robert Schetterer wrote:
>> Am 06.12.2011 17:44, schrieb Lionel Bouton:
>>> Le 06/12/2011 12:29, Kevin Wincott a écrit :
>>>> we currently run sqlgrey across a number of mail cluster servers, what
>>>> we are seeing on some occasions are servers reconnecting many times in
>>>> the space of a few seconds, then giving up. has anyone come across this
>>>> before and how did you get round it?
>> look at your logs, are these bots, where do they come from ?
>> there are bots simply dont care about greylist or any other smtp
>> feature, they simple fire
>>
>> if using postfix ,use postscreen, anyway you dont need to greylist all
>> in general, do it only for reverse dns ips looking like dyn ips
>> these means selective, you wont see much more spam passing by this way
>> and fast legal clients
>>
>> anotherway is fail2ban, and/or iptables recent
>>
>> for extrem fast bots i use iptables recent from rsyslog pipe and a shell
>> script, i had 5 smtp cons per second in max
>> which leads to 0,25 million bot ips during a half day on one server
>> mostly from india and brasil
>>
>>> This isn't standard compliant behaviour (to workaround temporary
>>> glitches, mail delivery should be retried for 5 days IIRC).
>>>
>>> Anyway, there are provisions to support this kind of behaviour in
>>> SQLgrey. Most of the time this doesn't require any tuning, but if
>>> SQLgrey doesn't manage to recognize these servers, you can whitelist
>>> them: see the distributed whitelists for examples.
>>> Don't touch the distributedd whitelists (they are overwritten when
>>> updating SQLgrey) but place your whitelist entries in the corresponding
>>> *.local files, SQLgrey loads their content on the fly (no need to restart).
>>>
>>> You should report the servers with such problem here and the whitelist
>>> entry you used to workaround your problem : if several people report the
>>> same problem, I'll add the whitelist entries to the ones distributed.
>>>
>>> Best regards,
>>>
>>> Lionel
>>>
>>> ------------------------------------------------------------------------------
>>> Cloud Services Checklist: Pricing and Packaging Optimization
>>> This white paper is intended to serve as a reference, checklist and point of 
>>> discussion for anyone considering optimizing the pricing and packaging model 
>>> of a cloud services business. Read Now!
>>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>>>
> Kind regards,
> 
> Kevin Wincott (ISP Administrator) CCENT, CCNA
> 
> This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of Midland Computers Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please contact the sender.
> 
> Please note: Prices are based upon the prices given at the quotation stage and are valid for 7 days. All prices exclude VAT, delivery and installation unless stated otherwise. Quotes are accepted in accordance with our Terms and Conditions which are available upon request. Any 3rd Party hardware and software we supply (i.e. Microsoft, HP etc) is in good faith, if for any reason faults or bugs are found we cannot be held responsible. Goods under warranty will be replaced by the manufacturer, however data transfer, re-loading of software, configuration etc. is chargeable. Any dispute/warranty is direct with the manufacturer, not Midland Computers unless warranty states otherwise. E&OE.
> 
> _______________________________________________
>>> Sqlgrey-users mailing list
>>> Sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>>
> 
> 
> ------------------------------------------------------------------------------
> Cloud Services Checklist: Pricing and Packaging Optimization
> This white paper is intended to serve as a reference, checklist and point of 
> discussion for anyone considering optimizing the pricing and packaging model 
> of a cloud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users


-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria