[xmail] Re: GLST.EXE taking 100% CPU
On Fri, 21 Apr 2006, Michal A. Valasek wrote: | Likely the machine shut down incorrectly (aka bad crash). At least one of those three machines was NEVER shut down incorrectly. = It's important production server, which has its own UPS in addition of = another UPS and generator which backs up the entire server house. If I'll find the time, I'll try to replace GDBM with the SleepyCat DB. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Filters stopping with errcode 90
On Sun, 23 Apr 2006, Rob Arends wrote: I'm trying to track down a non-delivered email. I have found that the root cause was Dario's AVFilter returned errcode 90. Which I believe to be 'normal' for a particular behaviour. The problem is that the next filter did not execute and the email was dropped. The filter is a normal 'in filter' and returns '20' when a Virus is found. It does return various other errcodes, but not the usual xMail documented codes. No problem, xMail just ignores the ones it is not looking for. I had this scary thought that, like DOS cmd file, the errcode is true when the value is equal OR higher. So I checked the xMail doco and it clearly states the if the filter does not return 4,5,6 (and I assume 20,21,22) the message continues. If all filters return values different from '6, 5 and 4' the message continues its trip. I have logs created for filters and smtp, and looking through them, I clearly see that the email was RECV=OK (smtp), and 2 of 3 filters ran. See below the filters log excerpt, showing the errcode 90. pre-data 0 0 d:\Greylist\glst.exe in0 90 D:\AvFilter\AvFilter.exe So the point is, the filter returned 90, why did the next filter not fire - why was the email not delivered? I was running 1.21 at the time and are now running 1.22, but looking at the change log, I don't believe there is any difference in filter handling and execution. Does anyone have any thoughts? Now stop thinking in decimal, and look at it in binary: 4 = 0100 5 = 0101 6 = 0110 16 = 0001 90 = 01011010 For XMail you are returning: = 00010010 ^ ^- 2 + 16 - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: *POSSIBLE SPAM* Re: Re: friend client domain
On Mon, 24 Apr 2006, Jorn Hass wrote: Davide: Seems like your server somehow didn't close the FIN_WAIT_2 state on my server, due to IPFW firewalling. (Known FreeBSD problem...) I have subsequently set the firewalling to limitless connections from troublesome servers like this (Currently 2...), then it manages to close them, as this seems to happen in the IPFW throttling stage on simultaneous connections. Hmm, strange. I tried from my home comcast account and all transactions where correct. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Retry times for temp fail
On Tue, 25 Apr 2006, Rob Arends wrote: Davide, I've just experienced a link down (not nice) but am back online again. During that time, some emails I sent via my local Xmail server bounced back to me. Investigation showed that xmail was retrying to send that email every 32 seconds. I found this in the postmaster bounce email. [PeekTime] 1145928143 : Tue, 25 Apr 2006 11:22:23 +1000 ErrCode = -232 ErrString = Error connecting to remote address SMAIL SMTP-Send MX = dest-smtp-server SMTP = my-smtp-server From = [EMAIL PROTECTED] To = [EMAIL PROTECTED] Failed ! SMTP-Error = 417 Temporary delivery error SMTP-Server = dest-smtp-server repeated at +32seconds, 31(or 32) times - which gives about 17 minutes before bouncing. How or where is this retry set? I am using CMD line including -Qt600 -Qi2 -Qr10 I don't know WTF is going on with you, but if you don't put spaces between command line switches and the param, that ain't gonna work :) Which according to your Zinc.pl gives: 01 send-time = 0 (00:00:00) next-try = 600(00:10:00) 02 send-time = 600(00:10:00) next-try = 900(00:15:00) 03 send-time = 1500 (00:25:00) next-try = 1350 (00:22:30) 04 send-time = 2850 (00:47:30) next-try = 2025 (00:33:45) 05 send-time = 4875 (01:21:15) next-try = 3037 (00:50:37) 06 send-time = 7912 (02:11:52) next-try = 4556 (01:15:56) 07 send-time = 12468 (03:27:48) next-try = 6834 (01:53:54) 08 send-time = 19303 (05:21:43) next-try = 10251 (02:50:51) 09 send-time = 29554 (08:12:34) next-try = 15377 (04:16:17) 10 send-time = 44932 (12:28:52) next-try = 23066 (06:24:26) So I'm confused!!, or are the two retry schedules unrelated. Thanks in adv for your clarification. Rob :-) - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Retry times for temp fail
I don't know WTF is going on with you, but if you don't put spaces between command line switches and the param, that ain't gonna work :) Hmm, thanks for telling me I'm a lamer so nicely !! So I assume that the -Qt -Qi -Qr values defaulted to zero when configured with no space? OR would they have not changed from the default values of 480,16,32. It seems that the -Qr was still 32, but the others were not 480 16. Rob :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, 26 April 2006 3:50 AM To: xmail@xmailserver.org Subject: [xmail] Re: Retry times for temp fail On Tue, 25 Apr 2006, Rob Arends wrote: Davide, I've just experienced a link down (not nice) but am back online again. During that time, some emails I sent via my local Xmail server bounced back to me. Investigation showed that xmail was retrying to send that email every 32 seconds. I found this in the postmaster bounce email. [PeekTime] 1145928143 : Tue, 25 Apr 2006 11:22:23 +1000 ErrCode = -232 ErrString = Error connecting to remote address SMAIL SMTP-Send MX = dest-smtp-server SMTP = my-smtp-server From = [EMAIL PROTECTED] To = [EMAIL PROTECTED] Failed ! SMTP-Error = 417 Temporary delivery error SMTP-Server = dest-smtp-server repeated at +32seconds, 31(or 32) times - which gives about 17 minutes before bouncing. How or where is this retry set? I am using CMD line including -Qt600 -Qi2 -Qr10 I don't know WTF is going on with you, but if you don't put spaces between command line switches and the param, that ain't gonna work :) Which according to your Zinc.pl gives: 01 send-time = 0 (00:00:00) next-try = 600(00:10:00) 02 send-time = 600(00:10:00) next-try = 900(00:15:00) 03 send-time = 1500 (00:25:00) next-try = 1350 (00:22:30) 04 send-time = 2850 (00:47:30) next-try = 2025 (00:33:45) 05 send-time = 4875 (01:21:15) next-try = 3037 (00:50:37) 06 send-time = 7912 (02:11:52) next-try = 4556 (01:15:56) 07 send-time = 12468 (03:27:48) next-try = 6834 (01:53:54) 08 send-time = 19303 (05:21:43) next-try = 10251 (02:50:51) 09 send-time = 29554 (08:12:34) next-try = 15377 (04:16:17) 10 send-time = 44932 (12:28:52) next-try = 23066 (06:24:26) So I'm confused!!, or are the two retry schedules unrelated. Thanks in adv for your clarification. Rob :-) - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
