Re: [milter-greylist] invalid IPv6 address
2004-10-12 by manu@netbsd.org
... Sounds fine. Did you tested it? Does it works as intented? If it does I ll check in the fix and release 1.5.9 -- Emmanuel Dreyfus Il y a 10 sortes de
Messages
Browse messages
Page 134 of 144 · 7199 messages matched
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by Cyril Guibourg
Hello Hajimu, ... Which is right. Imho, we could consider getting dump_lex.l less pointy head so that such line would be safely ignored at startup. Another
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Matthias Scheler
... My fault. I remebered incorrectly that you have to clear these fields for arguments to socket related system calls. But they are of cause allowed to be
RE: Volume
2004-10-12 by Sutherland, James
Well I ve got it installed and it s running. I m worried the db file may grow to large to be sustained. We ll see Stats so far. Unique triplets in the first
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by Hajimu UMEMOTO
Hi, ... scotto5 This email address seems doesn t match the rule of `email . `: is not allowed in `atext . Following rule
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by Hajimu UMEMOTO
Hi, ... manu How can we acheive that? Any lex expert in the room? :) How about this patch? Though it is not a way above, it should match with only exact an
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by Hajimu UMEMOTO
Hi, ... manu How can we acheive that? Any lex expert in the room? :) Sorry but I have no idea for now. I m not a lex expert. Sincerely, -- Hajimu UMEMOTO @
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by manu@netbsd.org
... How can we acheive that? Any lex expert in the room? :) -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et
Re: [milter-greylist] Compile problem on Tru64 UNIX
2004-10-12 by manu@netbsd.org
... [sample code] Good. Can you make the patch for configure.ac? I could do it but I won t be able to test. -- Emmanuel Dreyfus Il y a 10 sortes de personnes
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by manu@netbsd.org
... I just copied Mathias sample code. I ll remove these allocations. -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by manu@netbsd.org
... Mmmm... Hajimu Umemoto made IPv6 integration, he might have an idea: why is this e-mail address seen as an IPv6 address by the lexer? Until we find a real
Re: [milter-greylist] invalid IPv6 address
2004-10-12 by Hajimu UMEMOTO
Hi, ... scotto5 64.106.137.140 scotto5 1097598374 # 2004-10-12 scotto5 09:26:14 scotto5
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Hajimu UMEMOTO
Hi, ... manu Could you test the following patch? manu ftp://ftp.espci.fr/shadow/manu/local.patch + case AF_INET6: + len = sizeof(sin6); + memcpy(&sin6, sa,
invalid IPv6 address
2004-10-12 by scoost
Running 1.5.8 on Redhat ELES 3.0 Twice now I have gotten a line in the cache file that does not allow milter-greylist to restart. The line follows: (watch
Re: [milter-greylist] Volume
2004-10-12 by Emmanuel Dreyfus
... There are two scallability problems in milter-greylist 1) RAM usage. But if you have a big mail server you can afford to buy more memory 2) time to dump
Volume
2004-10-12 by Sutherland, James
Anyone have experience with milter-greylist on a high volume server? By high volume I mean 250k incoming mail connections per day? I ve had some problems in
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Emmanuel Dreyfus
... Latest: 1.5.8 ... I m not sure we can do that: libmilter documentation explicitely says it takes care of all signals. Catching the signal may break the
Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Klas Heggemann
... To which release is this? We run 1.5.3 and it does not seem to apply to this version. ... In order to get the database saved when the process gets killed,
Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Emmanuel Dreyfus
... (snip) ... Could you test the following patch? ftp://ftp.espci.fr/shadow/manu/local.patch It should mark a local peer as such and avoind sending sync
RE: [milter-greylist] Compile problem on Tru64 UNIX
2004-10-12 by attila.bruncsak@itu.int
... Here it is: $ cat tst.c #include #include main() { #ifdef AF_INET6 struct in6_addr s; #endif } $ cc -D_XOPEN_SOURCE=500
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Emmanuel Dreyfus
... Ok, I thought you meant to replace the sync mecanism by something based on UDP. I ll implement what you suggest. -- Emmanuel Dreyfus manu@netbsd.org
Re: [milter-greylist] Compile problem on Tru64 UNIX
2004-10-12 by Emmanuel Dreyfus
... [That s tricky] What about tryig to use an IPv6 related structure with and without OSF_SOURCE? If the result is (fail, suceed), that means we need to add
RE: [milter-greylist] Compile problem on Tru64 UNIX
2004-10-12 by attila.bruncsak@itu.int
... In Tru64 UNIX version 4.x there is no native IPV6 support (maybe with special kits installed only). Anyhow, I never succeeded to compile it on Tru64 UNIX
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Matthias Scheler
... Registering functions via atexit() is pointless in that case. ... How does libmilter handle SIGTERM? I would be surprised if it doesn t call exit(3C). Kind
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Matthias Scheler
... Why? I don t say you should use the UDP socket except for checking if you can bind to the IP address of a specific peer which means it is a local address.
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by manu@netbsd.org
... But that kills backward compatibility. We could also check that the address is non local. Is there a way of doing that? -- Emmanuel Dreyfus Il y a 10
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by manu@netbsd.org
... That s bad since we will never call exit() ... It cannot. libmilter takes care of the signals, there is no way of catching them from a milter. -- Emmanuel
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Matthias Scheler
... An easy and portable way to implement that feature would be trying to bind a UDP socket to the address of every peer (requesting an arbitrary port). If
Re: [milter-greylist] Re: syncing autowhitelisted entries between mx-hosts
2004-10-12 by Matthias Scheler
... No. But function registered that way will of cause only be called if the program return from main() or exists via exit(3C). Being killed by signal won t do
Re: syncing autowhitelisted entries between mx-hosts
2004-10-11 by manu@netbsd.org
... It s done through atexit(). Is there some known oddities with atexit() on Solaris? -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux
Re: [milter-greylist] Compile problem on Tru64 UNIX
2004-10-11 by manu@netbsd.org
... Could you write a configure test that check that macro? The work is easy, as we already have similar tests (for instance about -D__EXTENSIONS__) (namespace
Re: [milter-greylist] Re: Make Error: conf_lex.c
2004-10-11 by Emmanuel Dreyfus
... I suspect you forgot to run configure -- Emmanuel Dreyfus manu@netbsd.org
Re: Make Error: conf_lex.c
2004-10-11 by martinmcwhorter
... I am not sure what I did, but I must have done something wrong. I rm -fr the greylist-1.4 dir and retared (yeah I know) xvfz it. Make worked fine this
Re: [milter-greylist] Re: Make Error: conf_lex.c
2004-10-11 by Emmanuel Dreyfus
... What do you have in the makefile about lex? How LEX is defined? Does make clean && make conf_lex.l do something? -- Emmanuel Dreyfus manu@netbsd.org
Re: Make Error: conf_lex.c
2004-10-11 by martinmcwhorter
... No other error. ... Lex does not fail, but make failed after that with: dump_yacc.y:44:22: dump_lex.c: No such file or directory make: *** [dump_yacc.o]
Re: [milter-greylist] Make Error: conf_lex.c
2004-10-11 by Emmanuel Dreyfus
... It is generated using lex (or flex) from conf_lex.l Do you have another error before about this operation? lex conf_lex.l should give you a lex.yy.c rename
Make Error: conf_lex.c
2004-10-11 by martinmcwhorter
I am trying to make milter-greylist 1.4 from source on a redhat 9.0 linux machine. The error I get is: conf_yacc.y:148:22: conf_lex.c: No such file or
Re: syncing autowhitelisted entries between mx-hosts
2004-10-11 by Klas Heggemann
... I think a lot of this is legitimate letters (to our approx 15000 users ...) I myself receive very little spam after the greylisting was implemented. People
[milter-greylist] Compile problem on Tru64 UNIX
2004-10-11 by attila.bruncsak@itu.int
Hello, I took time now to try to go higher version from 1.5.3 with my patch up to version 1.5.8. The 1.5.4 already includes the IPV6 support. To have the IPV6
Re: syncing autowhitelisted entries between mx-hosts
2004-10-11 by Emmanuel Dreyfus
... After you starte greylisting, you usually still get a lot of spam sent from regular mail servers. Removal requests and/or blacklisting cures it. ... True.
Re: [milter-greylist] [SPF] libspf_alt vs libspf2
2004-10-06 by Alexandre CHERIF
Re, yep that s true, i will send a new patch for libspf2 and new api this week Regards
Re: [milter-greylist] [SPF] libspf_alt vs libspf2
2004-10-06 by manu@netbsd.org
... With libspf2-1.2.0, it seems SPF_create_config does not exist anymore. If that s the case, you ll probably have to check libspf2 version to ensure the
pending patches
2004-10-06 by manu@netbsd.org
Hello I m back on broadband, and I ll try to handle the pending patches this week. I have Alexandre Cherif s line 273 of milter-greylist.c: inet_ntop(AF_INET,
Re: [milter-greylist] RFC: New config syntax proposal
2004-10-01 by Emmanuel Dreyfus
... That s wrong. Because an ACL has to match all rules to get selected, my setup would be: acl user1 { rcpt user1@atmine.com } acl user2 ( rcpt
RFC: New config syntax proposal
2004-09-30 by manu@netbsd.org
... Good, I hate re-inventing the wheel. (snip) ... You don t *have* to use the complex features, but it s good to have them available: So we d have a first
Re: [milter-greylist] Patch to milter-greylist - adds norcpt keyword
2004-09-30 by Graham Dunn
... Squid has already invented this particular wheel, yes? from squid.conf (with changes)... # TAG: acl # Defining an Access List # # acl aclname
Re: [milter-greylist] Patch to milter-greylist - adds norcpt keyword
2004-09-30 by Cyril Guibourg
... What about fromto: ?
Re: [milter-greylist] Patch to milter-greylist - adds norcpt keyword
2004-09-30 by Emmanuel Dreyfus
... That does not address the need Dan has, does it? He wants to greylist specific sender/reciever pairs. -- Emmanuel Dreyfus manu@netbsd.org
Re: [milter-greylist] Patch to milter-greylist - adds norcpt keyword
2004-09-30 by Cyril Guibourg
... what about something like: #general parameters timeout 4d quiet some-recipien-domain.com { addr X.Y.Z.T rcpt john.doe from friend@yahoo.com domain
Re: [milter-greylist] Patch to milter-greylist - adds norcpt keyword
2004-09-30 by Emmanuel Dreyfus
... The feature is nice and desirable but I have concerns with the syntax. rcpt means recipient, it sounds weird to add the sender. What about introducing a