[xmail] Re: Error message since updating to 1.20
Yes I agree that $mailroot/spool/local and $mailroot/spool/temp are documented and exist in distribution, but the problem occurs when someone wants to clear out the spool they kill all the folders under $mailroot/spool Yes I agree, if you don't know what your doing (and you kill too many folders) then you deserve to have pain. The problem is that these individuals then create noise here wanting help fixing, when a simple check in xmail will create the folders as well as the numbered folders at xmail start, and there is less noise. This also improves the appearance of the stability of Xmail when it fixes up after dumb mistakes. I suppose if the error message that occurred was a little more specific - ie. Error - Mailroot/spool/local folder missing would do just the same. Less noise = more IMAP coding. grin Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, 16 June 2004 2:27 AM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Tue, 15 Jun 2004 [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. Yes, the numberred ones. Tell me again why would you remove directories from the XMail structure? They *are* in the supplied MailRoot and they are documented to be required. - 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: Error message since updating to 1.20
I knew XMail recreated the numbered folders on start-up. I took if for granted that as it recreated the numbered folders it would also recreate the other two. I found the problem when I compared the problematic XMail server to the other one which was still running fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Arends Sent: 16 June 2004 09:37 To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 Yes I agree that $mailroot/spool/local and $mailroot/spool/temp are documented and exist in distribution, but the problem occurs when someone wants to clear out the spool they kill all the folders under $mailroot/spool Yes I agree, if you don't know what your doing (and you kill too many folders) then you deserve to have pain. The problem is that these individuals then create noise here wanting help fixing, when a simple check in xmail will create the folders as well as the numbered folders at xmail start, and there is less noise. This also improves the appearance of the stability of Xmail when it fixes up after dumb mistakes. I suppose if the error message that occurred was a little more specific - ie. Error - Mailroot/spool/local folder missing would do just the same. Less noise = more IMAP coding. grin Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, 16 June 2004 2:27 AM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Tue, 15 Jun 2004 [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. Yes, the numberred ones. Tell me again why would you remove directories from the XMail structure? They *are* in the supplied MailRoot and they are documented to be required. - 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] get a handle on Sober.H spam ?
Hi list, anybody else annoyed by right-wing political spam produced by hosts infected by Sober.G ? (well it maybe a local problem to german speaking users ... anyway it might spread) We are facing a dramatic increase of SMTP traffic due to that. Since there is no attachment AV doesn't get it. Since there is no 'normal' sign of spam (like multiple recipients, junk characters etc.) spamfilters are unlikely to get it either. So my blacklisting logic (discribed earlier here) has no chance to stop those hosts from sending us mail. They _do_ have valid hostnames, so RDNS doesn't either. The only thing I found is, that in the logs at pos. 5 'senderdomain' I find bogus. Now: *) why does RDNS not check ? *) where can we put a filter to do so ? pre-data sounds promising Any comments ? I will try to put up a filter for that as soon as I find some time ... Goesta -- Wiener Hilfswerk - EDV 1072 Wien, Schottenfeldgasse 29 Tel: 512 36 61 DW 407 / Fax 512 36 61 33 -- Attached file included as plaintext by Ecartis -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQEVAwUBQNAV0+EKFiIqAG4fAQISbgf7BOHpt512LB51uGs+f+gzUOqkgg4FrXGt t2MndZ/MZKGvoCvvKP5Hle1mmrLXPePFUosOsK9Co34Vh2ox+QX02JcwpdwyrkLg FfaR9Kp4kZRDAm9Mykc1Lpb8j/JRbpumMjo3tmYWBCbAwOSO3YPK6OOGmrCIIm4k mHZIp0KEePrT3X3n9O4G2GioQ/QRKQbN+Oo+rMgulrPkoT4ujD35Iqnhv506HCYD RaVwe4zcTm9pW7+bfYahOxo3xD3g1v31b6CBE+JO+HqllrePBb/zWb99r4DXo55a wxmla/DBBdbUbI9CGiCsJFZxsVcsWMG0zAMUEkIEE5aMsD5xHkZzUg== =RF+6 -END PGP SIGNATURE- - 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: get a handle on Sober.H spam ?
On [Wed, 16.06. 11:41], Goesta Smekal wrote: *) why does RDNS not check ? *) where can we put a filter to do so ? pre-data sounds promising I just read RFC 822 (again) and the HELO command should pass the domain. So, Davide, is it the contents of this HELO string that ends up as senderdomain in the SMTP logs ? And if 'yes', why is it not RDNS checked ? And ca I do it with pre-data filtering ? (can't wait to start a new filter project again ;-) ) Goesta -- Wiener Hilfswerk - EDV 1072 Wien, Schottenfeldgasse 29 Tel: 512 36 61 DW 407 / Fax 512 36 61 33 -- Attached file included as plaintext by Ecartis -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQEVAwUBQNAZOuEKFiIqAG4fAQJevAf/Z/WHq8Upr6a7ER+m/CyyKCsh54/GJlS3 JD5NjQmKItgDnc/G0hGxY65ZWgRqP9ofph8cQbfEgWUqD5t5s9Ms5+S8Zu/6VYPb q8enFHO/UETCaIx9INulZ/+tuIGnzzYpQdOICLOa+f4t8EKX6Pkxr7O/upGxjE+S +0B86xDNDFm0qnlLvCEJR7ZgjVqXubqBAhukIBs+5mX2D3tBXCVIA641DpH/YaK+ plpKHCeMsf7E9nfNLHAfdp+mHGPBTx8qFcup5oKXeiO9PzZIMMIYuseE1cW87lsb yCHFxxLk6KRLG5HnGsM9nxDHlE3ickJ1MVu/tK8YCdieoX87GHv5Iw== =YDWp -END PGP SIGNATURE- - 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: get a handle on Sober.H spam ?
Hi Goesta, if you are running Spamassassin, some rulesets for stopping those mails are described right here: http://www.heise.de/newsticker/foren/go.shtml?read=1msg_id=5832097forum_id=57381 good look, Achim Am Mi, 2004-06-16 um 11.41 schrieb Goesta Smekal: Hi list, anybody else annoyed by right-wing political spam produced by hosts infected by Sober.G ? (well it maybe a local problem to german speaking users ... anyway it might spread) We are facing a dramatic increase of SMTP traffic due to that. Since there is no attachment AV doesn't get it. Since there is no 'normal' sign of spam (like multiple recipients, junk characters etc.) spamfilters are unlikely to get it either. So my blacklisting logic (discribed earlier here) has no chance to stop those hosts from sending us mail. They _do_ have valid hostnames, so RDNS doesn't either. The only thing I found is, that in the logs at pos. 5 'senderdomain' I find bogus. Now: *) why does RDNS not check ? *) where can we put a filter to do so ? pre-data sounds promising Any comments ? I will try to put up a filter for that as soon as I find some time ... Goesta - 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: get a handle on Sober.H spam ?
On [Wed, 16.06. 13:12], Achim Schmidt wrote: Hi Goesta, if you are running Spamassassin, some rulesets for stopping those mails are described right here: http://www.heise.de/newsticker/foren/go.shtml?read=1msg_id=5832097forum_id=57381 This is exactly the way I _don't_ want to do it. Why ? Because tomorrows junk contains different words an I end up spending hours of my time typing racist phrases into SA rules finally ommitting german communication at all. Actually I'm about to write a filter checking if the HELO domain exists. Hints from Davide are welcome :-) ( for example, wyh doesn't xmail do this in the first place ? ) stay tuned ... Goesta -- Wiener Hilfswerk - EDV 1072 Wien, Schottenfeldgasse 29 Tel: 512 36 61 DW 407 / Fax 512 36 61 33 -- Attached file included as plaintext by Ecartis -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQEVAwUBQNA06OEKFiIqAG4fAQJdYgf/Z4vsrSDdjmMlrp3e6x008dhPS26ixsFY Di3YqKXCA5QLYXKXKrMmqzm5D9cOszz5U2BOQEQlWEyfnyxUWTbd5msHeH9CidV4 mOPNaZlhkIXJTGppEcUyyLdXd36jJroiOBMpnZP/pWD6WHhEB6npr64irdJQfisP YSKlX76uhLFZBqQMbYpLnbhlNpJQkR14EeHP8O7ERJpnf4/yBjeTjS4T+/4AXKes Gq6gQFDO/+iqZx6+Y667eebsPGrsQOF7q+Q1eDyHxwiF5jznd/GaMqF3QsebZ8OH Y8u9ihVzeR5UXAZiYHTRvG9SQzA3vWpqDFvAmYQIwqP65XvDtgPAFw== =QS4e -END PGP SIGNATURE- - 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: email to mailing list delivered several times
At 18:34 14.6.2004, you wrote: On Mon, 14 Jun 2004, Roman Dusek wrote: If you look inside some slog file, you'll see End of socket stream data errors, that means that the connection has been dropped while XMail was trying to read data from the remote SMTP server. If this data happened to be the ack response to the SMTP DATA command, XMail will *obviously* consider the delivery as failed, while the remote server, if not performing checks correctly, might consider the message as received. This smells a lot like either broken MTAs ar very broken firewalls in the middle path. If the situation is as you explained, could the result be that I can find the e-mail to one mailing list member in 10 copies in XMail queue that are all trying to deliver? I suppose if XMail consider the delivery as failed, it should try to deliver it again but not to make another message in its queue and try to deliver both the new one *and* the original one. Are there 10 copies of the *same* mailing list message to the *same* user inside the spool? Exactly, that is the problem. In the file I have posted recently (http://customer.iclub.cz/mail.zip), each directory contained theese copies of the *same* mailing list message to the *same* user that I have found in the spool (16 copies to one user in directory 1, 16 copies to another one user in dir 2 and 4 copies to another user in directory 3) How such user delivery is handled? Does it have a mailproc.tab? I'm not sure if I understand these questions. These users are outside XMail, so no mailproc.tab. They are a kind of companies that are being informed through this mailing list. In fact, this XMail server has one domain with two accounts defined. One account is a mailing list with about 900 mlusers and another one is the user sending the message. Roman - 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: get a handle on Sober.H spam ?
At 05:41 6/16/2004, Goesta Smekal wrote: We are facing a dramatic increase of SMTP traffic due to that. Since there is no attachment AV doesn't get it. Since there is no 'normal' sign of spam (like multiple recipients, junk characters etc.) spamfilters are unlikely to get it either. I can't speak for anyone else, but I've found that denying service to dynamic addresses (based on RDNS patterns) to be a very effective tool for reducing both spam and virus traffic. Since most (not all, as has been pointed out here in the past) dynamic addressed machines are covered by terms of service or acceptable use policies that prohibit the running of servers, a case can be made that these machines should not be sending mail directly to mail servers (other than the ISP responsible for their connectivity). And, of course, if there are specific machines that are running mail servers, they can avoid such a block in two ways: 1) Getting a static IP address from their provider so that you can whitelist the address 2) Getting non-generic RDNS assigned by their provider For example, one of the RDNS patterns that gets blocked here is *-*-*-*.bahnhofbredband.net - this blocks the generically assigned RDNS machines (those with IP addresses in the first portion), while not blocking legitimate mail servers in that domain (as they would not have IP addresses in the first portion of the RDNS value). Of course, blocking based on RDNS takes a minor modification to the source code (or, the use of version 1.19 or later, with a pre-data filter). - 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: get a handle on Sober.H spam ?
--- Tracy [EMAIL PROTECTED] wrote: I can't speak for anyone else, but I've found that denying service to dynamic addresses (based on RDNS patterns) to be a very effective tool for reducing both spam and virus traffic. Since most (not all, as has been pointed out here in the past) dynamic addressed machines are covered by terms of service or acceptable use policies that prohibit the running of servers, a case can be made that these machines should not be sending mail directly to mail servers (other than the ISP responsible for their connectivity). And, of course, if there are specific machines that are running mail servers, they can avoid such a block in two ways: 1) Getting a static IP address from their provider so that you can whitelist the address 2) Getting non-generic RDNS assigned by their provider [...] Of course 1. and 2. are not feasible for about 99% of broadband users who want to run a legitimate mail server. Static address and RDNS is out of the question (an ISP usually charges a busisness rate for this) -Lac - 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: get a handle on Sober.H spam ?
At 10:24 6/16/2004, lac wrote: Of course 1. and 2. are not feasible for about 99% of broadband users who want to run a legitimate mail server. Static address and RDNS is out of the question (an ISP usually charges a busisness rate for this) I think your percentage is a little high (I find the actual answer to be closer to about 40%, rather than 99%, although it is sometimes necessary to talk to the smaller, local providers or resellers rather than dealing with the big boys), although I'm sure it varies based on geographic location. Being in the US, most of my experience is with US providers. And I've found (by dealing with a number of them) that if you manage to get past the front line sales people and talk to someone who actually has a clue what the terms static IP and custom RDNS mean, that it can be set up without a significant additional cost (perhaps a one time cost, or a small monthly fee for the address, if you go with a static IP). For example, my current provider charges me $2 per month per static IP address, and charged me a $50 one time charge to establish DNS mirroring (I run my own DNS servers for my vanity domains, and they provide backup DNS services). Perhaps not the cheapest possible solution, but it isn't like doubling or tripling the monthly cost of the connectivity, either Of course, there are those who would put forward the argument that if you can't distinguish yourself from all the other hosts out there, then you shouldn't be talking direct-to-MX. I'm not sure I agree with that (yet), but the evidence to support that point of view is growing every day. It *is* hard to distinguish legitimate mail servers running on dynamic addresses from the hordes of zombie virus spewing machines. Hence those people who do it right (albeit without the legitimacy of a static IP and/or custom RDNS) get lost in the noise... - 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: get a handle on Sober.H spam ?
=20 1) Getting a static IP address from their provider so that you can whitelist the address 2) Getting non-generic RDNS assigned by their provider [...] Of course 1. and 2. are not feasible for about 99% of broadband users who want to run a legitimate mail server. Static address and RDNS is out of the question (an ISP usually charges a busisness rate for this) It is free with my provider. I know others where it is the same overhere. Certainly not 99% then. And soon you will have no choice if you want any mail send. Some providers over here already block port 25 - 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: get a handle on Sober.H spam ?
lac wrote: --- Tracy [EMAIL PROTECTED] wrote: I can't speak for anyone else, but I've found that denying service to dynamic addresses (based on RDNS patterns) to be a very effective tool for reducing both spam and virus traffic. Since most (not all, as has been pointed out here in the past) dynamic addressed machines are covered by terms of service or acceptable use policies that prohibit the running of servers, a case can be made that these machines should not be sending mail directly to mail servers (other than the ISP responsible for their connectivity). And, of course, if there are specific machines that are running mail servers, they can avoid such a block in two ways: 1) Getting a static IP address from their provider so that you can whitelist the address 2) Getting non-generic RDNS assigned by their provider [...] Of course 1. and 2. are not feasible for about 99% of broadband users who want to run a legitimate mail server. Static address and RDNS is out of the question (an ISP usually charges a busisness rate for this) -Lac I've been grey listing suspect servers, returning a 4xx error in a pre-data filter on the first try, then letting it through on the next, assuming enough time has passed. This does complicate things, as you'll need to track the senders email address and IP address, and the rcpt(s) address in a database -- but it seems to be working well with few false positives. It can potentially delay a good amount of mail however, depending on how you decide what's suspect or not - and gets even more complicated if you have any backup SMTP servers. - 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: get a handle on Sober.H spam ?
At 11:54 6/16/2004, lac wrote: It's funny that the main reason why I'm running my own mail server is the spam. I like having a complete control over creating disposable email accounts. If I buy something from Amazon I create '[EMAIL PROTECTED]' account. When I get spam addressed to '[EMAIL PROTECTED]' I know who sold my info (or where it got stolen :) If that's the main reason you're running a mail server, then you should look into smart-hosting your outbound mail through your ISP's mail servers. That will solve the problem of being blocked due to generic RDNS for you, and will still allow you to control your incoming mail (because the From or Reply-To address will still be the address on your mail server). It will also solve the problem with port 25 blocking on your ISP server (I don't know if your ISP is currently doing that or not, but a lot of the major players are pushing it, so it's really just a matter of time - and if getting a static IP and / or custom RDNS is too big a problem with your provider, I suspect that getting a port 25 blocking exception will be also). - 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: 1.20 out ...
It's ok. I get that too. It's the TLS data associated with the main=20 thread, and it is intentionally never freed. It's not a leak since it is a= =20 one-time allocation. I really do not know what is going on in your=20 machine. After RSS was ~60MB: * addr=0x080be6b8 size=892 from=0809863b from=0808e1b5 from=08055df1 from=08055f03 from=0806be27 from=0806c15c from=0806c357 from=0806c52a * addr=0x0b5af7a0 size=28 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b619eb0 size=20 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b88c398 size=25 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b8cbef0 size=38 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b8986b8 size=38 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b8bbf78 size=23 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b7ed570 size=29 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 * addr=0x0b872f10 size=27 from=0809863b from=0808e1b5 from=08085884 from=0808f62d from=0808f916 from=0804ed46 from=0804c8ea from=0804c4d5 - 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: 1.20 out ...
On Wed, 16 Jun 2004, [iso-8859-1] S=F6nke Ruempler wrote: It's ok. I get that too. It's the TLS data associated with the main=3D2= 0 thread, and it is intentionally never freed. It's not a leak since it is a=3D =3D20 one-time allocation. I really do not know what is going on in your=3D20 machine. =20 After RSS was ~60MB: Well, this is roughly 1Kb of leak :) Mind passing it tru the script I=20 posted you bout three times. Hex numbers are kids difficult to read. =20 =20 * addr=3D0x080be6b8 size=3D892 from=3D0809863b from=3D0808e1b5 from=3D08055df1 from=3D08055f03 from=3D0806be27 from=3D0806c15c from=3D0806c357 from=3D0806c52a * addr=3D0x0b5af7a0 size=3D28 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b619eb0 size=3D20 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b88c398 size=3D25 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b8cbef0 size=3D38 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b8986b8 size=3D38 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b8bbf78 size=3D23 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b7ed570 size=3D29 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 * addr=3D0x0b872f10 size=3D27 from=3D0809863b from=3D0808e1b5 from=3D08085884 from=3D0808f62d from=3D0808f916 from=3D0804ed46 from=3D0804c8ea from=3D0804c4d5 =20 - 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] =20 - 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]
