Am Dienstag, 21. Februar 2006 21:17 schrieb Timo Zimmermann:
> Am Dienstag, den 21.02.2006, 21:05 +0100 schrieb Gerhard Gaußling:
> > Was hat es damit auf sich?
>
> hast du dir den Link mal durchgelesen bzw. die genau Meldung?
> Was glaubst du wohl, was es damit auf sich hat?
Keine Ahnung:
http://www.abuse.net/cgi-bin/relaytest
Mail relay testing
Connecting to 84.175.79.64 for anonymous test ...
Relay test result
Could not connect, test failed.
Um einen open relay wird es sich bei meinem Rechner also wohl nicht
handeln?
http://www.google.com/search?num=50&hs=QrI&hl=de&client=firefox&rls=org.mozilla%3Ade-DE%3Aunofficial&q=error+421+%22open+relay%22+postfix&btnG=Suche&lr=
Das einzige, was ich in dem Postfix-Manual finden konnte ist:
<quote>
Here the "highvolume.com" destination is continuing to accumulate
deferred mail. The incoming and active queues are fine, but the
deferred queue started growing some time between 1 and 2 hours
ago and continues to grow.
If the high volume destination is not down, but is instead slow, one
might see similar congestion in the active queue. Active queue
congestion is a greater cause for alarm; one might need to take
measures to ensure that the mail is deferred instead or even add an
access(5) rule asking the sender to try again later.
If a high volume destination exhibits frequent bursts of consecutive
connections refused by all MX hosts or "421 Server busy errors", it is
possible for the queue manager to mark the destination as "dead"
despite the transient nature of the errors. The destination will be
retried again after the expiration of a $minimal_backoff_time timer. If
the error bursts are frequent enough it may be that only a small
quantity of email is delivered before the destination is again marked
"dead".
The MTA that has been observed most frequently to exhibit such bursts of
errors is Microsoft Exchange, which refuses connections under load.
Some proxy virus scanners in front of the Exchange server propagate the
refused connection to the client as a "421" error.
Note that it is now possible to configure Postfix to exhibit similarly
erratic behavior by misconfiguring the anvil(8) server (not included in
Postfix 2.1.). Do not use anvil(8) for steady-state rate limiting, its
purpose is DoS prevention and the rate limits set should be very
generous!
</quote>
Ich werde da nicht ganz schlau draus. Allerdings meldet
murphy.debian.org bei meinen mails (aber nur von ggrubbish)
RCVD_IN_SORBS_DUL (spamassassin).
Ich kann erst morgen die Postfix Bücher aus der Bibliothek holen,
vielleicht hilft das ja.
ciao
Gerhard
--
ubuntu-de mailing list
ubuntu-de@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-de
|
