|
Save the teapot fund New CSS web design for Wibble proudly provided by Kelv. Please contact the webmaster with any questions or concerns. |
Wibble > List archives > postfix > 2004 > October [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: postfix/qmgr[xxx]: xxx: to=<xxx>, relay=none, delay=xxx, status=deferred (delivery temporarily suspended: transport is unavailable)
On Saturday, October 02, 2004 at 12:33 CEST,
Kapoli András <akapoli@xxxxxx> wrote:
[...]
> qmgr -v logging shows:
>
> postfix/qmgr[xxx]: qmgr_queue_unthrottle: queue [foo]@[bar].hu
> postfix/qmgr[xxx]: qmgr_active_done: 9A71523D0D
> postfix/qmgr[xxx]: 9A71523D0D: removed
> postfix/qmgr[xxx]: qmgr_job_free: 9A71523D0D local
> postfix/qmgr[xxx]: watchdog_start: 0x80752a0
> postfix/qmgr[xxx]: qmgr_transport_unthrottle: transport filter
> postfix/qmgr[xxx]: watchdog_start: 0x80752a0
> postfix/qmgr[xxx]: qmgr_transport_select: filter
> postfix/qmgr[xxx]: qmgr_active_drain: allocate filter
> postfix/qmgr[xxx]: connect to subsystem private/filter: Connection
> refused
> postfix/qmgr[xxx]: qmgr_transport_throttle: transport filter: reason:
> transport is unavailable
>
> qmgr_transport_select: filter, why not smtp instead?
You have something in your configuration that selects "filter" as the
nexthop transport. You may have an old message with such a content
filter. Requeuing all messages ("postsuper -r ALL") will solve that
(provided, of course, that nothing in your new configuration will use
the "filter" transport).
--
Magnus Bäck
magnus@xxxxxxxxxxx
|