On 29 Aug 2020, at 07:17, Viktor Dukhovni wrote:
> On Sat, Aug 29, 2020 at 06:16:27AM -0600, @lbutlr wrote:
>
>> After updating Bind and dovecot and rebooting the server, I am getting these
>> errors on almost every incoming mail.
>> Bind is running, and I can manually lookup the domains and dig
@lbutlr wrote:
> Bind is running, and I can manually lookup the domains and dig -x
> the IPs, so I don’t think bind is the issue?
Although dig and drill are good for tracing DNS queries the better
tool for tracing system default lookups is 'getent'. It will perform
a lookup using the same libc li
On Sat, Aug 29, 2020 at 06:16:27AM -0600, @lbutlr wrote:
> After updating Bind and dovecot and rebooting the server, I am getting these
> errors on almost every incoming mail.
> Bind is running, and I can manually lookup the domains and dig -x the IPs, so
> I don’t think bind is the issue?
Red
@lbutlr:
> Aug 29 01:30:13 mail.covisp.net postfix/smtpd[40178] 4Bdp5d3gF5z36j0y:
> reject: RCPT from mx2.freebsd.org[96.47.72.81]: 451 4.3.0
> : Temporary lookup failure;
> from= to=
> proto=ESMTP helo=
Your Postfix resolv.conf file may point to the wrong IP address.
Wietse
@lbutlr skrev den 2020-08-29 14:16:
After updating Bind and dovecot and rebooting the server, I am getting
these errors on almost every incoming mail.
try reboot ?
Current load os 0.29 instead of 12.9 and climbing, sp I don’t think
it’s related.
is
dig +trace google.com
working ?
is
pin
Thanks, it was solved as my previous answer.
2013/11/11 Wietse Venema
> Merve Temizer:
> > If i do not need why i am getting "Temporary lookup failure" for every
> > attempt while i was sending mail through telnet?
>
> Wietse
> > The reason for the failure is in the MAILLOG file. Postfix does
Merve Temizer:
> If i do not need why i am getting "Temporary lookup failure" for every
> attempt while i was sending mail through telnet?
Wietse
> The reason for the failure is in the MAILLOG file. Postfix does
> not provide configuration error details to SMTP clients.
Merve Temizer:
> i change
Merve Temizer:
> If i do not need why i am getting "Temporary lookup failure" for every
> attempt while i was sending mail through telnet?
The reason for the failure is in the MAILLOG file.
Postfix does not provide configuration error details to SMTP clients.
Wietse
Zitat von Viktor Dukhovni :
On Wed, Mar 06, 2013 at 06:13:05PM +, lst_ho...@kwsoft.de wrote:
Zitat von Wietse Venema :
>Postfix reports that the LDAP client library could not connect to
>any of the LDAP servers. Don't shoot the messenger.
>
>Wietse
Would the "domain" parameter in th
On Wed, Mar 06, 2013 at 06:13:05PM +, lst_ho...@kwsoft.de wrote:
> Zitat von Wietse Venema :
>
> >Postfix reports that the LDAP client library could not connect to
> >any of the LDAP servers. Don't shoot the messenger.
> >
> > Wietse
>
> Would the "domain" parameter in the LDAP config pr
Zitat von Wietse Venema :
Alvaro Marin:
For a moment, one ActiveDirectory server for some domains was down, so
I've seen in logs:
warning: dict_ldap_connect: Unable to bind to server ldap://IP1
ldap://IP2 as cn=x,ou=x,dc=x,dc=x: -1 (Can't contact LDAP server)
...
Is anyway to configure Post
Alvaro Marin:
> For a moment, one ActiveDirectory server for some domains was down, so
> I've seen in logs:
>
> warning: dict_ldap_connect: Unable to bind to server ldap://IP1
> ldap://IP2 as cn=x,ou=x,dc=x,dc=x: -1 (Can't contact LDAP server)
...
> Is anyway to configure Postfix to avoid this s
Am 06.03.2013 17:17, schrieb Alvaro Marin:
> Hello,
>
> I've several Postfix servers configured to relay email for users/domains.
> We've different LDAP servers to query and a cdb file; something like this:
>
> relay_recipient_maps = ldap:/etc/postfix/ldap_users.cf,
> ldap:/etc/postfix/actived
wner-postfix-us...@postfix.org] On Behalf Of Victor Duchovni
Sent: 29 May 2009 17:17
To: postfix-users@postfix.org
Subject: Re: temporary lookup failure
On Sat, May 30, 2009 at 02:09:35AM +1000, Barney Desmond wrote:
> 2009/5/29 Jon Harris :
> > However, I have tried putting "proxy:"
On Sat, May 30, 2009 at 02:09:35AM +1000, Barney Desmond wrote:
> 2009/5/29 Jon Harris :
> > However, I have tried putting "proxy:" in front of my mysql maps and it
> > stopped it being able to receive email. Presumably, I need to enable
> > proxymap to get proxy maps to work. This is something I
2009/5/29 Jon Harris :
> However, I have tried putting "proxy:" in front of my mysql maps and it
> stopped it being able to receive email. Presumably, I need to enable
> proxymap to get proxy maps to work. This is something I don't know how
> to do.
Error logs?
My suspicion is that the proxy map
Jon Harris wrote:
> Hi Brian
>
> Everything you said makes a great deal of sense - thanks very much. I
> have changed the RBL settings, as you advised.
>
> Yes, the load has gone up considerably, particularly, we are seeing a
> massive rise of spam traffic on this box (mainly on one or two of the
>
Hi Brian
Everything you said makes a great deal of sense - thanks very much. I
have changed the RBL settings, as you advised.
Yes, the load has gone up considerably, particularly, we are seeing a
massive rise of spam traffic on this box (mainly on one or two of the
domains 30 domains its responsi
Jon Harris wrote:
> Hi List
>
> A few of our clients use our postfix server for relaying. Generally, its
> working really well, but several users are reporting regular "451
> Temporary Lookup Failure" bounce errors. This is them sending "outgoing"
> (ie non-local domains) and domains that Postfix s
Hungry Snail:
>
> Hi guys,
>
> I have just started recieving emails from postfix telling me that there is a
> Temporary lookup failure.
>
>
> *
> Subject: Postfix SMTP server: errors from
> adsl190-28-1-167.epm.net.co[190.28.1.167]
> Out: 220 mailserver.mydomain.tld ESMTP Postfix (Debian
20 matches
Mail list logo
