Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-18 by brian Snead
I am having trouble applying this patch to my sync.c file. I didn t have any trouble with the previous diff file you sent. Is there a different way this one
Messages
Browse messages
Page 140 of 144 · 7199 messages matched
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by manu@netbsd.org
... Yes, you are right. From the man page: s_port The port number at which the service resides. Port numbers must be given and are returned in network
milter-greylist 1.5.2
2004-06-17 by manu@netbsd.org
Hi Version 1.5.2 tries to fix the MX sync troubles on Solaris and Tru64 that Attila tracked down today. 1.5.2: Add a template Makefile to manually tweak if
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by Cyril Guibourg
... I believe the bug is in sync.c where the service number returned by getservbyname() is assigned using htons() which reverts the byte order.
RE: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by Brian Snead
I ran the program and got 0x3412. Brian. ... From: manu@netbsd.org [mailto:manu@netbsd.org] Sent: Thursday, June 17, 2004 4:10 PM To:
Re: [milter-greylist] inactive, but adding tuples to grelist.db
2004-06-17 by manu@netbsd.org
... Well, people usually don t notice, except if they are on the phone with the sender in a I send it (click), have you got it? mode. What they notice is
Re: [milter-greylist] Problem with a uunet relay server
2004-06-17 by manu@netbsd.org
... I wonder what software those uterly broken MTA run ... Yes. Generally speaking, you should add as much known addresses to the whitelist as you can. There
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by manu@netbsd.org
... It s a little endian problem: 5252 = 0x1484 33812 = 0x8414 Can you try the following test program? #include #include int main(argc,
RE: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by Brian Snead
Emmanuel, I think you are right about me stating the port wrong. However, I have never been able to get the mxsync to work if I have the following entry in my
RE: [milter-greylist] Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-17 by Boris Losev
... After diff appling Unexpected reply add from... doesnt appear in syslog: Jun 17 17:31:03 intra2 milter-greylist: [ID 829402 mail.info] Incoming MX
inactive, but adding tuples to grelist.db
2004-06-17 by Graham Dunn
Is it possible to run milter-greylist in a mode that is purely data collection, ie. logging the host, from:, rcpt tuples but not tempfailing any mail? I d use
RE: [milter-greylist] Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-17 by attila.bruncsak@itu.int
Hello, ... To summarize: 1. On V1.5.1 both Tru64 UNIX and Solaris 8 gives the error message: Unexpected reply add from ... This is probably due to the bug
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by Emmanuel Dreyfus
... xinetd has nothing to do here. You should just need it in /etc/services ... Is it really 33000? Not 33812? (33812 is 5252 in reverse-endian display) ...
Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-17 by Boris Losev
... 8? Look at this http://groups.yahoo.com/group/milter-greylist/message/230
Problem with a uunet relay server
2004-06-17 by Brian Snead
I was seeing an interesting chain events with two relay servers owned by uunet. My client was sending a message to 4 people in my office. The first uunet
RE: [milter-greylist] Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-17 by attila.bruncsak@itu.int
Hello, ... Now with V1.5.1 I get also the same problem: Unexpected reply add from peer... The fflush() just after the fgets() in the function sync_server
RE: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by Brian Snead
I am happy to report that the patch allowed me to find the problem and all is well now. However, this brings up two additional things I saw while
RE: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by attila.bruncsak@itu.int
Hello, ... I attach a patch that you can apply to the code. This surely not solve your problem but may give some hints where the problem might be. God knows
[milter-greylist] Request to make ADDRLEN configure option
2004-06-17 by attila.bruncsak@itu.int
Hello, Is it possible to make the ADDRLEN constant to be a configuration value instead of being fixed to 31 in the source code? So to conditionally define with
Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-17 by Boris Losev
... sync is ok (greylist.db on MXes are identical), but Unexpected reply add from... still appear in syslog: Jun 17 11:57:41 intra2 milter-greylist: [ID
Re: [milter-greylist] Sync operation failing with 'Unexpected rep ly "200" from peer ...'
2004-06-17 by manu@netbsd.org
... The fix is in 1.5.1, so everyone can test if it s okay. -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et
RE: [milter-greylist] Sync operation failing with 'Unexpected rep ly "200" from peer ...'
2004-06-17 by attila.bruncsak@itu.int
Hello, ... If there are two consecutive reads without write operation between them the fflush() is not needed by the documentation. To be on the safe side it
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by manu@netbsd.org
... And rebooting the machine changes nothing? -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et ceux qui ne
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-17 by brian Snead
... It is only the Redhat 8.0 system that fails with the cannot start MX sync error. All the other systems load fine. What is really strange is the error
Re: [milter-greylist] MX sync bind failed - Address in use
2004-06-16 by manu@netbsd.org
... When you say the third fails, it s always the same machine, or it s the last machine where you start milter-greylist? -- Emmanuel Dreyfus Il y a 10 sortes
MX sync bind failed - Address in use
2004-06-16 by Brian Snead
Hello, I have three MX servers and am trying to get mx sync to work between them. Two of the servers are syncing, but the third is logging the following error
Re: [milter-greylist] IANA registration?
2004-06-16 by manu@netbsd.org
... It s too late, the protocol is already there. -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et ceux qui
Re: [milter-greylist] IANA registration?
2004-06-16 by Dan Hollis
... I wonder if it s better to find existing protocol or port that can be used for mx syncing, than making a new one. -Dan
milter-greylist-1.5.1
2004-06-16 by manu@netbsd.org
milter-greylist-1.5.1 is available It should fix most of the problem reported. Please tell me what remains: 1.5.1: Fix mixed I/O in MX sync on Solaris, from
IANA registration?
2004-06-16 by manu@netbsd.org
Hi milter-greylist uses port 5252 for MX sync. I wonder if it makes sense to register that to the IANA. I ve never been into that, so I don t know if it s the
Re: [milter-greylist] Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-16 by manu@netbsd.org
... Try adding fflush() before the fgets() in sync.c -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et ceux
Re: [milter-greylist] Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-16 by manu@netbsd.org
... To sum up, we need to fflush after each time data is readen from the file descriptor, that s it? -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le
Re: [milter-greylist] Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-16 by Emmanuel Dreyfus
... I suspect this is the same problem at another place: the input buffer and output buffer get mixed. -- Emmanuel Dreyfus manu@netbsd.org
Re: Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-16 by Boris Losev
... It seems patch isn t working on Solaris 8. I ve applied patch, compilation was ok, but instead of Unexpected reply 200 from peer .. I ve seen
[milter-greylist] Sync operation failing with 'Unexpected reply " 200" from peer ...'
2004-06-16 by attila.bruncsak@itu.int
Hello, I was wondering why the MX sync was not working at all for me. I got always the error message in the syslog which is in the subject of this mail. Now I
Re: [milter-greylist] Spoke too soon
2004-06-16 by Graham Dunn
... That seems to have fixed it. Bind 9.2.3 needs to be configured with the --with-libbind argument in order to produce the correct libbind.a file to compile
[milter-greylist] Cleaning up rc-solaris.sh via the Makefile
2004-06-16 by attila.bruncsak@itu.int
Hello, You may want to patch the Makefile.in to be able to clean up the rc-solaris.sh on make clean . See attached diff output. Bests, Attila
Re: peer - reply 200
2004-06-16 by Boris Losev
... I ve the same problem on Solaris 8 (SunOS intra1 5.8 Generic_108528-11 sun4m sparc SUNW,SPARCstation-5) with milter-greylist-1.4.
Re: [milter-greylist] IP address binding
2004-06-15 by manu@netbsd.org
... What about a configuration file option? We already have too much command line options. I propose syncaddr, and while we are there, we can have a syncport
Re: [milter-greylist] IP address binding
2004-06-15 by Cyril Guibourg
... I started to play with it and got something working. At this time a [-i addr] cmd arg changes the default bind to INADD_ANY behaviour. I choosen to make
Re: [milter-greylist] IP address binding
2004-06-15 by manu@netbsd.org
... Yes, that s what I finnally understood. One more thing in the TODO list. -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui
Re: [milter-greylist] IP address binding
2004-06-15 by Dan Hollis
... Presumably he doesnt want it to bind to * for security or other reasons. -Dan
Re: [milter-greylist] Configure problem on Tru64 UNIX
2004-06-15 by Emmanuel Dreyfus
... Ues, I ll remove -Wall in the next release. It just breaks things. -- Emmanuel Dreyfus manu@netbsd.org
RE: [milter-greylist] Configure problem on Tru64 UNIX
2004-06-15 by attila.bruncsak@itu.int
Hello, Forcing the configure not to use -Wall option let it finish his task correctly. The compilation is working fine as well. I continue to put this version
Re: Re: [milter-greylist] IP address binding
2004-06-15 by Emmanuel Dreyfus
... It s not possible yet, though it is not a difficult feature to add. -- Emmanuel Dreyfus manu@netbsd.org
Re: Re: [milter-greylist] IP address binding
2004-06-15 by Boris Losev
I mean can milter-greylist use specific IP address for syncing on multiple MX configuration. Other words can milter-greylist listen port 5252 on specific IP
Re: [milter-greylist] IP address binding
2004-06-15 by Emmanuel Dreyfus
... What do you mean by binding to IP address ? -- Emmanuel Dreyfus manu@netbsd.org
IP address binding
2004-06-15 by Boris Losev
I d like to configure milter-greylist for binding to IP address. Can I do it?
Re: [milter-greylist] Little issue with conf parser
2004-06-15 by Cyril Guibourg
... This exactly what I meant when asking about patching the man page in my initial message ! ... +++ greylist.conf.5 Tue Jun 15 11:02:28 2004 @@ -40,8
Re: [milter-greylist] Little issue with conf parser
2004-06-15 by Emmanuel Dreyfus
... Easy fix: document that comments are only lines starting by a # -- Emmanuel Dreyfus manu@netbsd.org