Glen B:
> directly. So, can I request a raw message dump tool that simply outputs
> the headers and data section? I'd be fine with a raw envelope used in
> SMTP DATA transactions. If this is possible with an existing tool then
> I'd be fine with that also. As it stands I can't rely on postcat ou
On 10-Mar-2009, at 20:43, Glen B wrote:
Why no TZ was set in the chroot, I'm clueless
Because the chroot jail doesn't have access to read the TMZ information?
--
I draw the line at 7 unreturned phone calls.
Glen B wrote:
Wietse Venema wrote:
Ben Winslow:
FWIW, my test system uses the system-wide timezone (US/Central)
in the output from mailq and the timezone from $TZ (US/Eastern)
for the output from postcat. This is, IMO, the correct behavior.
I hadn't thought of that (system versus user
Wietse Venema wrote:
Ben Winslow:
FWIW, my test system uses the system-wide timezone (US/Central)
in the output from mailq and the timezone from $TZ (US/Eastern)
for the output from postcat. This is, IMO, the correct behavior.
I hadn't thought of that (system versus user time zone). I
Ben Winslow:
> FWIW, my test system uses the system-wide timezone (US/Central)
> in the output from mailq and the timezone from $TZ (US/Eastern)
> for the output from postcat. This is, IMO, the correct behavior.
I hadn't thought of that (system versus user time zone). It could
explain the origina
On Tue, 10 Mar 2009 10:36:25 -0400 (EDT)
wie...@porcupine.org (Wietse Venema) wrote:
> This may very well be a Debian bug where they run daemons chrooted
> but don't provide the correct timezone file inside the jail.
Just for reference, the postfix 2.5.5-1.1 package in Debian -- if any
services i
Wietse:
>Type the following commands, and report the output:
>
>$ date
>$ mailq | grep DBBAD4A340AD
>$ date
>
>This may very well be a Debian bug where they run daemons chrooted
>but don't provide the correct timezone file inside the jail.
Glen B:
> box:/# date
> Tue Mar 10 12:38:51 EDT 2009
> box
On Tue, Mar 10, 2009 at 10:20:15AM -0700, Glen B wrote:
> > box:/# mailq | grep DBBAD4A340AD
> > postqueue: warning: Mail system is down -- accessing queue
> > directly
> > DBBAD4A340AD? 827 Mon Mar? 9 10:29:27? root
> > box:/# date
> > Tue Mar 10 12:39:03 EDT 2009
> > box:/#
Perhaps the "pos
--- On Tue, 3/10/09, Glen B wrote:
> From: Glen B
> Subject: Re: v2.5.5 showq and postcat date/time stamp discrepancy
> To: "Wietse Venema"
> Date: Tuesday, March 10, 2009, 1:16 PM
> >
> >--- On Tue, 3/10/09, Wietse Venema
> wrote:
> >
> >From
Glen B:
> ?
> ? I'm running the commands from a SSH shell logged in as root. What do you
> mean by setuid wrapper?
> ?
Type the following commands, and report the output:
$ date
$ mailq | grep DBBAD4A340AD
$ date
This may very well be a Debian bug where they run daemons chrooted
but don't provi
I'm running the commands from a SSH shell logged in as root. What do you mean
by setuid wrapper?
GlenB
--- On Tue, 3/10/09, Victor Duchovni wrote:
From: Victor Duchovni
Subject: Re: v2.5.5 showq and postcat date/time stamp discrepancy
To: postfix-users@postfix.org
Date: Tuesday,
On Tue, Mar 10, 2009 at 01:01:37AM -0400, Glen B wrote:
>
> Hi,
>
> Postfix 2.5.5 on Debian
>
> I've just noticed a discrepancy between showq (postqueue -p) and postcat.
> I've looked through the code, played with the conversion code in postcat
> and I honestly can not figure out what's going wr
Hi,
Postfix 2.5.5 on Debian
I've just noticed a discrepancy between showq (postqueue -p) and
postcat. I've looked through the code, played with the conversion code
in postcat and I honestly can not figure out what's going wrong:
-Queue ID- --Size-- Arrival Time -Sender/Recipient
13 matches
Mail list logo
