Wietse, > With an ugly hack we could make these a "notify-none" recipient
I always like ugly hacks ;-) This > /^(RCPT\s+TO:\s<corpus-(ham|spam)@MYDOMAIN.*)/$1 NOTIFY=NEVER in command_filter seems to do the job. Just wonder could a time-unit be specified instead of NEVER? But I still keep my graveyard postfix which I already setup based on Viktors reply. Always good to have a graveyard behind the house ;-) Have a good one and happy 2022 to all tobi On Thu, 2022-01-06 at 11:30 -0500, Wietse Venema wrote: > Viktor Dukhovni: > > On Thu, Jan 06, 2022 at 01:08:33PM +0100, > > tobs...@brain-force.ch wrote: > > > > > Is somehow possible to use other delay notification settings for > > > a > > > particular recipient address? > > > > No, this is a message-level property, same for all delayed > > recipients > > of the message. > > With an ugly hack we could make these a "notify-none" recipient > (see example in > http://www.postfix.org/postconf.5.html#smtpd_command_filter). > > > > My global setting is 30min which is fine except for two > > > addresses. > > > Those addresses are on a remote system which is not always up. It > > > gets > > > the mail on boot by ETRN command to the postfix server. So it > > > queues on > > > postfix server until that box is up again the next day (starts > > > once a > > > day for about 3hrs) > > > > > > Now I get a shipload of delay message warnings for this two > > > addresses. > > > So I wonder if it would be possible to configure other delay > > > warning > > > setting (ex 24h) for these two particular addresses. > > > > > > Thanks for any ideas and have a good one > > > > The only way to handle this is to relay the mail in question to a > > separate "slow" Postfix instance (not a transport, but a completely > > separate Postfix with its own main.cf, queue manager, ...). > > > > In that Postfix instance you can have a longer or no delay warning. > > I agree, a proper solution requires a Postfix 'graveyard' instance. > > Wietse
