[pfx] Re: status=deferred (bounce or trace service failure)

2024-04-22 Thread Wietse Venema via Postfix-users
Viktor Dukhovni via Postfix-users: > On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > > > Recently i'm seeing a few messages deferred with status=deferred > > (bounce or trace service failure) > > > > instead of status=deferred (host .

[pfx] Re: status=deferred (bounce or trace service failure)

2024-04-22 Thread 785 243 via Postfix-users
1:01AM -0400, 785 243 via Postfix-users wrote: > > > Recently i'm seeing a few messages deferred with status=deferred > > (bounce or trace service failure) > > > > instead of status=deferred (host .. said: 450 ...) > > > > from the logs: > > >

[pfx] Re: status=deferred (bounce or trace service failure)

2024-04-22 Thread Viktor Dukhovni via Postfix-users
On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > Recently i'm seeing a few messages deferred with status=deferred > (bounce or trace service failure) > > instead of status=deferred (host .. said: 450 ...) > > from the logs: > > postf

[pfx] status=deferred (bounce or trace service failure)

2024-04-21 Thread 785 243 via Postfix-users
Recently i'm seeing a few messages deferred with status=deferred (bounce or trace service failure) instead of status=deferred (host .. said: 450 ...) from the logs: postfix/smtp[272605]: warning: unexpected protocol delivery_request_protocol from private/bounce socket (expected

trace service failure

2011-06-18 Thread Vince Sabio
: 587564A7357: trace service failure Jun 18 00:24:16 ares postfix/local[1935]: 587564A7357: to=localu...@ares.hva-va.org, relay=local, delay=116238, delays=116238/0.03/0/0.05, dsn=4.3.0, status=deferred (587564A7357: trace service failed) That's all there is (every 70 minutes). The e-mail messages

Re: trace service failure

2011-06-18 Thread Jeroen Geilman
:24:16 ares postfix/qmgr[874]: 587564A7357: from=localu...@crs.loc.gov, size=4031, nrcpt=1 (queue active) Jun 18 00:24:16 ares postfix/local[1935]: warning: 587564A7357: trace service failure Oops. Of course, this is documented; http://www.postfix.org/trace.8.html says: *DESCRIPTION

Re: trace service failure

2011-06-18 Thread Wietse Venema
Vince Sabio: Jun 18 00:24:16 ares postfix/qmgr[874]: 587564A7357: from=localu...@crs.loc.gov, size=4031, nrcpt=1 (queue active) Jun 18 00:24:16 ares postfix/local[1935]: warning: 587564A7357: trace service failure Jun 18 00:24:16 ares postfix/local[1935]: 587564A7357: to=localu

Re: trace service failure

2011-06-18 Thread Vince Sabio
** At 08:23 -0400 on 06/18/2011, Wietse Venema wrote: Vince Sabio: Jun 18 00:24:16 ares postfix/qmgr[874]: 587564A7357: from=localu...@crs.loc.gov, size=4031, nrcpt=1 (queue active) Jun 18 00:24:16 ares postfix/local[1935]: warning: 587564A7357: trace service failure Jun 18 00:24:16 ares

Re: trace service failure

2011-06-18 Thread Vince Sabio
** At 13:33 +0200 on 06/18/2011, Jeroen Geilman wrote: On 06/18/2011 10:57 AM, Vince Sabio wrote: I am running a list server that uses Postfix 2.0.18 (yes, it's a little bit creaky) as its MTA. On one of the lists, users are complaining that they are receiving repeats of one specific message

Re: trace service failure

2011-06-18 Thread Noel Jones
On 6/18/2011 11:36 AM, Vince Sabio wrote: ** At 13:33 +0200 on 06/18/2011, Jeroen Geilman wrote: Just locate the offending queue file and kill it. Yep -- that seems to have worked. There were two queue files, located in ~queue/defer/ and ~queue/deferred/; killed them both, and the problem

Re: trace service failure

2011-06-18 Thread Jerry
On Sat, 18 Jun 2011 12:37:44 -0400 Vince Sabio vi...@vjs.org articulated: So, now that I've apparently screwed the pooch, what is the recommended upgrade path to the most recent full release? FYI, this is on FreeBSD-5.1-RELEASE. (Yeah, I'm not really good about upgrades. I kinda wait until