Do you mind opening a ticket ?

I was talking to eric@ and asking him if he had a chance to look at this
and he had missed this :-/


On Sun, Nov 23, 2014 at 03:19:08AM +0600, Denis Fateyev wrote:
> Hello all,
> 
> It comes non-bootstrapped, otherwise the build is fine. Of course, it's
> actually needed to provide it bootstrapped.
> 
> The real problem here is that resolving isn't working properly which I
> suspect probably is a "libasr" issue.
> When I'm trying to send a message I get this:
> 
> --------
> Nov 23 02:56:44 build1-amd64 smtpd[15997]: smtp-in: New session
> e704b8d725a197bd from host build1-amd64.svc.denode.net [local]
> Nov 23 02:56:45 build1-amd64 smtpd[15997]: smtp-in: Accepted message
> 9cfb3cd7 on session e704b8d725a197bd: from=<[email protected]>,
> to=<[email protected]>, size=346, ndest=1, proto=ESMTP
> Nov 23 02:56:45 build1-amd64 smtpd[15997]: smtp-in: Closing session
> e704b8d725a197bd
> Nov 23 02:56:45 build1-amd64 smtpd[15997]: smtp-out: Failed to resolve MX
> for [relay:fateyev.com]: No MX found for domain
> Nov 23 02:56:45 build1-amd64 smtpd[15997]: relay: TempFail for
> 9cfb3cd7a581004f: session=0000000000000000, from=<
> [email protected]>, to=<[email protected]>, rcpt=<->,
> source=-, relay=fateyev.com, delay=1s, stat=No MX found for domain
> Nov 23 02:57:14 build1-amd64 smtpd[15997]: smtp-in: New session
> e704b8da0f1628bb from host build1-amd64.svc.denode.net [local]
> Nov 23 02:57:14 build1-amd64 smtpd[15997]: smtp-in: Accepted message
> 5c013644 on session e704b8da0f1628bb: from=<[email protected]>,
> to=<[email protected]>, size=344, ndest=1, proto=ESMTP
> Nov 23 02:57:14 build1-amd64 smtpd[15997]: smtp-in: Closing session
> e704b8da0f1628bb
> Nov 23 02:57:14 build1-amd64 smtpd[15997]: smtp-out: Failed to resolve MX
> for [relay:poolp.org]: No MX found for domain
> Nov 23 02:57:14 build1-amd64 smtpd[15997]: relay: TempFail for
> 5c013644233515d9: session=0000000000000000, from=<
> [email protected]>, to=<[email protected]>, rcpt=<->,
> source=-, relay=poolp.org, delay=0s, stat=No MX found for domain
> Nov 23 03:03:24 build1-amd64 smtpd[15997]: smtp-out: Failed to resolve MX
> for [relay:fateyev.com]: No MX found for domain
> Nov 23 03:03:24 build1-amd64 smtpd[15997]: relay: TempFail for
> 9cfb3cd7a581004f: session=0000000000000000, from=<
> [email protected]>, to=<[email protected]>, rcpt=<->,
> source=-, relay=fateyev.com, delay=6m40s, stat=No MX found for domain
> --------
> 
> DNS resolving and netwok connection on the same machines are fine:
> 
> [root@build1-amd64 x86_64]# nslookup
> > set q=mx
> > poolp.org
> Server:        192.168.0.1
> Address:    192.168.0.1#53
> 
> Non-authoritative answer:
> poolp.org    mail exchanger = 50 mx2.poolp.org.
> poolp.org    mail exchanger = 200 poolp.no-ip.org.
> poolp.org    mail exchanger = 0 mx1.poolp.org.
> 
> > fateyev.com
> Server:        192.168.0.1
> Address:    192.168.0.1#53
> 
> Non-authoritative answer:
> fateyev.com    mail exchanger = 5 alt2.aspmx.l.google.com.
> fateyev.com    mail exchanger = 10 aspmx2.googlemail.com.
> fateyev.com    mail exchanger = 10 aspmx3.googlemail.com.
> fateyev.com    mail exchanger = 10 aspmx4.googlemail.com.
> fateyev.com    mail exchanger = 10 aspmx5.googlemail.com.
> fateyev.com    mail exchanger = 1 aspmx.l.google.com.
> fateyev.com    mail exchanger = 5 alt1.aspmx.l.google.com.
> 
> 
> Tested under RHEL6 and Fedora 20 with the same results.
> Software versions: libasr-201411201818, opensmtpd-5.4.4p1-rc1.
> 
> -- 
> wbr, Denis.
> 
> On Sat, Nov 22, 2014 at 11:15 PM, Gilles Chehade <[email protected]> wrote:
> 
> > On Fri, Nov 21, 2014 at 10:34:51AM +0100, V??clav Stracho?? wrote:
> > > Hi,
> > >
> > > I've tried to install new portable OpenSMTPD version and it looks like
> > > install.sh script is missing:
> > >
> >
> 
> [ -- skipped -- ]
> 
> strange, we'll look into it and get back shortly
> >
> > --
> > Gilles Chehade
> >
> > https://www.poolp.org                                          @poolpOrg
> >

-- 
Gilles Chehade

https://www.poolp.org                                          @poolpOrg

-- 
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]

Reply via email to