On 31 December 2022 05:29:58 CET, Sean Hennessey <sean.hennes...@mercurygate.com> wrote: >I'm doing some testing and am trying to figure out a way to set up postfix so >that it won't ever send a DSN. > >In googling around I found one option is to change the bounce service in >master.cf to use the discard service. That seems to stop the DSN for a bounce >to be sent out, but I get some warnings in the logs about attributes. I'm >assuming that's because the discard service doesn't really know how to >properly deal w/ a bounce request. > >bounce unix - - y - 0 discard -v -v -v > >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: connection established >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: master_notify: status 0 >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: deliver_request_initial: >send initial status >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: send attr status = 0 >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: vstream_fflush_some: fd >12 flush 10 >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: vstream_buf_get_ready: >fd 12 got 522 >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: bounce socket: wanted >attribute: flags >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: input attribute name: >nrequest >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: warning: unexpected >attribute nrequest from bounce socket (expecting: flags) >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: warning: >deliver_request_get: error receiving common attributes >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: deliver_request_final: >send: "" -1 >Dec 30 23:15:59 OptiPlex-9010 postfix/discard[17341]: send attr status = > >Is there a "correct" way to turn of all DSN notices for bounces? >
Hello, Sean. Have you tried the process described here: http://www.postfix.org/DSN_README.html André.
