Loading ...
Sorry, an error occurred while loading the content.
 

Re: update: 1 mail stoped by 1 user. Now it is 2 users and I noticed something.

Expand Messages
  • Josh Cason
    The postcat -q -eh command does not work. It does not like the -e??? What do I need to do? Thanks, Josh ... From: Viktor Dukhovni
    Message 1 of 6 , Sep 23, 2013
      The postcat -q -eh command does not work. It does not like the -e??? What do
      I need to do?

      Thanks,

      Josh
      ----- Original Message -----
      From: "Viktor Dukhovni" <postfix-users@...>
      To: <postfix-users@...>
      Sent: Tuesday, September 17, 2013 2:33 PM
      Subject: Re: update: 1 mail stoped by 1 user. Now it is 2 users and I
      noticed something.


      > On Tue, Sep 17, 2013 at 02:04:55PM -0600, Josh Cason wrote:
      >
      >> So this is a update. I had put a few days ago. I said 1 mail was
      >> stopped by 1 user in the incoming directory. Then goes away without
      >> a error. Well I now have 2 users. But I noticed something the other
      >> day and on this user. It has a pair of ?? marks on it. So I did a
      >> search but still did not provide any answers. Most of that type
      >> went through no problem. The other update was there was on some
      >> email. It showed up a few hours later. I'm still trying to see that
      >> in my logs. But what would cause a message to hang out in the
      >> incoming that long. When all the other go through? Size? I did
      >> finally see a bounce back. I'll look into that too. See if I can
      >> find out what it says.
      >
      > The above is a bunch of speculative noise. To report a problem:
      >
      > - Provide configuration information (postconf -n, master.cf, ...)
      >
      > - Provide detailed related logging (matching the queue-id and
      > any related earlier messages from processes with the same pid).
      > Also any related logging from master(8) about its child processes.
      >
      > - Show a long listing of the problem queue file with permissions
      > and modification time as well as the current time reported by "date".
      >
      > - Show the output of "postcat -q -eh <queue-id>" for the problem
      > queue-id.
      >
      > Messages for which the SMTP client never sends "." may sit (incomplete)
      > in incoming for some time. Also if your operating system has buggy
      > poll or epoll code, daemon processes may hang intermittently and
      > be killed by the watchdog timer.
      >
      > A message is incomplete while its permissions are 0600, and changes
      > to 0700 once cleanup(8) has received and post-processed (perhaps via a
      > milter) the entire message.
      >
      > Without real evidence, you're on your own.
      >
      > --
      > Viktor.
      >
      > --
      > This message has been scanned for viruses and
      > dangerous content by Galaxy Mail Server, and is
      > believed to be clean.
      >


      --
      This message has been scanned for viruses and
      dangerous content by Galaxy Mail Server, and is
      believed to be clean.
    • Wietse Venema
      ... # postcat -q queueid | sed /^$/q Options -e and -h were added in Postfix 2.7 (over three years ago). Wietse
      Message 2 of 6 , Sep 23, 2013
        Josh Cason:
        > The postcat -q -eh command does not work. It does not like the -e??? What do
        > I need to do?

        # postcat -q queueid | sed '/^$/q'

        Options -e and -h were added in Postfix 2.7 (over three years ago).

        Wietse


        >
        > Josh
        > ----- Original Message -----
        > From: "Viktor Dukhovni" <postfix-users@...>
        > To: <postfix-users@...>
        > Sent: Tuesday, September 17, 2013 2:33 PM
        > Subject: Re: update: 1 mail stoped by 1 user. Now it is 2 users and I
        > noticed something.
        >
        >
        > > On Tue, Sep 17, 2013 at 02:04:55PM -0600, Josh Cason wrote:
        > >
        > >> So this is a update. I had put a few days ago. I said 1 mail was
        > >> stopped by 1 user in the incoming directory. Then goes away without
        > >> a error. Well I now have 2 users. But I noticed something the other
        > >> day and on this user. It has a pair of ?? marks on it. So I did a
        > >> search but still did not provide any answers. Most of that type
        > >> went through no problem. The other update was there was on some
        > >> email. It showed up a few hours later. I'm still trying to see that
        > >> in my logs. But what would cause a message to hang out in the
        > >> incoming that long. When all the other go through? Size? I did
        > >> finally see a bounce back. I'll look into that too. See if I can
        > >> find out what it says.
        > >
        > > The above is a bunch of speculative noise. To report a problem:
        > >
        > > - Provide configuration information (postconf -n, master.cf, ...)
        > >
        > > - Provide detailed related logging (matching the queue-id and
        > > any related earlier messages from processes with the same pid).
        > > Also any related logging from master(8) about its child processes.
        > >
        > > - Show a long listing of the problem queue file with permissions
        > > and modification time as well as the current time reported by "date".
        > >
        > > - Show the output of "postcat -q -eh <queue-id>" for the problem
        > > queue-id.
        > >
        > > Messages for which the SMTP client never sends "." may sit (incomplete)
        > > in incoming for some time. Also if your operating system has buggy
        > > poll or epoll code, daemon processes may hang intermittently and
        > > be killed by the watchdog timer.
        > >
        > > A message is incomplete while its permissions are 0600, and changes
        > > to 0700 once cleanup(8) has received and post-processed (perhaps via a
        > > milter) the entire message.
        > >
        > > Without real evidence, you're on your own.
        > >
        > > --
        > > Viktor.
        > >
        > > --
        > > This message has been scanned for viruses and
        > > dangerous content by Galaxy Mail Server, and is
        > > believed to be clean.
        > >
        >
        >
        > --
        > This message has been scanned for viruses and
        > dangerous content by Galaxy Mail Server, and is
        > believed to be clean.
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.