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

Stress docs update

Expand Messages
  • Michael Orlitzky
    At the bottom of the stress readme, http://www.postfix.org/STRESS_README.html#other there is an allusion to what would eventually become postscreen. Might as
    Message 1 of 6 , May 1, 2012
      At the bottom of the stress readme,

      http://www.postfix.org/STRESS_README.html#other

      there is an allusion to what would eventually become postscreen. Might
      as well update it with a sentence and a link to POSTSCREEN_README.html?
    • Wietse Venema
      ... Right. Who has time? Wietse
      Message 2 of 6 , May 1, 2012
        Michael Orlitzky:
        > At the bottom of the stress readme,
        >
        > http://www.postfix.org/STRESS_README.html#other
        >
        > there is an allusion to what would eventually become postscreen. Might
        > as well update it with a sentence and a link to POSTSCREEN_README.html?

        Right. Who has time?

        Wietse
      • DTNX Postmaster
        ... Please let me know if this isn t the right format, style and such; $ diff -u STRESS_README.html STRESS_README-postscreen.html ... +++
        Message 3 of 6 , May 3, 2012
          On May 1, 2012, at 18:32, Wietse Venema wrote:

          > Michael Orlitzky:
          >> At the bottom of the stress readme,
          >>
          >> http://www.postfix.org/STRESS_README.html#other
          >>
          >> there is an allusion to what would eventually become postscreen. Might
          >> as well update it with a sentence and a link to POSTSCREEN_README.html?
          >
          > Right. Who has time?
          >
          > Wietse

          Please let me know if this isn't the right format, style and such;

          $ diff -u STRESS_README.html STRESS_README-postscreen.html
          --- STRESS_README.html 2012-05-03 10:20:36.000000000 +0200
          +++ STRESS_README-postscreen.html 2012-05-03 10:26:27.000000000 +0200
          @@ -520,11 +520,12 @@
          server. Other clients are tarpitted, and will never get a chance
          to affect mail server performance. </p>

          -<p> At some point in the future, Postfix may come with a simple
          -front-end daemon that does basic greylisting and pipelining detection
          -to keep zombies and other ratware away from Postfix itself. This
          -would use the "pass" service type which has been available in
          -stable Postfix releases since Postfix 2.5. </p>
          +<p> Since version 2.8, Postfix ships with a front-end daemon called
          +<a href="postscreen.8.html">postscreen(8)</a> that does basic
          +greylisting and pipelining detection to keep zombies and other ratware
          +away from Postfix itself. For further information and implementation
          +details, see <a href="POSTSCREEN_README.html">POSTSCREEN_README</a>.
          +</p>

          <h2><a name="credits"> Credits </a></h2>


          HTH,
          Jona
        • Rob Sterenborg
          ... According to the POSTSCREEN_README, postscreen doesn t do greylisting at all: postscreen and greylisting are different things. The below is your patch
          Message 4 of 6 , May 3, 2012
            > -----Original Message-----
            > From: owner-postfix-users@... [mailto:owner-postfix-
            > users@...] On Behalf Of DTNX Postmaster
            > Sent: Thursday, May 03, 2012 10:43 AM
            > To: postfix users
            > Subject: Re: Stress docs update
            >
            > Please let me know if this isn't the right format, style and such;
            >
            > $ diff -u STRESS_README.html STRESS_README-postscreen.html
            > --- STRESS_README.html 2012-05-03 10:20:36.000000000 +0200
            > +++ STRESS_README-postscreen.html 2012-05-03 10:26:27.000000000
            > +0200
            > @@ -520,11 +520,12 @@
            > server. Other clients are tarpitted, and will never get a chance
            > to affect mail server performance. </p>
            >
            > -<p> At some point in the future, Postfix may come with a simple
            > -front-end daemon that does basic greylisting and pipelining detection
            > -to keep zombies and other ratware away from Postfix itself. This
            > -would use the "pass" service type which has been available in
            > -stable Postfix releases since Postfix 2.5. </p>
            > +<p> Since version 2.8, Postfix ships with a front-end daemon called
            > +<a href="postscreen.8.html">postscreen(8)</a> that does basic
            > +greylisting and pipelining detection to keep zombies and other
            > ratware
            > +away from Postfix itself. For further information and implementation
            > +details, see <a href="POSTSCREEN_README.html">POSTSCREEN_README</a>.
            > +</p>
            >
            > <h2><a name="credits"> Credits </a></h2>

            According to the POSTSCREEN_README, postscreen doesn't do greylisting at
            all: postscreen and greylisting are different things. The below is your
            patch adapted with a partial copy-paste from the POSTSCREEN_README.


            --
            Rob


            --- STRESS_README.html 2012-05-03 10:54:00.624335965 +0200
            +++ STRESS_README-postscreen.html 2012-05-03 10:58:40.638712109 +0200
            @@ -503,11 +503,14 @@
            server. Other clients are tarpitted, and will never get a chance
            to affect mail server performance. </p>

            -<p> At some point in the future, Postfix may come with a simple
            -front-end daemon that does basic greylisting and pipelining detection
            -to keep zombies and other ratware away from Postfix itself. This
            -would use the "pass" service type which has been available in
            -stable Postfix releases since Postfix 2.5. </p>
            +<p> Since version 2.8, Postfix ships with a front-end daemon called
            +<a href="postscreen.8.html">postscreen(8)</a> that performs triage
            +on multiple inbound SMTP connections at the same time. While a single
            +postscreen(8) process keeps zombies away from Postfix SMTP server
            +processes, more Postfix SMTP server processes remain available for
            +legitimate clients. For further information and implementation
            +details, see <a href="POSTSCREEN_README.html">POSTSCREEN_README</a>.
            +</p>

            <h2><a name="credits"> Credits </a></h2>
          • Michael Orlitzky
            ... When a client passes the deep protocol tests, postscreen sends it a 4xx; that s essentially greylisting. But, there s no need to mention that on
            Message 5 of 6 , May 4, 2012
              On 05/03/12 05:14, Rob Sterenborg wrote:
              >>
              >> <h2><a name="credits"> Credits </a></h2>
              >
              > According to the POSTSCREEN_README, postscreen doesn't do greylisting at
              > all: postscreen and greylisting are different things. The below is your
              > patch adapted with a partial copy-paste from the POSTSCREEN_README.
              >

              When a client passes the deep protocol tests, postscreen sends it a 4xx;
              that's essentially greylisting. But, there's no need to mention that on
              STRESS_README: it can be inferred from POSTSCREEN_README.
            • Wietse Venema
              This is now updated. Wietse Other measures to off-load zombies The postscreen(8) daemon, introduced with Postfix 2.8, provides additional protection against
              Message 6 of 6 , May 6, 2012
                This is now updated.

                Wietse

                Other measures to off-load zombies

                The postscreen(8) daemon, introduced with Postfix 2.8, provides
                additional protection against mail server overload. One postscreen(8)
                process handles all connections from "new" SMTP clients, and allows
                only well-behaved clients to talk to a Postfix SMTP server process.
                By keeping spambots away, postscreen(8) leaves more SMTP server
                processes available for legitimate clients, and delays the onset
                of server overload conditions.
              Your message has been successfully submitted and would be delivered to recipients shortly.