On 7/18/2012 9:51 AM, Wietse Venema wrote:
Darren Pilgrim:
On 2012-07-18 03:08, Wietse Venema wrote:
Darren Pilgrim:
inet_protocols = ipv4
Well there is your problem.
No, that was postconf -n from the working config (which is ipv4 only).
I offered to help, and you sent the configuration
Darren Pilgrim:
> On 2012-07-18 03:08, Wietse Venema wrote:
> > Darren Pilgrim:
> >> inet_protocols = ipv4
> >
> > Well there is your problem.
>
> No, that was postconf -n from the working config (which is ipv4 only).
I offered to help, and you sent the configuration of a different machine?
I wi
On 2012-07-18 03:08, Wietse Venema wrote:
Darren Pilgrim:
inet_protocols = ipv4
Well there is your problem.
No, that was postconf -n from the working config (which is ipv4 only).
Per the first email, I set inet protocols = ipv4, ipv6 when I added the
IPv6 address.
Darren Pilgrim:
> inet_protocols = ipv4
Well there is your problem.
Wietse
On 2012-07-17 03:58, Wietse Venema wrote:
Darren Pilgrim:
I have Postfix v2.9.1 installed from ports. My OS is:
# uname -a
FreeBSD catnip.pilgrimaccounting.com 8.3-RELEASE-p3 FreeBSD
8.3-RELEASE-p3 #0: Thu Jun 14 13:08:22 PDT 2012
r...@catnip.pilgrimaccounting.com:/usr/obj/usr/src/sys/CATNIP a
Darren Pilgrim:
> I have Postfix v2.9.1 installed from ports. My OS is:
> # uname -a
> FreeBSD catnip.pilgrimaccounting.com 8.3-RELEASE-p3 FreeBSD
> 8.3-RELEASE-p3 #0: Thu Jun 14 13:08:22 PDT 2012
> r...@catnip.pilgrimaccounting.com:/usr/obj/usr/src/sys/CATNIP amd64
>
> When I enable IPv6 with
I have Postfix v2.9.1 installed from ports. My OS is:
# uname -a
FreeBSD catnip.pilgrimaccounting.com 8.3-RELEASE-p3 FreeBSD
8.3-RELEASE-p3 #0: Thu Jun 14 13:08:22 PDT 2012
r...@catnip.pilgrimaccounting.com:/usr/obj/usr/src/sys/CATNIP amd64
When I enable IPv6 with the following in main.cf:
ghe wrote, at 04/10/2009 02:54 PM:
> Oh, dear! I'm not sure what, if anything, I can do about this, but
> thanks to you all for the response(s). Maybe a non-caching name server
> might help.
You've only indicated that an authenticated client's IP address does not
reliably provide a reverse lookup
ghe wrote:
Oh, dear! I'm not sure what, if anything, I can do about this, but
thanks to you all for the response(s). Maybe a non-caching name server
might help.
I don't think there's anything you can do about it. The settings for how
long a cached record stays alive and when an update is atte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J.P. Trosclair wrote:
> SBC Global's ns1.swbell.net does answer with the appropriate IP address,
> but neither our companies name servers or my local dns on my home
> network can resolve adsl-99-29-103-142.dsl.hstntx.sbcglobal.net. I
> restarted named
Yes it does:
# host adsl-99-29-103-142.dsl.hstntx.sbcglobal.net
adsl-99-29-103-142.dsl.hstntx.sbcglobal.net has address 99.29.103.142
SBC Global's ns1.swbell.net does answer with the appropriate IP address,
but neither our companies name servers or my local dns on my home
network can resolve
ghe:
> Wietse Venema wrote:
>
> >>> # host 99.29.103.142
> >>> 142.103.29.99.in-addr.arpa domain name pointer
> >>> adsl-99-29-103-142.dsl.hstntx.sbcglobal.net.
> >> As far as I know, this is the only Blackberry using this mail server.
> >> Other hosts/domains/devices don't have this problem. Can
On Fri, Apr 10, 2009 at 11:41:51AM -0600, ghe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wietse Venema wrote:
>
> >>> # host 99.29.103.142
> >>> 142.103.29.99.in-addr.arpa domain name pointer
> >>> adsl-99-29-103-142.dsl.hstntx.sbcglobal.net.
> >> As far as I know, this is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wietse Venema wrote:
>>> # host 99.29.103.142
>>> 142.103.29.99.in-addr.arpa domain name pointer
>>> adsl-99-29-103-142.dsl.hstntx.sbcglobal.net.
>> As far as I know, this is the only Blackberry using this mail server.
>> Other hosts/domains/devices
ghe:
> I'm getting log entries like this:
>
> > Apr 2 12:55:53 ralph postfix/smtpd[15788]: 779DFC6D76:
> > client=unknown[99.29.103.142], sasl_method=LOGIN, sasl_username=joelqw
>
> This is one of my users' Blackberry. Notice that Postfix (or maybe it's
> Dovecot, in the sasl verification) is s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting log entries like this:
> Apr 2 12:55:53 ralph postfix/smtpd[15788]: 779DFC6D76:
> client=unknown[99.29.103.142], sasl_method=LOGIN, sasl_username=joelqw
This is one of my users' Blackberry. Notice that Postfix (or maybe it's
Dovecot, in
16 matches
Mail list logo
