Oi Marcio, por esse motivo seria abcana vc aumentar os debugs dos
processos do postfix e acompanhar no log, aí vco saberia exatamente
onde está parando.

http://www.postfix.org/DEBUG_README.html

Making Postfix daemon programs more verbose

Append one or more "-v" options to selected daemon definitions in
/etc/postfix/master.cf and type "postfix reload". This will cause a
lot of activity to be logged to the syslog daemon. For example, to
make the Postfix SMTP server process more verbose:

    /etc/postfix/master.cf:
        smtp      inet  n       -       n       -       -       smtpd -v

To diagnose problems with address rewriting specify a "-v" option for
the cleanup(8) and/or trivial-rewrite(8) daemon, and to diagnose
problems with mail delivery specify a "-v" option for the qmgr(8) or
oqmgr(8) queue manager, or for the lmtp(8), local(8), pipe(8),
smtp(8), or virtual(8) delivery agent.
Manually tracing a Postfix daemon process

Many systems allow you to inspect a running process with a system call
tracer. For example:

    # trace -p process-id (SunOS 4)
    # strace -p process-id (Linux and many others)
    # truss -p process-id (Solaris, FreeBSD)
    # ktrace -p process-id (generic 4.4BSD)

Even more informative are traces of system library calls. Examples:

    # ltrace -p process-id (Linux, also ported to FreeBSD and BSD/OS)
    # sotruss -p process-id (Solaris)

See your system documentation for details.

Tracing a running process can give valuable information about what a
process is attempting to do. This is as much information as you can
get without running an interactive debugger program, as described in a
later section.
Automatically tracing a Postfix daemon process

Postfix can attach a call tracer whenever a daemon process starts.
Call tracers come in several kinds.

   1.

      System call tracers such as trace, truss, strace, or ktrace.
These show the communication between the process and the kernel.
   2.

      Library call tracers such as sotruss and ltrace. These show
calls of library routines, and give a better idea of what is going on
within the process.

Append a -D option to the suspect command in /etc/postfix/master.cf,
for example:

    /etc/postfix/master.cf:
        smtp      inet  n       -       n       -       -       smtpd -D

Edit the debugger_command definition in /etc/postfix/main.cf so that
it invokes the call tracer of your choice, for example:

    /etc/postfix/main.cf:
        debugger_command =
             PATH=/bin:/usr/bin:/usr/local/bin;
             (truss -p $process_id 2>&1 | logger -p mail.info) & sleep 5

Type "postfix reload" and watch the logfile.


2011/3/16 Márcio Luciano Donada <[email protected]>:
> Em 16/3/2011 18:52, Hamilton Vera escreveu:
>> do postfix e poste os logs do sistema.
>>
> Hamilton,
> Acabei de descobrir agora um timed out no postqueue -p (esses são os
> deferred)
>
> mx:/etc/postfix# postqueue -p|grep timed|wc -l
> 682
>
>
>                                        T  5 10 20 40  80 160 320 640
> 1280 1280+
>                                TOTAL 949  2  7 55 50 166 656   5   5
> 2     1
>                          hotmail.com 158  1  3 17 10  29  98   0   0
> 0     0
>                            gmail.com  78  0  1 11  7   8  51   0   0
> 0     0
>                         yahoo.com.br  75  0  0  3  1   7  64   0   0
> 0     0
>                         terra.com.br  70  1  1  7  5   8  48   0   0
> 0     0
>                  toledobrasil.com.br  39  0  0  0  9  18  12   0   0
> 0     0
>                           uol.com.br  30  0  0  4  2   5  19   0   0
> 0     0
>                  cooperitaipu.com.br  28  0  0  1  0   5  22   0   0
> 0     0
>                     angellira.com.br  27  0  0  0  1   9  17   0   0
> 0     0
>                        realbanco.com  24  0  0  0  0   1  17   5   0
> 1     0
>                            ig.com.br  17  0  0  2  0   5  10   0   0
> 0     0
>                       brturbo.com.br  17  0  0  0  0   2  15   0   0
> 0     0
>                       chr-hansen.com  15  0  0  0  0  15   0   0   0
> 0     0
>                      coolacer.com.br  13  0  0  0  0   0  13   0   0
> 0     0
>                      desbrava.com.br  12  0  0  0  0   0  12   0   0
> 0     0
>                    unochapeco.edu.br  11  0  0  0  0   1  10   0   0
> 0     0
>                        comper.com.br  10  0  0  0  2   0   8   0   0
> 0     0
>                         mhnet.com.br   9  0  0  0  0   0   9   0   0
> 0     0
>                  globalproductssa.cl   9  0  0  0  0   0   9   0   0
> 0     0
>                      cotrisal.com.br   8  0  0  0  0   2   6   0   0
> 0     0
>
> Porém, não consigo entender porque não entrega, pois eu peguei o caso do
> hotmail, dei um telnet no MX dele e abriu numa boa. Porém os IPs que
> estão nas mensagens da fila, infelimente não abrem. Agora não sei como
> devo proceder.
> _______________________________________________
> Postfix-BR mailing list
> [email protected]
> http://listas.softwarelivre.org/mailman/listinfo/postfix-br
>



-- 
Hamilton Vera
int Administrator (char Network[],char ComputationalSystems[])
http://hvera.wordpress.com
_______________________________________________
Postfix-BR mailing list
[email protected]
http://listas.softwarelivre.org/mailman/listinfo/postfix-br

Responder a