Re: [milter-greylist] Invalid helo strings check support?.
2007-06-20 by manu@netbsd.org
... Yes, I added HELO filtering in milter-greylist for this kind of problems. But I don t call it fighting against spammers. What can be using HELO localhost,
Messages
Browse messages
Page 72 of 144 · 7199 messages matched
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-20 by Matthias Scheler
... But it works. I use milter-regex for this purpose and it rejected 831 SMTP connections (on a low traffic mail server) which used HELO localhost in the
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-20 by manu@netbsd.org
... You can t fight on the HELO string, as the spammer can send whatever he wants. HELO filtering is only going to help in dealing with very special situations
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-19 by Mart Pirita
Tere. ... But isn t it manually adjustable blacklist? And fighting manually against spammers seems mission impossible? ... Dnsbl also checks senders ip against
Re: [milter-greylist] Weak greylisting
2007-06-19 by Collin Baillie
... Probably something simple like; method normal|reverse and if fallback to subnetmatch was implemented in the event of reverse lookup failure, then that too
Re: [milter-greylist] Weak greylisting
2007-06-19 by manu@netbsd.org
... Well, I guess nobody opposes to the addition of fancy features. 4.0 alpha has become more a kind of swiss-knife anti-spam tool than just a greylist filter.
Re: [milter-greylist] Weak greylisting
2007-06-19 by Collin Baillie
... Ok, after more experience with milter-greylist, I can agree that subnetmatch would work like weak greylisting. However, weak greylisting (you may remember
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-15 by Fabien Tassin
Hi, any comment on that patch ? did anyone try it? /Fabien
Re: [milter-greylist] Which Version for Production?
2007-06-15 by manu@netbsd.org
... The first step in that direction is to create a clean API between the main logic and the database back-end. Once you access storage through a well defined
Re: [milter-greylist] Which Version for Production?
2007-06-15 by AIDA Shinra
At Thu, 14 Jun 2007 23:05:30 +0200, ... Berkeley DB 4.x can guarantee its consistency after system failures by journaling mechanism just as RDBMSes do. See:
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-15 by Fabien Tassin
damn yahoo. retry without the patch. http://www.sofaraway.org/tmp/milter-greylist/milter-greylist-4.0a6-configure.patch /Fabien === Date: Fri, 15 Jun 2007
Re: [milter-greylist] Which Version for Production?
2007-06-15 by Oliver Fromme
... That s why a transactional database should be used. It guarantees consistency, no matter if and when the client application crashes. Personally I would
Re: [milter-greylist] Which Version for Production?
2007-06-15 by Dan Mahoney, System Admin
... So then the solution is simple. Keep the same dumpfile we have now as an option. -Dan -- It s three o clock in the morning. It s too late for oops .
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-15 by manu@netbsd.org
... An example? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
Re: [milter-greylist] Which Version for Production?
2007-06-15 by manu@netbsd.org
... You are not: we dump in a new file and rename the new file into the old one. That means that unless your OS plays the dangerous game of flushing metadata
Re: [milter-greylist] Which Version for Production?
2007-06-14 by Dan Mahoney, System Admin
... How is this different from how a crash is handled now? We re at the mercy of the berkeley engine instead of being at the mercy of the dumpfile. If the
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-14 by Matt Kettler
... I find it rather funny that the above page has this statement in it: Reject the request when the hostname in the client HELO (EHLO) command is not in
Re: [milter-greylist] Which Version for Production?
2007-06-14 by manu@netbsd.org
... The problem was that it was impossible to be sure no corruption could occur on the DB file if milter-greylist crashed at a wrong time. -- Emmanuel Dreyfus
Re: [milter-greylist] Which Version for Production?
2007-06-14 by Dan Mahoney, System Admin
... (Sorry for the late, late reply, I ve been out of the loop in the hospital...nasty stuff) Okay, so would anyone be interested in some sort of bounty on
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-14 by manu@netbsd.org
... Well, let s hope that won t break everything... ... Go ahead. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-14 by Fabien Tassin
... Just had a look. Seems easy but current code is a little bit messy. Some tests are performed twice, and lib tests are spread everywhere. Would you accept a
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-14 by Fabien Tassin
... once I have time, yes. Unless someone beat me to it :) /Fabien
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-14 by manu@netbsd.org
... That seems a good solution. Are you going to work on that change? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
Re: [milter-greylist] milter-greylist 4.0 alpha6 is available
2007-06-14 by Fabien Tassin
... there s an issue with configure. I ve already faced it with libbind, that why I ve initially proposed the patch mentionned above, but it s a more general
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-13 by manu@netbsd.org
... In 4.0 beta: racl blacklist helo /domain .com/ msg go away! ... An example. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-13 by Mart Pirita
Tere. ... Hmm, didn t know, any example how to do it? ... Like dnsbl maybe? -- Mart
Re: [milter-greylist] Invalid helo strings check support?.
2007-06-13 by manu@netbsd.org
... My concern is always limitting the config file mess. We can already set an ACL clause on HELO against a substring or a regex. How do you imagine the syntax
Invalid helo strings check support?.
2007-06-08 by Mart Pirita
Tere. Postfix includes good helo check options (http://www.postfix.org/uce.html#smtpd_helo_restrictions): smtpd_helo_restrictions = reject_non_fqdn_hostname,
Re: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-06-08 by Federico Giannici
... In case it could be useful, I have restricted the range of time the bug has been introduced: the problem IS present in version 3.1.3 and IS NOT present in
RE: [milter-greylist] Delivery attempt every second or so
2007-06-07 by Brian W. Antoine
... this ... That looks like your typical maliciously clueless cable company. They ve decided that a Temp Failure means they should hammer your server into
Delivery attempt every second or so
2007-06-07 by Alan Clifford
Below is the log which I happened to be watching with a tail -f. Is this an anti-greylisting strategy? It continued for the full 5 minutes that I have
milter-greylist 4.0 alpha6 is available
2007-06-04 by manu@netbsd.org
Here is our alpha6 ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-4.0a6.tgz MD5 (milter-greylist-4.0a6.tgz) = fb469a3947a6821519a62644a412827 Changes
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-06-04 by attila.bruncsak@itu.int
... I have applied the patch, and there is no problem for the time being. Bests, Attila
Re: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-31 by Emmanuel Dreyfus
... You rock! :-) ... What about this fix? Index: milter-greylist.c =================================================================== RCS file:
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-31 by attila.bruncsak@itu.int
... So here we are: May 30 19:14:34 mail1 sendmail[217629]: l4UHCKir217629: from= , size=10000, class=0, nrcpts=1, msgid= , proto=ESMTP,
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-30 by attila.bruncsak@itu.int
... Hello, The attached patch may give a bit more of information about the session in which the error may occur. Bests, Attila
RE: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-28 by attila.bruncsak@itu.int
... Sure, you can do this way too... The main point is to have notification about the re-lunch of milter-greylist, since it is a major event which should not
Re: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-27 by Emmanuel Dreyfus
... This has the advantage that you can even run it within gdb and collect a backtrace after a crash... -- Emmanuel Dreyfus manu@netbsd.org
Re: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-27 by Joel Reicher
... Why do something so complex? You could instead run milter-greylist in the foreground inside an infinite loop, putting whatever else you like in the loop
Re: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-25 by manu@netbsd.org
... You can run the milter within gdb, with the -D flag. When it crashes, issue the bt command to get a backtrace. It may help. Indeed 4.0 alpha series have a
RE: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-25 by attila.bruncsak@itu.int
... Hello, I strongly recommend to everybody to include notification in case of automatic re-lunch of milter-greylist. Here is my
Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-25 by Federico Giannici
A few weeks ago I sent here a couple emails saying that since I upgraded from version 3.1.1 to 4.0a1 I noticed that from time to time a lot of error messages
Re: [milter-greylist] [PATCH] A trivial fix
2007-05-20 by manu@netbsd.org
... Got it, thanks! -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
[PATCH] A trivial fix
2007-05-20 by AIDA Shinra
Trivial bugfix: Index: acl.c =================================================================== RCS file: /milter-greylist/milter-greylist/acl.c,v retrieving
Re: [milter-greylist] memory leak or normal behaviour?
2007-05-17 by Michael Fromme
... By observation : found one memory leak by strict definition, and found a steady increase of virtual memory size. I d expect asymtotic memory usage of a
Re: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-16 by manu@netbsd.org
... /var/milter-greylist/runningsize.log ... I guess someone could incrementally try each developement snapshot to between 3.0 and 4.0 alpha to see when things
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-15 by attila.bruncsak@itu.int
... At my side the version 3.0 was running fine in production for 5 months without restarting. There is no sign of any significant memory leek. If you wish I
Re: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-15 by Emmanuel Dreyfus
... I couldn t say if I have it, as my milter is restarted every 24 hours by a crontab. A safety net that should not exist for a beta, but was actually very
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-15 by attila.bruncsak@itu.int
... One more information: I have the same problem both on Tru64 UNIX and on SuSe LINUX, so I do not think that the problem is platform specific. I have
Re: [milter-greylist] Using SPF in ACL
2007-05-14 by manu@netbsd.org
LE BOURDOULOUS Alain DSIC BEERTD CGN Messagerie ... Yes, this has been discussed before: filtering on SPF should be improved, probably this way: spf pass