Yahoo Groups archive
Messages
Page 30 of 144 · 7199 messages matched
2011-02-24 by Oliver Fromme
... How would that change if the recipient check comes first? The recipient check doesn t change the IP/sender/recipient tuple, so greylisting would work just
2011-02-24 by Steger Wolfgang
... [mailto:milter-greylist@yahoogroups.com] On Behalf Of Les Mikesell ... users? ... Ok., it s a week since you asked, but here are some ideas about the way
2011-02-22 by Johann Klasek
... No other entries referencing p1IFvfPf026150 do exist? Strange ... What does it look like if milter-greylist is *not* active? Is something like Feb 18
2011-02-18 by Les Mikesell
... If I have acl greylist default .... set, I get entries like: Feb 18 09:57:43 mailmx milter-greylist: p1IFvfPf026150: addr [118.96.199.46][118.96.199.46]
2011-02-18 by Johann Klasek
... What does this look like in maillog? ... As far as I understand sendmail internal processing including milter callbacks this is not true at least in my
2011-02-18 by attila.bruncsak@itu.int
... with ... exist. ... config, ... I am using the FEATURE(`access_db ) in the sendmail configuration file. All the e-mails are rejected per default in the
2011-02-18 by manu@netbsd.org
... milter-greylist runs before sendmail checks the address is valid. I do not think you can change that. ... I solve this problem by having milter-greylist
2011-02-17 by Les Mikesell
I am running sendmail/MimeDefang and recently added milter-greylist as an additional spam check. The domains in question are regularly hit with
2011-02-02 by Greg Troxel
... You really need to post far more details of what you are doing. For example, your milter-greylist config, which presumably you ve tried to make minimal to
2011-02-02 by Delahunty, Mark
Hi I run sendmail with milter-greylist and a second milter, mimedefang. When I send an email to an unknown local recipient, sendmail is rejecting it before
2011-01-31 by Kouhei Sutou
Hi, In Re: [milter-greylist] Re: p0f + postfix on Mon, 31 Jan 2011 09:22:37 +0100, ... I agree. Thanks, -- kou
2011-01-31 by Francois Tigeot
... I have good news: since upgrading the system, milter-greylist has stopped crashing and has now been running for more than a hour without any bad
2011-01-31 by manu@netbsd.org
... As I understand, fixing the thing id therefore beyond what we can do in milter-greylist. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
2011-01-31 by Kouhei Sutou
Hi, Here is another workaround. :) In [milter-greylist] Re: p0f + postfix on Sun, 30 Jan 2011 19:22:05 -0000, ... {client_addr}
2011-01-30 by Francois Tigeot
... I think I won t need to: I ve reported the pthread issue with your test program to the kernel list. Matt Dillon has found the bug and has just commited a
2011-01-30 by Francois Tigeot
... DragonFly 2.6 give the same answers as most other systems: parent (672727152) TSS key 0x0 set to 0xbfbffbc8 parent (672727152) TSS key 0x0 read as
2011-01-30 by gitoshi
here the workaround Some Milter applications use the {if_addr} macro to recognize local mail; this macro does not exist in Postfix. Workaround: use the
2011-01-30 by manu@netbsd.org
... (...) ... Now you have to find, by adding mg_log everywhere, the location where conf_release is called wile GET_CONF or conf_retain has not. Adding this
2011-01-30 by Francois Tigeot
... I have cleaned-up some of the mg_log() calls and added your last patches. milter-greylist now crashes in a different way: Jan 30 16:56:16 milter-greylist:
2011-01-30 by Francois Tigeot
... Damn. Doesn t surprise me :-( ... I ll try to setup a test system soon. -- Francois Tigeot
2011-01-30 by manu@netbsd.org
Here is a bug workaround attempt. The patch is against latest sources but I tested it with success on latest 4.2.x. I think it should be ifdef only for
2011-01-30 by manu@netbsd.org
... It seems to be a real bug in DragonflyBSD, here is whar the standard says: Upon thread creation, the value NULL shall be associated with all defined keys
2011-01-30 by John Espiro
I apologize for the offtopic message... In conjunction with milter-greylist, I have been using milter-regex (http://www.benzedrine.cx/milter-regex.html).
2011-01-30 by John Espiro
OK - I had migrated from a RHEL machine to Ubuntu, and it seems that the default locations for things have changed. I used the guides on the website to make
2011-01-30 by manu@netbsd.org
... Ok, I think we tracked down the problem. I am not a POSIX.1 expert, but I suspect this is a pthread bug. This TSS has not been set in the child, so reading
2011-01-30 by Francois Tigeot
... Done. /var/log/maillog log extract: Jan 30 11:23:33 milter-greylist: 673054832: calling dumper_start() from main, line 1711 Jan 30 11:23:33
2011-01-30 by manu@netbsd.org
... But there is a mystery here: we do not see two conf_retain() calls. I suggest you log pthread_self() on conf_retain() entering. I wonder if the problem
2011-01-30 by Francois Tigeot
... That s right. ... I get some messages when I start milter-greylist: 673054832: calling dumper_start() from main, line 1711 673054832: calling dumper() from
2011-01-30 by manu@netbsd.org
... The first call, on top of dumper(), right? This means we launch two dumper threads, which is a good reason for getting into troubled. Can you add debug
2011-01-29 by Francois Tigeot
... I guess it s on line 133: Jan 29 20:45:53 milter-greylist: 673055056: conf_retain called from dumper, line 133 Jan 29 20:45:53 milter-greylist: conf.c:351
2011-01-29 by manu@netbsd.org
... Are you sure this not done by a start up script? How do you launch milter-greylist? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
2011-01-29 by John Espiro
When milter-greylist crashes or my system isw rebooted, the db folder and it s contents are deleted. 1.) Is this a permission issue? 2.) What ownership/perms
2011-01-29 by manu@netbsd.org
... Great, we now have our culprit. Unfortunately there are two calls to conf_retain() in dumper(), therefore you need to alter the debug statement to include
2011-01-29 by Francois Tigeot
... I had to use LOG_WARNING but otherwise there was no particular issue with the added lines. ... It seems to always be the same thread indeed. [With the
2011-01-29 by manu@netbsd.org
... No idea, I have not looked at the code at all. But indeed this is the right way, we just need someone to do it. -- Emmanuel Dreyfus
2011-01-29 by Greg Troxel
... I have run into this as well. How hard is it to patch postfix? I would think postfix people would look upon this reasonably, and we could certainly put
2011-01-29 by manu@netbsd.org
... And while you are there, logging the thread ID will help: if (GET_CONF()) mg_log(LOG_WARN, %d: conf_retain called from %s , pthread_self(), __func__); As
2011-01-29 by manu@netbsd.org
... I would assume that select() is above any suspicion, otherwise most of your program would crash. But if milter-greylist memory becomes corrupted, you can
2011-01-29 by Francois Tigeot
... Do you think this sort of crash may be consistent with a bug in select() ? ... I already did since you asked a few days ago. My experiments were all done
2011-01-29 by manu@netbsd.org
... That suggests things are quire rotten, and that ignoring the assertion in conf_retain() was not the right approach. Can you try replacing it by a return? I
2011-01-29 by manu@netbsd.org
... Not yet, but that seems easy to fix. The p0f interface require the local interface IP address. Sendmail makes it available through the {if_addr} macro, and
2011-01-29 by gitoshi
running CentOS 5.5 + postfix 2.3 using the follow line in my config racl greylist default delay 4m addheader X-Greylist-OS: %Fx however I get the follow
2011-01-27 by Francois Tigeot
... This is what I got: Program received signal SIGSEGV, Segmentation fault. 0x281342ff in select () from /usr/lib/libc.so.7 (gdb) bt #0 0x281342ff in select
2011-01-27 by manu@netbsd.org
... Make sure you built with -g, and run inside gdb: # gdb milter-greylist (gdb) r -Dv -p /var/milter-greylist/milter-greylist.sock Once you crash, type bt to
2011-01-26 by Francois Tigeot
... That was on a single test machine (the MX for wolfpond.org). I have now upgraded a second server to DragonFly-2.8 and applied this same modification to
2011-01-24 by manu@netbsd.org
... Ok it works. I don t know what happened last time, perhaps I used a wrong file. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
2011-01-23 by Joe Pruett
it was definitely done against the 4.2.6 tarball and i was just able to apply the patch with no hassles. and i just looked at the development tarball and it
2011-01-23 by Francois Tigeot
... There s no error message, it works fine: Jan 23 15:39:32 pizza milter-greylist: reloading config file /etc/mail/greylist.conf Jan 23 15:39:32 pizza
2011-01-23 by manu@netbsd.org
... And you only get it on startup, right? What happens on config reload? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@netbsd.org
2011-01-23 by Francois Tigeot
... Done: - assert(0); + return; Apart from the conf_retain error message, milter-greylist started fine and is now running normally. -- Francois