[xmail] Re: glst tarball windows
gzippd tarbals can be open with this tools (current version) (and for many, with very old versions too ) : 7zip unzip powerarchiver winzip winrar .. .. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoyé : mercredi 15 février 2006 04:43 À : xmail@xmailserver.org Objet : [xmail] Re: glst tarball windows On Tue, 14 Feb 2006, Tony Shiffer wrote: I know this is nuts, but none of the tools I have can open the glst tarball. I do have 3 windows programs that handle tar's, but not this tar. Can someone reccomend a windows program that will unpack Davide's tarball on Windows - or perhaps someone could make the files available for me? Any version of Winzip will work. Also the unzip.exe will work. Google will help you finding this stuff. - 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]
[xmail] Re: glst tarball windows
Davide is true for Unzip :) remove from the list ! -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de CLEMENT Francis Envoyé : mercredi 15 février 2006 10:41 À : 'xmail@xmailserver.org' Objet : [xmail] Re: glst tarball windows gzippd tarbals can be open with this tools (current version) (and for many, with very old versions too ) : 7zip unzip powerarchiver winzip winrar .. .. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mercredi 15 f=E9vrier 2006 04:43 =C0 : xmail@xmailserver.org Objet : [xmail] Re: glst tarball windows On Tue, 14 Feb 2006, Tony Shiffer wrote: I know this is nuts, but none of the tools I have can open=20 the glst tarball. I do have 3 windows programs that handle tar's, but not this=20 tar. Can someone reccomend a windows program that will unpack=20 Davide's tarball on Windows - or perhaps someone could make the files available for me? Any version of Winzip will work. Also the unzip.exe will work.=20 Google will=20 help you finding this stuff. - 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] - 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] Question about Kernel 2.6
I am currently running xmail on Redhat 9 with kernel 2.4.20-8. On RedHat I had to insert the line export LD_ASSUME_KERNEL=2.4 into the xmail startup file. I am currently working on moving my mail server to a stronger box, running Suse 9 with kernel 2.6.5-7.97. Would I have to take this line out or is there any known issues with XMail running on this Kernel? My old mail server has been rock solid, currently with 385 days uptime. Thanks for any feedback, Chad - 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: Spammers - How to block them.
The email response below reminds me of the real causes of your slow-to-drop connections. XMail slows down considerably when I use CustMapsList in server.tab. The process as I understand it for an email that is to be dropped. 1. Remote server starts SMTP connection to xMail. 2. xMail looks up IP in CustMapsList. (if found then goto 5) 3. xMail accepts the [Mail from] and [rcpt to] info. 4. xMail looks up the SMTP-MaxErrors, the local users and aliases, and rejects as needed. (maybe even a predata filter) 5. xMail drops the connection. Ok. Points 1,3,4,5 are all very easy to understand and configure. After all, this is what we have been discussing over the last few days. Point 2 The longer the CustMapsList the longer the delay before xMail can determine that the IP was black listed. xMail will ask each of the RBLs if they have the IP listed, (I think this synchronously, but could be in asynchronously). If synchronously, then the longer the list of RBLS, the longer before xMail can continue. Even asynchronously xMail would have to wait for the last one to reply. Obviously if one of the RBLs returns true, then the process stops immediately. Now even if you don't have a long list of RBLs, the issue could still be in this area. How fast is your DNS server response? If it times out often or just can't cope, that will lengthen the time for the RBL responses to xMail. You can see that one SMTP connection starts a dozen other connections before the user [rcpt to] is even sent to xMail. Now multiply that by all the connections you have, and.. You get the picture. I can't remember the number of times xMail connection faults have been reported on this list and they boiled down to DNS issues. Please check your DNS response time and potentially reduce the RBL list, or put the most likely match as the first RBL listed. Get Ethereal and watch your SMTP traffic, you will be amazed at the amount of traffic one connection spawns. It will also give you an idea of your DNS traffic. Remember to use a hub (or a switch with a monitor port) to capture the traffic, unless you run Ethereal on the xMail server. Rob :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henri van Riel Sent: Wednesday, February 15, 2006 6:19 AM To: Jeff Buehler Cc: xmail@xmailserver.org Subject: [xmail] Re: Spammers - How to block them. Hi Jeff, I suspect this makes little difference, but just in case you aren't aware of this, you can run ASSP on a different computer - it doesn't have to be the same system, and so Perl also does not need to be on your XMail system. I'm not certain why you have feelings about running something in front of XMail if it will simply reduce the burden on your server (significantly) but we all have our reasons, I suppose! The main reason for not wanting anything installed before XMail is mainly because I've been having bad experiences with AVmailGate but also because I'd much rather have XMail solve my problem. There must be a way without having to install (and maintain) several tools. If you aren't processing much email, then I can't understand why you are getting the server too busy errors you mentioned in your first email. Something doesn't sound quite right. Frankly, even before I was running ASSP, I was processing quite a bit of email (thousands a day, sometimes more, and thousands more a day of SPAM) and I never received an error like that on send. That's odd. How many smtp threads were you running? I've set the maximum to 16 now where 4 should be enough to handle all incoming mail (easily!). I understood you to say that you were getting SMTP connect errors because XMail was taking too long to refuse invalid users. Logically, if you are receiving server too busy errors simply from refusing emails to non-valid users (as I read your first email to be saying), which would require an incredible volume of invalid email (or a very, very slow server), then the only way to prevent server overload would be to put something in front of XMail, since XMail is already refusing those emails that are causing the problem. But I must have misunderstood given the direction the rest of this thread has taken. The server won't break any speed records, that's true. Still, it should be more than good enough for my purposes. XMail slows down considerably when I use CustMapsList in server.tab. My guess is that these services are very slow and XMail has to check 4 or 5 for each and every email it receives. I guess all my smtp threads are busy waiting for a reply from these anti-spam services and are unable to allow other connections. Setting SMTP-RDNSCheck to 1 in my server.tab also slows down mail processing in XMail. If it is simply an issue of SPAM in general, and you need to block it, and you don't want to use something like ASSP (for reasons of purity?), then your best bet is greylisting (as Rob Arends covers
[xmail] Re: Question about Kernel 2.6
On Wednesday 15 February 2006 09:02, Chad Fleenor wrote: I am currently running xmail on Redhat 9 with kernel 2.4.20-8. On RedHat I had to insert the line export LD_ASSUME_KERNEL=2.4 into the xmail startup file. I am currently working on moving my mail server to a stronger box, running Suse 9 with kernel 2.6.5-7.97. Would I have to take this line out or is there any known issues with XMail running on this Kernel? I've run XMail on several different versions of SuSE without problems. I currently have a server running on 9.1 and am testing openSUSE 10.0-OSS, both unmodified and without any issues. I'm also running a mail server on Mandriva 2006.0 and while XMail runs fine, I've had trouble installing some of the SpamAssassin modules. I'd have to look it up, but off the top of my head I think it was the Net::Ident module that I couldn't install on Mandriva. My old mail server has been rock solid, currently with 385 days uptime. Very Nice! Jeff - 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: Spammers - How to block them.
To reduce CustMapsList processing time, you can, with most of 'big blacklist' mainteners (spamcop, rbl, ..) do local a mirror for the zones in a local dns server, so you could reduce dns traffic dramaticaly and custmaplist response time by saying xmail to use the local dns server. Note that I never used this setup for local custmaslists, as we have enought bandwidth et power for our current usage. So don't ask me how to do (or at last ressort ;-) ). First check the list maintener web site for instructions ;-) Francis -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Rob Arends Envoyé : mercredi 15 février 2006 15:07 À : xmail@xmailserver.org Objet : [xmail] Re: Spammers - How to block them. The email response below reminds me of the real causes of your slow-to-drop connections. XMail slows down considerably when I use CustMapsList in server.tab. The process as I understand it for an email that is to be dropped. 1. Remote server starts SMTP connection to xMail. 2. xMail looks up IP in CustMapsList. (if found then goto 5) 3. xMail accepts the [Mail from] and [rcpt to] info. 4. xMail looks up the SMTP-MaxErrors, the local users and aliases, and rejects as needed. (maybe even a predata filter) 5. xMail drops the connection. Ok. Points 1,3,4,5 are all very easy to understand and configure. After all, this is what we have been discussing over the last few days. Point 2 The longer the CustMapsList the longer the delay before xMail can determine that the IP was black listed. xMail will ask each of the RBLs if they have the IP listed, (I think this synchronously, but could be in asynchronously). If synchronously, then the longer the list of RBLS, the longer before xMail can continue. Even asynchronously xMail would have to wait for the last one to reply. Obviously if one of the RBLs returns true, then the process stops immediately. Now even if you don't have a long list of RBLs, the issue could still be in this area. How fast is your DNS server response? If it times out often or just can't cope, that will lengthen the time for the RBL responses to xMail. You can see that one SMTP connection starts a dozen other connections before the user [rcpt to] is even sent to xMail. Now multiply that by all the connections you have, and.. You get the picture. I can't remember the number of times xMail connection faults have been reported on this list and they boiled down to DNS issues. Please check your DNS response time and potentially reduce the RBL list, or put the most likely match as the first RBL listed. Get Ethereal and watch your SMTP traffic, you will be amazed at the amount of traffic one connection spawns. It will also give you an idea of your DNS traffic. Remember to use a hub (or a switch with a monitor port) to capture the traffic, unless you run Ethereal on the xMail server. Rob :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henri van Riel Sent: Wednesday, February 15, 2006 6:19 AM To: Jeff Buehler Cc: xmail@xmailserver.org Subject: [xmail] Re: Spammers - How to block them. Hi Jeff, I suspect this makes little difference, but just in case you aren't aware of this, you can run ASSP on a different computer - it doesn't have to be the same system, and so Perl also does not need to be on your XMail system. I'm not certain why you have feelings about running something in front of XMail if it will simply reduce the burden on your server (significantly) but we all have our reasons, I suppose! The main reason for not wanting anything installed before XMail is mainly because I've been having bad experiences with AVmailGate but also because I'd much rather have XMail solve my problem. There must be a way without having to install (and maintain) several tools. If you aren't processing much email, then I can't understand why you are getting the server too busy errors you mentioned in your first email. Something doesn't sound quite right. Frankly, even before I was running ASSP, I was processing quite a bit of email (thousands a day, sometimes more, and thousands more a day of SPAM) and I never received an error like that on send. That's odd. How many smtp threads were you running? I've set the maximum to 16 now where 4 should be enough to handle all incoming mail (easily!). I understood you to say that you were getting SMTP connect errors because XMail was taking too long to refuse invalid users. Logically, if you are receiving server too busy errors simply from refusing emails to non-valid users (as I read your first email to be saying), which would require an incredible volume of invalid email (or a very, very slow server), then the only way to prevent server overload would be to put something in front of XMail, since XMail is already refusing those emails that are causing the problem. But I must have misunderstood given the
[xmail] Re: Spammers - How to block them.
Hello Rob, Tuesday, February 14, 2006, 2:19:14 PM, you wrote: Try SMTP-MaxErrors1 In server.tab If there is ONE erroneous RCPT TO, then dump the connection. I've tried it and it works really well! The only problem is... even a legitimate server can cause an smtp error every once in a while... Once you kill off all the repeat connections, then you might increase to 2, and combine with your script to cover other issues. I have mine set to 3. I'll set it to 3 and watch the log for errors. GLST - I have Windows, so it was all built into glst.exe. I don't know for Linux. Thanks for the hint anyway! -- Henri. - 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] smtp works / pop doesn't
Hey all, I successfully installed xmail on a NSLU2 and it works very well. But when I open outlook or a similar email-app it can find the pop server but fails to log in. I use [EMAIL PROTECTED] as a loginname and the password is 100% correct. When I telnet to server:110 I get a login message and when I type my username and hit enter, the telnetbox disappears. Where did I go wrong or what point did I miss? Gr. Martin - 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: Odd connections...
On Wed, 15 Feb 2006, Henri van Riel wrote: I noticed something weird... I'm monitoring my mailserver very closely because of the recent problems and I noticed x35.xmailserver.org (69.30.125.51) connects to my server every now and then: # netstat -a | grep myserver:25, returns: tcp 0 0 myserver:25 x35.xmailserver.o:37670 ESTABLISHED This was a couple of minutes ago, around 5pm my time. Obviously I thought there was mail coming in from the list but when I checked there was nothing. That's odd. To be sure, I checked my smtp log and it said the last connection from that server was at 10:46 my time... Shouldn't the connection have shown up in my smtp log? Why would a server connect to xmail and not deliver mail? If it would have been rejected it would have showed up in the log I think. This can happen for various reasons, like your server stuck in a DNS local address resolution (done at the very beginning of the SMTP session) or by something happened to the network in the middle that broke the link. - 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]
