Re: Transport not available
Sven Juergensen (KielNET)
it's postmap not postalias.
*whistle*
never mind ;)
Mit freundlichen Gruessen
i. A. Sven Juergensen
--
Fachbereich
Informationstechnologie
KielNET GmbH
Gesellschaft fuer Kommunikation
Preusserstr. 1-9, 24105 Kiel
Telefon : 0431 / 2219-053
Telefax : 0431 / 2219-005
E-Mail : s.juer...@kielnet.de
Internet: http://www.kielnet.de
AS# 25295
Key fingerprint:
65B6 90FC 010A 39CE DCA5 336D 9C45 3B7A B02D E132
"221 2.7.0 Error: I can break rules, too. Goodbye."
Geschaeftsfuehrer Eberhard Schmidt
HRB 4499 (Amtsgericht Kiel)
Sven Juergensen (KielNET) wrote:
> Hi list,
>
> does anyone have an idea about why
> something like the following happened?
>
> Jan 10 09:14:37 mx2 postfix/qmgr[32000]: EF9C4217CB:
> to=<som...@bla.blub>, relay=none, delay=43213, delays=43213/0.02/0/0,
> dsn=4.3.0, status=deferred (mail transport unavailable)
>
> There are like 5. mails queued and every
> single one of them has this issue. I redid
> the hashed transport so that it points to
> another rfc 1918 ip machine
> (domain.com :[mach1.in.e]) followed by a
> postalias but a postsuper -r ALL or a
> restart of postfix just spits out the
> following logmessage:
>
> warning: connect to transport [mach1.in.e]: No such file or directory
>
> In essence, the mails are kind of stuck
> on that machine. Is there a way to
> direct them to another machine or
> migrate the entire mailq to somewhere
> else?
>
> Many thanks and regards,
>
> sven03
>
> Mit freundlichen Gruessen
>
> i. A. Sven Juergensen
>