[xmail] Re: 1.25-pre06 ...
Heheh.. try [EMAIL PROTECTED] The A record points to 192.168.0.51 and there is no MX... Ivo - Original Message - From: Davide Libenzi [EMAIL PROTECTED] To: xmail@xmailserver.org Sent: Friday, April 20, 2007 4:05 AM Subject: [xmail] Re: 1.25-pre06 ... On Thu, 19 Apr 2007, Tom Banting wrote: How can you get an A record if the name servers are off line? What am I missing? The only A records you have are for the off line name servers. Doesn't matter. I can see the attempt to deliver to the A-record from the logs. That's enough for me. - 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: 1.25-pre06 ...
On Fri, 20 Apr 2007, Ivo Smits wrote: Heheh.. try [EMAIL PROTECTED] The A record points to 192.168.0.51 and there is no MX... As I already said, that test is already done. Now I need a domain with all NS to be out of service, to verify that XMail does not try A-record. - 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: 1.25-pre06 ...
Davide- Can you try gosouthampton.com? I own the domain, and dig won't bring back anything on the domain even though there are nameservers listed for the domain. Davide Libenzi wrote: On Fri, 20 Apr 2007, Ivo Smits wrote: Heheh.. try [EMAIL PROTECTED] The A record points to 192.168.0.51 and there is no MX... As I already said, that test is already done. Now I need a domain with all NS to be out of service, to verify that XMail does not try A-record. - 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] -- Robert Schiffman Director of Technology Lounge Lizard Worldwide, Inc. 620 Johnson Ave. Suite 1B Bohemia, NY 11716 631-563-6165 ext. 21 631-563-6278 (fax) Email: [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: 1.25-pre06 ...
On Fri, 20 Apr 2007, Robert Schiffman wrote: Davide- Can you try gosouthampton.com? I own the domain, and dig won't bring back anything on the domain even though there are nameservers listed for the domain. Ok, I verfied both cases: 1) NS avaiblable, but no MX. Correctly send to A-record 2) NS avaiblable but out-of-reach. Correctly do *not* send to A-record - 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: 1.25-pre06 ...
On Thu, 19 Apr 2007, Rob Arends wrote: Davide, I have some domains I can play with if you like to do what you want. What specific 'errors' do you want to create. The last test I have to run, requires having a registered domain whose NS servers are out-of-reach. This to test that XMail will not try A-record delivery in that case. - 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: 1.25-pre06 ...
How can you get an A record if the name servers are off line? What am I missing? The only A records you have are for the off line name servers. At 02:21 PM 19/04/2007, you wrote: On Thu, 19 Apr 2007, Rob Arends wrote: Davide, I have some domains I can play with if you like to do what you want. What specific 'errors' do you want to create. The last test I have to run, requires having a registered domain whose NS servers are out-of-reach. This to test that XMail will not try A-record delivery in that case. - 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.25-pre06 ...
On Thu, 19 Apr 2007, Tom Banting wrote: How can you get an A record if the name servers are off line? What am I missing? The only A records you have are for the off line name servers. Doesn't matter. I can see the attempt to deliver to the A-record from the logs. That's enough for me. - 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: 1.25-pre06 ...
Ho hum ... Convenient to blame a temp net error for the first dns related error I've seen in ages, right after testing your new dns resolving code. Coincidence maybe. This is going nowhere - end thread. :-( Question: how many other MTAs do their own DNS lookups ? Do they use the OS resolver setting ? What is the benefit of Xmail doing the dns resolution entirely by itself? Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, April 18, 2007 11:51 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Wed, 18 Apr 2007, Rob Arends wrote: SO Getting back to the real issue at hand... Why would a VERY large ISP (optusnet.com.au) be broken. It certainly is not broken now when DIGs are done. The only difference is that one NS that wasn't responding - it now is. And you say that xmail tries all NS records until it gets valid results or all NS are exhausted, so one NS not responding should not be a problem. Unfortunately the reason I switched to SMARTDNSHOST years ago was due to the reliability of xmail's DNS lookup routines. I use 'named' as a caching DNS server and point xmail to it and have had very little problem caused by lookup failure since. Within one day of trying NO SMARTDNSHOST on 1.25pre06, I had undeliverable emails. I have since re-enabled SMARTDNSHOST and again I have no problems (the user has resent the emails successfully). I had no problems in sending to that domain, and in general I had no problems whatsoever so far with it. You didn't try to resend to that domain, did you? You probably hit a temporary network problem, you saw the message XMail generated, and you posted to the mailing list. Why it is more rare that you see this using a 'named' resolver? Because 'named' caches *everything*, so it is easier that temporary network problems end up being hidden by its caching. - 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: 1.25-pre06 ...
so it is easier that temporary network problems end up being hidden by its caching. - Davide But why should a temporary network problem cause any issue in the first place, unless that problem is a bad DNS entry? Network connectivity issues during a DNS query should at most cause a delay in sending the mail, but the mail should eventually get through without user intervention. I'm still concerned that your fall back to A after MX timeout could cause a permanent delivery failure (trying to send to the host pointed to by the A record, potentially hitting an SMTP server that would refuse the delivery) when the failure should only be temporary (can't get any results from the domain's DNS servers due to a network failure somewhere while trying to lookup the MX record). Admittedly, this would be a _very_ small window of opportunity, but still possible if Xmail handles this as you suggest. - 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.25-pre06 ...
On Thu, 19 Apr 2007, Rob Arends wrote: Ho hum ... Convenient to blame a temp net error for the first dns related error I've seen in ages, right after testing your new dns resolving code. Coincidence maybe. This is going nowhere - end thread. :-( It was a temporary error, wasn't it? Thing that the majority of other MTAs won't even bother to tell you in the first place, so you sleep happy. I already explained you, in the previous email, why this can happen. Question: how many other MTAs do their own DNS lookups ? Do they use the OS resolver setting ? What is the benefit of Xmail doing the dns resolution entirely by itself? And how many of them runs natively on basically all unxes and all windows w/out requiring you to fetch and link other 37 libraries? If, from the hight of your experience, you can tell me a POSIX function that does MX lookups and is supported natively by ll unx and all windows, that would be great. - 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: 1.25-pre06 ...
On Wed, 18 Apr 2007, John Kielkopf wrote: so it is easier that temporary network problems end up being hidden by its caching. - Davide But why should a temporary network problem cause any issue in the first place, unless that problem is a bad DNS entry? Network connectivity issues during a DNS query should at most cause a delay in sending the mail, but the mail should eventually get through without user intervention. I'm still concerned that your fall back to A after MX timeout could cause a permanent delivery failure (trying to send to the host pointed to by the A record, potentially hitting an SMTP server that would refuse the delivery) when the failure should only be temporary (can't get any results from the domain's DNS servers due to a network failure somewhere while trying to lookup the MX record). Admittedly, this would be a _very_ small window of opportunity, but still possible if Xmail handles this as you suggest. That can be done. Anyone has a domain name with no MX handy, for me to test? - 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: 1.25-pre06 ...
On Wed, 18 Apr 2007, Davide Libenzi wrote: On Wed, 18 Apr 2007, John Kielkopf wrote: so it is easier that temporary network problems end up being hidden by its caching. - Davide But why should a temporary network problem cause any issue in the first place, unless that problem is a bad DNS entry? Network connectivity issues during a DNS query should at most cause a delay in sending the mail, but the mail should eventually get through without user intervention. I'm still concerned that your fall back to A after MX timeout could cause a permanent delivery failure (trying to send to the host pointed to by the A record, potentially hitting an SMTP server that would refuse the delivery) when the failure should only be temporary (can't get any results from the domain's DNS servers due to a network failure somewhere while trying to lookup the MX record). Admittedly, this would be a _very_ small window of opportunity, but still possible if Xmail handles this as you suggest. That can be done. Anyone has a domain name with no MX handy, for me to test? Never mind, found it (example.com :) Now I see XMail going to A-record when sending to example.com, that is right. Now I need to test the other part, that is a temporary remote DNS error ... - 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: 1.25-pre06 ...
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mardi 17 avril 2007 01:49 =C0 : xmail@xmailserver.org Objet : [xmail] Re: 1.25-pre06 ... On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I have had to turn on smartdnshost again. =20 After having an error-free run for quite a while, this=20 morning I see errors. Investigation shows. =20 Issue 1: - - Partial Bounce email content: (I've swapped @ for *) =20 ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] =20 ErrCode =3D -217 ErrString =3D Error connecting to remote address No problems here (trying to send to a bogus address in that domain): [00] XMail bounce:=20 [EMAIL PROTECTED];Error=3D[553=20 5.3.0[EMAIL PROTECTED]... No such user] [01] Error sending message=20 [1176767187543.1082977200.2724.x35.xmailserver.org] from=20 [xmailserver.org]. ID:S2233ED Mail From: [EMAIL PROTECTED] Rcpt To: [EMAIL PROTECTED] Server:mail.optusnet.com.au [211.29.132.250] [02] The reason of the delivery failure was: 553 5.3.0 [EMAIL PROTECTED]... No such user - Davide I don't understand your response, Davide, as Rob pointed out the fact = that xmail tried to connect to Server:www.optusnet.com.au [211.29.132.105] And you response used :=20 Server:mail.optusnet.com.au [211.29.132.250] So, even if the final user doesn't exist, it's not the real problem mentionned/reported by Rob :) The question seems to be (correct me, Rob, if not correct) : Why xmail used/choosed/got/tried/... WWW.optusnet.com.au on Rob server = and not MAIL.optusnet.com.au the effectively declared MX for optusnet.com, = as your server ? And Rob digs seemed to proove that there is no 'dns' problem from its = server as a mx search return effectively MAIL.optusnet.com as the MX !?!? Rfc seems to say (if I interpreted them correctly) : IF at least one mx entry is found user ONLY the mx list, even if all/some busy, = unreachable, (next retries must continue to use the MX entries, and never fallback = to A records). A records usage could be used only as an alternative = auto mx when NO mx entries exist. A dns server in the route that automaticaly add the A record as an 'autogenerated' MX entry ? Any test that Rob could run to try to find the reason (bad isp cache = dns, ) ? Francis - 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.25-pre06 ...
On Tue, 17 Apr 2007, CLEMENT Francis wrote: I don't understand your response, Davide, as Rob pointed out the fact = that xmail tried to connect to Server:www.optusnet.com.au [211.29.132.105] And you response used :=20 Server:mail.optusnet.com.au [211.29.132.250] That means that 1.25-pre06 looked up the MX just fine here. So, even if the final user doesn't exist, it's not the real problem mentionned/reported by Rob :) The question seems to be (correct me, Rob, if not correct) : Why xmail used/choosed/got/tried/... WWW.optusnet.com.au on Rob server = and not MAIL.optusnet.com.au the effectively declared MX for optusnet.com, = as your server ? And Rob digs seemed to proove that there is no 'dns' problem from its = server as a mx search return effectively MAIL.optusnet.com as the MX !?!? Rfc seems to say (if I interpreted them correctly) : IF at least one mx entry is found user ONLY the mx list, even if all/some busy, = unreachable, (next retries must continue to use the MX entries, and never fallback = to A records). A records usage could be used only as an alternative = auto mx when NO mx entries exist. XMail either gets an MX or it tries the A record, that is *exactly* the domain name. That was WWW.domainname, and the *only* way it could have got there, is as a MX. Strange thing is, that host does not appear anywhere in the DNS packets at the moment. A temporary screw up on their DNS? - 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: 1.25-pre06 ...
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mardi 17 avril 2007 01:53 =C0 : xmail@xmailserver.org Objet : [xmail] Re: 1.25-pre06 ... On Mon, 16 Apr 2007, Davide Libenzi wrote: On Tue, 17 Apr 2007, Rob Arends wrote: =20 Davide, I have had to turn on smartdnshost again. =20 After having an error-free run for quite a while, this=20 morning I see errors. Investigation shows. =20 Issue 1: - - Partial Bounce email content: (I've swapped @ for *) =20 ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] =20 ErrCode =3D -217 ErrString =3D Error connecting to remote address And, BTW, www.optusnet.com.au is *NOT* the A record. If=20 Yes it is : set type=3Da optusnet.com.au Nom=A0:optusnet.com.au Address: 211.29.132.105 set type=3Dptr 211.29.132.105 105.132.29.211.in-addr.arpa name =3D www.optusnet.com.au XMail would have=20 tried the A record, you should have seen optusnet.com.au in there. So, the questions are : - In this case specific 'bad name reported in the error', how xmail get (perhabs not its decision ?) and report www.optusnet.com.au as the name = and not optusnet.com.au as it should be ? =20 - And this does not response to the more general question, Why the A ip address used here and not the existing MX entries (even if only one and eventually busy, unreachable, ...) Any possibility to 'trace' xmail dns stack and algo in a log to see = then and why the decision to use the A is taken ? (tcp dump are not suffisent here as whe could not see xmail decision on = dns responses) Francis - 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: 1.25-pre06 ...
On Tue, 17 Apr 2007, CLEMENT Francis wrote: And, BTW, www.optusnet.com.au is *NOT* the A record. If=20 Yes it is : set type=3Da optusnet.com.au Nom=A0:optusnet.com.au Address: 211.29.132.105 set type=3Dptr 211.29.132.105 105.132.29.211.in-addr.arpa name =3D www.optusnet.com.au Ok, it is clear that you do not understand how XMail and in general the fallback-to-A-record works ;) The A record tried by XMail *is* the domain name, not fscking WWW.domainname :) - 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: 1.25-pre06 ...
On Tue, 17 Apr 2007, CLEMENT Francis wrote: Possible it's a dns server problem Who does xmail response on a timeout after dns query ? Who many retries = ? And final decision on dns timeout ? A record tries ? I ask this because, I noticed that dns timeouts are frequent with some french isp especially on udp (qos ? prioritization ?), and an immediate retry generally get the response. A timeout (inside the DNS retry policy rule) from every domain DNS server is treated as failure to get the MX, hence the A record is tried. - 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: 1.25-pre06 ...
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mardi 17 avril 2007 09:14 =C0 : 'xmail@xmailserver.org' Objet : [xmail] Re: 1.25-pre06 ... On Tue, 17 Apr 2007, CLEMENT Francis wrote: And, BTW, www.optusnet.com.au is *NOT* the A record. If=3D20 =20 Yes it is : =20 set type=3D3Da optusnet.com.au Nom=3DA0:optusnet.com.au Address: 211.29.132.105 =20 set type=3D3Dptr 211.29.132.105 105.132.29.211.in-addr.arpa name =3D3D www.optusnet.com.au Ok, it is clear that you do not understand how XMail and in=20 general the=20 fallback-to-A-record works ;) The A record tried by XMail *is* the domain name, not fscking=20 WWW.domainname :) - Davide Sorry, I just didn't understand that your first response pointed out = the fact that xmail reported the domain name not the ptr query to the ip. But on 'fallback-to-A-record', I have not the same point of view :) Francis - 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.25-pre06 ...
On Tue, 17 Apr 2007, CLEMENT Francis wrote: Sorry, I just didn't understand that your first response pointed out = the fact that xmail reported the domain name not the ptr query to the ip. But on 'fallback-to-A-record', I have not the same point of view :) It'd be good to know if Rob can reproduce the problem (after having nuked the DNS MX cache). - 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: 1.25-pre06 ...
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mardi 17 avril 2007 09:38 =C0 : 'xmail@xmailserver.org' Objet : [xmail] Re: 1.25-pre06 ... On Tue, 17 Apr 2007, CLEMENT Francis wrote: Possible it's a dns server problem Who does xmail response on a timeout after dns query ? Who=20 many retries =3D ? And final decision on dns timeout ? A record tries ? I ask this because, I noticed that dns timeouts are frequent=20 with some french isp especially on udp (qos ? prioritization ?), and=20 an immediate retry generally get the response. A timeout (inside the DNS retry policy rule) from every domain=20 DNS server=20 is treated as failure to get the MX, hence the A record is tried. - Davide Ok, so is it possible to change the timeout value or change the number = of dns queries retries, even if 'out of dns standard retry policy rule', = as because some dns servers don't accept tcp connexions, and many packets = are lost due to qos policies at isp side and slow or busy lines, some xmail admins should really have to delay the ultimate 'A record attempts' to = have chances to get really existing mx records ? Francis - 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.25-pre06 ...
And, BTW, www.optusnet.com.au is *NOT* the A record. If XMail would have tried the A record, you should have seen optusnet.com.au in there. I do (from previous post) optusnet.com.au.37147 IN A 211.29.132.105 But the rev dns is : C:\dig -x 211.29.132.105 ; DiG 9.2.3 -x 211.29.132.105 ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;105.132.29.211.in-addr.arpa. IN PTR ;; ANSWER SECTION: 105.132.29.211.in-addr.arpa. 66125 IN PTR www.optusnet.com.au. ^ ;; AUTHORITY SECTION: 132.29.211.in-addr.arpa. 66125 IN NS ns2.optusnet.com.au. 132.29.211.in-addr.arpa. 66125 IN NS ns1.optusnet.com.au. ;; ADDITIONAL SECTION: ns1.optusnet.com.au.17134 IN A 203.2.75.2 ns2.optusnet.com.au.17134 IN A 203.2.75.12 ;; Query time: 0 msec ;; SERVER: 10.90.10.151#53(ns1) ;; WHEN: Tue Apr 17 14:09:43 2007 ;; MSG SIZE rcvd: 146 And of course the dns names shown in my post were from xmail - which got them from rev dns. So I agree with you, the www.optusnet.com.au is *NOT* the A record. But there is an A record that matches the domain where you would usually see the MX In this case there are both A MX for optusnet.com.au Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Tuesday, April 17, 2007 9:53 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Mon, 16 Apr 2007, Davide Libenzi wrote: On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I have had to turn on smartdnshost again. After having an error-free run for quite a while, this morning I see errors. Investigation shows. Issue 1: - - Partial Bounce email content: (I've swapped @ for *) ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] ErrCode = -217 ErrString = Error connecting to remote address And, BTW, www.optusnet.com.au is *NOT* the A record. If XMail would have tried the A record, you should have seen optusnet.com.au in there. - 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: 1.25-pre06 ...
.optusnet.com.au. optusnet.com.au.86400 IN NS ns1.optusnet.com.au. ;; Received 138 bytes from 203.2.75.2#53(ns1.optusnet.com.au) in 4171 ms C:\ How you get a TLDcc with a lame NS - I don't know. Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Tuesday, April 17, 2007 9:49 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I have had to turn on smartdnshost again. After having an error-free run for quite a while, this morning I see errors. Investigation shows. Issue 1: - - Partial Bounce email content: (I've swapped @ for *) ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] ErrCode = -217 ErrString = Error connecting to remote address No problems here (trying to send to a bogus address in that domain): [00] XMail bounce: [EMAIL PROTECTED];Error=[553 5.3.0[EMAIL PROTECTED]... No such user] [01] Error sending message [1176767187543.1082977200.2724.x35.xmailserver.org] from [xmailserver.org]. ID:S2233ED Mail From: [EMAIL PROTECTED] Rcpt To: [EMAIL PROTECTED] Server:mail.optusnet.com.au [211.29.132.250] [02] The reason of the delivery failure was: 553 5.3.0 [EMAIL PROTECTED]... No such user - 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: 1.25-pre06 ...
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Rob Arends Envoy=E9 : mardi 17 avril 2007 06:29 =C0 : xmail@xmailserver.org Objet : [xmail] Re: 1.25-pre06 ... Davide, I think the cause is shown here: C:\dig @ns1 optusnet.com.au mx +trace ; DiG 9.2.3 @ns1 optusnet.com.au mx +trace ;; global options: printcmd .. 361774 IN NS L.ROOT-SERVERS.NET. .. 361774 IN NS M.ROOT-SERVERS.NET. .. 361774 IN NS A.ROOT-SERVERS.NET. .. 361774 IN NS B.ROOT-SERVERS.NET. .. 361774 IN NS C.ROOT-SERVERS.NET. .. 361774 IN NS D.ROOT-SERVERS.NET. .. 361774 IN NS E.ROOT-SERVERS.NET. .. 361774 IN NS F.ROOT-SERVERS.NET. .. 361774 IN NS G.ROOT-SERVERS.NET. .. 361774 IN NS H.ROOT-SERVERS.NET. .. 361774 IN NS I.ROOT-SERVERS.NET. .. 361774 IN NS J.ROOT-SERVERS.NET. .. 361774 IN NS K.ROOT-SERVERS.NET. ;; Received 292 bytes from 10.90.10.151#53(ns1) in 0 ms au. 172800 IN NS ns.uu.net. au. 172800 IN NS dns1.telstra.net. au. 172800 IN NS sec1.apnic.net. au. 172800 IN NS sec3.apnic.net. au. 172800 IN NS adns1.berkeley.edu. au. 172800 IN NS adns2.berkeley.edu. au. 172800 IN NS audns.optus.net. au. 172800 IN NS aunic.aunic.net. ;; Received 387 bytes from 198.32.64.12#53(L.ROOT-SERVERS.NET)=20 in 203 ms dig: Couldn't find server 'ns.uu.net' (h_errno=3D11001) Then tried again immediately C:\dig @ns1 optusnet.com.au mx +trace ; DiG 9.2.3 @ns1 optusnet.com.au mx +trace ;; global options: printcmd .. 361741 IN NS J.ROOT-SERVERS.NET. .. 361741 IN NS K.ROOT-SERVERS.NET. .. 361741 IN NS L.ROOT-SERVERS.NET. .. 361741 IN NS M.ROOT-SERVERS.NET. .. 361741 IN NS A.ROOT-SERVERS.NET. .. 361741 IN NS B.ROOT-SERVERS.NET. .. 361741 IN NS C.ROOT-SERVERS.NET. .. 361741 IN NS D.ROOT-SERVERS.NET. .. 361741 IN NS E.ROOT-SERVERS.NET. .. 361741 IN NS F.ROOT-SERVERS.NET. .. 361741 IN NS G.ROOT-SERVERS.NET. .. 361741 IN NS H.ROOT-SERVERS.NET. .. 361741 IN NS I.ROOT-SERVERS.NET. ;; Received 308 bytes from 10.90.10.151#53(ns1) in 15 ms au. 172800 IN NS SEC3.APNIC.NET. au. 172800 IN NS ADNS1.BERKELEY.EDU. au. 172800 IN NS ADNS2.BERKELEY.EDU. au. 172800 IN NS AUDNS.OPTUS.NET. au. 172800 IN NS AUNIC.AUNIC.NET. au. 172800 IN NS NS.UU.NET. au. 172800 IN NS DNS1.TELSTRA.NET. au. 172800 IN NS SEC1.APNIC.NET. ;; Received 387 bytes from=20 192.58.128.30#53(J.ROOT-SERVERS.NET) in 46 ms com.au. 259200 IN NS ns3.ausregistry.net. com.au. 259200 IN NS ns3.melbourneit.com. com.au. 259200 IN NS ns4.ausregistry.net. com.au. 259200 IN NS ns5.ausregistry.net. com.au. 259200 IN NS ns6.ausregistry.net. com.au. 259200 IN NS dns1.telstra.net. com.au. 259200 IN NS au2ld.CSIRO.au. com.au. 259200 IN NS audns.optus.net. com.au. 259200 IN NS ns-au.ripe.net. com.au. 259200 IN NS ns1.ausregistry.net. com.au. 259200 IN NS ns2.ausregistry.net. ;; Received 309 bytes from 202.12.28.140#53(SEC3.APNIC.NET) in 312 ms optusnet.com.au.86400 IN NS ns1.optusnet.com.au. optusnet.com.au.86400 IN NS ns2.optusnet.com.au. ;; Received 101 bytes from=20 203.18.56.43#53(ns3.ausregistry.net) in 31 ms optusnet.com.au.86400 IN MX 50=20 mail.optusnet.com.au
[xmail] Re: 1.25-pre06 ...
On Tue, 17 Apr 2007, Rob Arends wrote: And, BTW, www.optusnet.com.au is *NOT* the A record. If XMail would have tried the A record, you should have seen optusnet.com.au in there. I do (from previous post) optusnet.com.au.37147 IN A 211.29.132.105 But the rev dns is : C:\dig -x 211.29.132.105 ; DiG 9.2.3 -x 211.29.132.105 ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;105.132.29.211.in-addr.arpa. IN PTR ;; ANSWER SECTION: 105.132.29.211.in-addr.arpa. 66125 IN PTR www.optusnet.com.au. ^ XMail passes down the domain name, that'd been optusnet.com.au. There is no way www.optusnet.com.au could have been shawn in there is it wasn't coming from an MX response. - 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: 1.25-pre06 ...
On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I think the cause is shown here: C:\dig @ns1 optusnet.com.au mx +trace ; DiG 9.2.3 @ns1 optusnet.com.au mx +trace ;; global options: printcmd .. 361774 IN NS L.ROOT-SERVERS.NET. .. 361774 IN NS M.ROOT-SERVERS.NET. .. 361774 IN NS A.ROOT-SERVERS.NET. .. 361774 IN NS B.ROOT-SERVERS.NET. .. 361774 IN NS C.ROOT-SERVERS.NET. .. 361774 IN NS D.ROOT-SERVERS.NET. .. 361774 IN NS E.ROOT-SERVERS.NET. .. 361774 IN NS F.ROOT-SERVERS.NET. .. 361774 IN NS G.ROOT-SERVERS.NET. .. 361774 IN NS H.ROOT-SERVERS.NET. .. 361774 IN NS I.ROOT-SERVERS.NET. .. 361774 IN NS J.ROOT-SERVERS.NET. .. 361774 IN NS K.ROOT-SERVERS.NET. ;; Received 292 bytes from 10.90.10.151#53(ns1) in 0 ms au. 172800 IN NS ns.uu.net. au. 172800 IN NS dns1.telstra.net. au. 172800 IN NS sec1.apnic.net. au. 172800 IN NS sec3.apnic.net. au. 172800 IN NS adns1.berkeley.edu. au. 172800 IN NS adns2.berkeley.edu. au. 172800 IN NS audns.optus.net. au. 172800 IN NS aunic.aunic.net. ;; Received 387 bytes from 198.32.64.12#53(L.ROOT-SERVERS.NET) in 203 ms dig: Couldn't find server 'ns.uu.net' (h_errno=11001) XMail tries all the available DNS NS before giving up, so I doubt a single failure could have created the problem. - 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: 1.25-pre06 ...
On Tue, 17 Apr 2007, John Kielkopf wrote: I'm probably missing something here, but falling back to the A record after timeouts would seem to be the wrong course of action. Couldn't a temporary connectivity issue caused Xmail to incorrectly fall-back to an A record for a domain, and worse yet, cache that A record for later use? XMail does not cache A record attempts. Next one would still try to re-fetch MX records. - 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: 1.25-pre06 ...
Davide Libenzi wrote: On Tue, 17 Apr 2007, John Kielkopf wrote: I'm probably missing something here, but falling back to the A record after timeouts would seem to be the wrong course of action. Couldn't a temporary connectivity issue caused Xmail to incorrectly fall-back to an A record for a domain, and worse yet, cache that A record for later use? XMail does not cache A record attempts. Next one would still try to re-fetch MX records. Still, you would think a timeout on a MX record lookup (from every domain DNS server) should also result in a time-out when looking up an A record. If you can get an A record without a timeout, then you should be able to at least get a nodata response on MX lookup. Good that Xmail does not cache the A record, but falling back to an A record after timeout on MX lookup still seems like a bad idea. - 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.25-pre06 ...
Davide Libenzi wrote: On Tue, 17 Apr 2007, CLEMENT Francis wrote: Possible it's a dns server problem Who does xmail response on a timeout after dns query ? Who many retries = ? And final decision on dns timeout ? A record tries ? I ask this because, I noticed that dns timeouts are frequent with some french isp especially on udp (qos ? prioritization ?), and an immediate retry generally get the response. A timeout (inside the DNS retry policy rule) from every domain DNS server is treated as failure to get the MX, hence the A record is tried. - Davide I'm probably missing something here, but falling back to the A record after timeouts would seem to be the wrong course of action. Couldn't a temporary connectivity issue caused Xmail to incorrectly fall-back to an A record for a domain, and worse yet, cache that A record for later use? - John - 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.25-pre06 ...
Davide, I can see you are adamant that xmail did not use the www.optusnet.com.au for delivery and I agree with you, however, I see that the path followed to get the point of reporting www.optusnet.com.au is 1. decipher domain part of TO address (optusnet.com.au) 2. get NS records for optusnet.com.au 3. get MX records for optusnet.com.au 4. some error occurred, so get A record for optusnet.com.au. (what the error was is not important here) 5. get PTR record for the IP we are going to send to: 211.29.132.105 (The A record) 6. attempt to send email fail 7. send a bounce email to postmaster (and sender) reporting the name obtained from the PTR lookup. ^ This is what xmail has done forever, and is not a problem, as long as you know the name reported is the PTR, rather than the domain part of the TO address. I think it is just fine as it is. SO Getting back to the real issue at hand... Why would a VERY large ISP (optusnet.com.au) be broken. It certainly is not broken now when DIGs are done. The only difference is that one NS that wasn't responding - it now is. And you say that xmail tries all NS records until it gets valid results or all NS are exhausted, so one NS not responding should not be a problem. Unfortunately the reason I switched to SMARTDNSHOST years ago was due to the reliability of xmail's DNS lookup routines. I use 'named' as a caching DNS server and point xmail to it and have had very little problem caused by lookup failure since. Within one day of trying NO SMARTDNSHOST on 1.25pre06, I had undeliverable emails. I have since re-enabled SMARTDNSHOST and again I have no problems (the user has resent the emails successfully). Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, April 18, 2007 1:43 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Tue, 17 Apr 2007, Rob Arends wrote: And, BTW, www.optusnet.com.au is *NOT* the A record. If XMail would have tried the A record, you should have seen optusnet.com.au in there. I do (from previous post) optusnet.com.au.37147 IN A 211.29.132.105 But the rev dns is : C:\dig -x 211.29.132.105 ; DiG 9.2.3 -x 211.29.132.105 ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;105.132.29.211.in-addr.arpa. IN PTR ;; ANSWER SECTION: 105.132.29.211.in-addr.arpa. 66125 IN PTR www.optusnet.com.au. ^ XMail passes down the domain name, that'd been optusnet.com.au. There is no way www.optusnet.com.au could have been shawn in there is it wasn't coming from an MX response. - 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: 1.25-pre06 ...
On Wed, 18 Apr 2007, Rob Arends wrote: SO Getting back to the real issue at hand... Why would a VERY large ISP (optusnet.com.au) be broken. It certainly is not broken now when DIGs are done. The only difference is that one NS that wasn't responding - it now is. And you say that xmail tries all NS records until it gets valid results or all NS are exhausted, so one NS not responding should not be a problem. Unfortunately the reason I switched to SMARTDNSHOST years ago was due to the reliability of xmail's DNS lookup routines. I use 'named' as a caching DNS server and point xmail to it and have had very little problem caused by lookup failure since. Within one day of trying NO SMARTDNSHOST on 1.25pre06, I had undeliverable emails. I have since re-enabled SMARTDNSHOST and again I have no problems (the user has resent the emails successfully). I had no problems in sending to that domain, and in general I had no problems whatsoever so far with it. You didn't try to resend to that domain, did you? You probably hit a temporary network problem, you saw the message XMail generated, and you posted to the mailing list. Why it is more rare that you see this using a 'named' resolver? Because 'named' caches *everything*, so it is easier that temporary network problems end up being hidden by its caching. - 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: 1.25-pre06 ...
Oh, ok !! So you want me to try without smartdnshost ?? (This mail sent without smartdnshost!) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Monday, April 16, 2007 2:13 PM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Mon, 16 Apr 2007, Rob Arends wrote: Also, using smartdnshost (local named process) So basically you're still using 1.24 :) - 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: 1.25-pre06 ...
I using without smartdnshost and ssl here for 5 days, no know problems. Ana Paula On 4/16/07, Rob Arends [EMAIL PROTECTED] wrote: Oh, ok !! So you want me to try without smartdnshost ?? (This mail sent without smartdnshost!) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Monday, April 16, 2007 2:13 PM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Mon, 16 Apr 2007, Rob Arends wrote: Also, using smartdnshost (local named process) So basically you're still using 1.24 :) - 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: 1.25-pre06 ...
I've created Debian packages for -pre06. If you feel adventurous add this to you /etc/apt/sources.list: deb http://arcadia.timisoara.roedu.net/xmail ./ deb-src http://arcadia.timisoara.roedu.net/xmail ./ then run apt-get update apt-get install xmail Send bugreports to me, and if everything goes well after 1.25 is launched I'll upload it to unstable too. - Radu - 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.25-pre06 ...
On Mon, 16 Apr 2007, Radu Spineanu wrote: I've created Debian packages for -pre06. If you feel adventurous add this to you /etc/apt/sources.list: deb http://arcadia.timisoara.roedu.net/xmail ./ deb-src http://arcadia.timisoara.roedu.net/xmail ./ then run apt-get update apt-get install xmail Send bugreports to me, and if everything goes well after 1.25 is launched I'll upload it to unstable too. Thank you Radu. Didn't we have a discussion open about things to fix in XMail to play nicer with Debian? - 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: 1.25-pre06 ...
Hi Davide, Thank you Radu. Didn't we have a discussion open about things to fix in XMail to play nicer with Debian? I could have misplaced those emails, sorry I've had a lot on my mind this last couple of days/weeks/months. The major issue is a LSB incompatibility because the -bs function is not implemented, you suggested a good fix by providing a wrapper but I didn't have time to write it yet. Also there is the testing on the k*bsd architectures, I lost my access to a machine where I did this work, so I will ask the porters to look over it. The SSL certificates are created in the Debian postinst script during upgrade. Was there anything else? - Radu - 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.25-pre06 ...
Davide, I have had to turn on smartdnshost again. After having an error-free run for quite a while, this morning I see errors. Investigation shows. Issue 1: - - Partial Bounce email content: (I've swapped @ for *) ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] ErrCode = -217 ErrString = Error connecting to remote address - DIG results Notice that the MX results are ignored and sending to the A result is attempted. C:\dig optusnet.com.au mx ; DiG 9.2.3 optusnet.com.au mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;optusnet.com.au. IN MX ;; ANSWER SECTION: optusnet.com.au.86400 IN MX 50 mail.optusnet.com.au. ;; AUTHORITY SECTION: optusnet.com.au.37130 IN NS ns2.optusnet.com.au. optusnet.com.au.37130 IN NS ns1.optusnet.com.au. ;; ADDITIONAL SECTION: mail.optusnet.com.au. 86400 IN A 211.29.132.250 ns1.optusnet.com.au.37130 IN A 203.2.75.2 ns2.optusnet.com.au.37130 IN A 203.2.75.12 ;; Query time: 46 msec ;; SERVER: 10.90.10.151#53(ns1) ;; WHEN: Tue Apr 17 08:37:34 2007 ;; MSG SIZE rcvd: 138 C:\dig optusnet.com.au a ; DiG 9.2.3 optusnet.com.au a ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;optusnet.com.au. IN A ;; ANSWER SECTION: optusnet.com.au.37147 IN A 211.29.132.105 ;; AUTHORITY SECTION: optusnet.com.au.37099 IN NS ns1.optusnet.com.au. optusnet.com.au.37099 IN NS ns2.optusnet.com.au. ;; ADDITIONAL SECTION: ns1.optusnet.com.au.37099 IN A 203.2.75.2 ns2.optusnet.com.au.37099 IN A 203.2.75.12 ;; Query time: 15 msec ;; SERVER: 10.90.10.151#53(ns1) ;; WHEN: Tue Apr 17 08:38:04 2007 ;; MSG SIZE rcvd: 117 C:\ - Issue 2: - - Partial Bounce email content: (I've swapped @ for *) ID:S347AD Mail From: stkilda*nzn.com.au Rcpt To: sweetheartsmusic*gmail.com Server:od-in-f83.google.com [64.233.161.83] ErrCode = -217 ErrString = Error connecting to remote address - Looking at the DIG for gmail.com, I get the same thing - A record was used for SMTP. - It seems that in your DNS rewrite; now, the A record is favoured if it exists. Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Arends Sent: Monday, April 16, 2007 6:45 PM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... Oh, ok !! So you want me to try without smartdnshost ?? (This mail sent without smartdnshost!) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Monday, April 16, 2007 2:13 PM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Mon, 16 Apr 2007, Rob Arends wrote: Also, using smartdnshost (local named process) So basically you're still using 1.24 :) - 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] Re: 1.25-pre06 ...
On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I have had to turn on smartdnshost again. After having an error-free run for quite a while, this morning I see errors. Investigation shows. Issue 1: - - Partial Bounce email content: (I've swapped @ for *) ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] ErrCode = -217 ErrString = Error connecting to remote address No problems here (trying to send to a bogus address in that domain): [00] XMail bounce: [EMAIL PROTECTED];Error=[553 5.3.0[EMAIL PROTECTED]... No such user] [01] Error sending message [1176767187543.1082977200.2724.x35.xmailserver.org] from [xmailserver.org]. ID:S2233ED Mail From: [EMAIL PROTECTED] Rcpt To: [EMAIL PROTECTED] Server:mail.optusnet.com.au [211.29.132.250] [02] The reason of the delivery failure was: 553 5.3.0 [EMAIL PROTECTED]... No such user - 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: 1.25-pre06 ...
On Mon, 16 Apr 2007, Davide Libenzi wrote: On Tue, 17 Apr 2007, Rob Arends wrote: Davide, I have had to turn on smartdnshost again. After having an error-free run for quite a while, this morning I see errors. Investigation shows. Issue 1: - - Partial Bounce email content: (I've swapped @ for *) ID:S347B1 Mail From: stkilda*nzn.com.au Rcpt To: sjellis*optusnet.com.au Server:www.optusnet.com.au [211.29.132.105] ErrCode = -217 ErrString = Error connecting to remote address And, BTW, www.optusnet.com.au is *NOT* the A record. If XMail would have tried the A record, you should have seen optusnet.com.au in there. - 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: 1.25-pre06 ...
On Mon, 16 Apr 2007, Radu Spineanu wrote: Hi Davide, Thank you Radu. Didn't we have a discussion open about things to fix in XMail to play nicer with Debian? I could have misplaced those emails, sorry I've had a lot on my mind this last couple of days/weeks/months. The major issue is a LSB incompatibility because the -bs function is not implemented, you suggested a good fix by providing a wrapper but I didn't have time to write it yet. Also there is the testing on the k*bsd architectures, I lost my access to a machine where I did this work, so I will ask the porters to look over it. The SSL certificates are created in the Debian postinst script during upgrade. Was there anything else? Oh man, you ask me? :) - 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: 1.25-pre06 ...
Davide, running on Win2ksp4 here for 3 days - seems to be ok. (No SSL) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Thursday, April 12, 2007 10:18 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Wed, 11 Apr 2007, Ana Paula Fernandes wrote: Working fine here, for about 4 hours. Thanks for testing! I forgot to mention that I added a column to the SMAIL log. That's the end response to the final DATA command (w/out the SMTP code). This usually returns the remote server message ID, that can be used to be reported to the remote MTA admin, in case shit^Wproblems happens. - 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: 1.25-pre06 ...
Also, using smartdnshost (local named process) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Arends Sent: Monday, April 16, 2007 11:09 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... Davide, running on Win2ksp4 here for 3 days - seems to be ok. (No SSL) Rob :-) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Thursday, April 12, 2007 10:18 AM To: xmail@xmailserver.org Subject: [xmail] Re: 1.25-pre06 ... On Wed, 11 Apr 2007, Ana Paula Fernandes wrote: Working fine here, for about 4 hours. Thanks for testing! I forgot to mention that I added a column to the SMAIL log. That's the end response to the final DATA command (w/out the SMTP code). This usually returns the remote server message ID, that can be used to be reported to the remote MTA admin, in case shit^Wproblems happens. - 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] Re: 1.25-pre06 ...
On Mon, 16 Apr 2007, Rob Arends wrote: Also, using smartdnshost (local named process) So basically you're still using 1.24 :) - 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: 1.25-pre06 ...
Working fine here, for about 4 hours. Ana Paula On 4/11/07, Davide Libenzi davidel@xmailserver.org wrote: This one makes the new DNS code to be quiter and bounce immediately in case of misconfigured DNS: http://www.xmailserver.org/xmail-1.25-pre06.tar.gz http://www.xmailserver.org/xmail-1.25-pre06.win32bin.zip - 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: 1.25-pre06 ...
On Wed, 11 Apr 2007, Ana Paula Fernandes wrote: Working fine here, for about 4 hours. Thanks for testing! I forgot to mention that I added a column to the SMAIL log. That's the end response to the final DATA command (w/out the SMTP code). This usually returns the remote server message ID, that can be used to be reported to the remote MTA admin, in case shit^Wproblems happens. - 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]
