When all deliveries to a site fail (a colhort of delivery agent
processes reports the destination is unavailable) the Postfix
scheduler puts the destination on a temporary 'dead destination'
list, to avoid spending resources on that destination.
Of course this design is not optimized for bursts
for those 5 minutes, Postfix is not even
trying the lookup any more. After the 5 minutes are up, new messages routing
to cluster9out.us.messagelabs.com are delivered without being deferred and the
queued messages begin to go out.
Testing shows that the DNS issue is very short term, lasting for 1
On Wed, Oct 19, 2022 at 4:12 PM Eric Wilkison wrote:
Are there configuration options that will
> a) adjust the number of DNS failures before postfix starts deferring the
> messages
> b) adjust the timeout before postfix stops queueing messages
Take a look at minimal_backoff_time and
the lookup any more. After the 5 minutes are up, new messages routing
to cluster9out.us.messagelabs.com are delivered without being deferred and the
queued messages begin to go out.
Testing shows that the DNS issue is very short term, lasting for 1 second or
so. However the pool of servers can
Thanks all.. gives me some direction to keep digging.
-Original Message-
From: owner-postfix-us...@postfix.org On
Behalf Of Viktor Dukhovni
Sent: Monday, September 5, 2022 9:36 AM
To: postfix-users@postfix.org
Subject: Re: Odd DNS issue requiring reboot.
On Sun, Sep 04, 2022 at 10:31
On Mon, Sep 05, 2022 at 11:40:17AM -0400, Curtis Maurand wrote:
> Are you sure it's not systemd-resolvd. It will happily override your
> resolver settings if it doesn't like your resolver. I've found that in
> my setups, to install my own resolver (usually pdns-recursor) and
> disable
On 9/5/22 11:23, Wietse Venema wrote:
Viktor Dukhovni:
Perhaps your resolver settings in the chroot jail become stale, and
are fixed when the "init script" resyncs the chroot with the /etc.
You might try running without chroot.
To turn off chroot for all Postfix daemons, update master.cf:
Viktor Dukhovni:
> Perhaps your resolver settings in the chroot jail become stale, and
> are fixed when the "init script" resyncs the chroot with the /etc.
> You might try running without chroot.
To turn off chroot for all Postfix daemons, update master.cf:
postconf -F "*/*/chroot = n"
postfix
On Sun, Sep 04, 2022 at 10:31:06PM -0400, Dave Lewis - Mailinglist wrote:
> So what seems to be happening Is that if something causes a dns issue
> postfix stops sending mail, and outgoing mail queues with things like this.
>
> (Host or domain name not found. Name service error for na
If it requires a REBOOT, then it is not a POSTFIX problem.
Wietse
to be happening Is that if something causes a dns issue
postfix stops sending mail, and outgoing mail queues with things like this.
(Host or domain name not found. Name service error for name=gmail.com
type=MX: Host not found, try again)
Also incoming mail is also affected, but not completely
You need to look in your logs.
https://www.postfix.org/DEBUG_README.html#logging
Wietse
Hi,
There is a postfix server (v3.4.13) with a multi instance (master.cf):
#servicetype private unpriv chroot wakeup maxproc command
127.0.0.1:30004 inet n- n - - smtpd
The master instance can send email to anywhere on the internet but the
multi
I'm seeing a DNS problem I cannot fathom:
# host 65.171.152.29
Host 29.152.171.65.in-addr.arpa not found: 2(SERVFAIL)
Hm. So who's authoritative?
# host -t ns 171.65.in-addr.arpa
171.65.in-addr.arpa name server ns1-auth.sprintlink.net.
171.65.in-addr.arpa name server ns3-auth.sprintlink.net.
On 29 Nov 2012, at 10:49, Ralf Hildebrandt r...@sys4.de wrote:
I'm seeing a DNS problem I cannot fathom:
# host 65.171.152.29
Well, there's part of your problem right there. Never, ever use host or
nslookup to query the DNS. Use dig. [Or drill if you're into debugging DNSSEC.]
Accept no
I've found that installing a caching DNS service on each STMP server
greatly reduces these delays.
On Mon, May 18, 2009 at 9:42 AM, Felix Nielsen felix.niel...@gmail.com wrote:
Hi
Is it normal that when connection to the SMTP engine is performed it
takes 4-6 sec. before greeting is presented?
Hi
Is it normal that when connection to the SMTP engine is performed it
takes 4-6 sec. before greeting is presented?
I suspect it is doing some DNS lookup on the client? - can it be
disabled for IPs?
Thanks
Felix
17 matches
Mail list logo
