Try create another postfix instance and force your filter send message to it.


________________________________
De: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> em nome 
de Rafael Azevedo <raf...@gmail.com>
Enviado: sexta-feira, 4 de janeiro de 2019 16:21
Para: Postfix users
Assunto: Re: Content filter - reijnect message back into queue

Viktor,

After doing as explained @ 
http://www.postfix.org/FILTER_README.html<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.postfix.org%2FFILTER_README.html&data=02%7C01%7C%7C031939dbd35f40c9c63908d672717813%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636822229006110766&sdata=LbHb%2Bqz8G4nIn%2BGCMtv8g%2BY0JvP7yzuTQamDr%2BXQNVs%3D&reserved=0>,
 I'm still having same behavior.

Jan  4 15:23:16 zimuslab postfix/pipe[2026324]: 90FAD13DE3B1: 
to=<x...@xx.net<mailto:x...@xx.net>>, relay=post_queue_content_filter, 
delay=0.07, delays=0.04/0/0/0.02, dsn=2.0.0, status=sent (delivered via 
post_queue_content_filter service (action=PERMIT))

After changing my script to simply "return" the situation persists.

Jan  4 15:33:27 zimuslab postfix/pipe[2026361]: 7751713DE600: 
to=<x...@xx.net<mailto:x...@xx.net>>, relay=post_queue_content_filter, 
delay=0.07, delays=0.04/0/0/0.02, dsn=2.0.0, status=sent (delivered via 
post_queue_content_filter service)

BR,
Rafael

Em sex, 4 de jan de 2019 às 15:28, Viktor Dukhovni 
<postfix-us...@dukhovni.org<mailto:postfix-us...@dukhovni.org>> escreveu:


> On Jan 4, 2019, at 11:54 AM, Rafael Azevedo 
> <raf...@gmail.com<mailto:raf...@gmail.com>> wrote:
>
> So I kindly ask you guys how can I re-inject message back into queue.

http://www.postfix.org/FILTER_README.html<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.postfix.org%2FFILTER_README.html&data=02%7C01%7C%7C031939dbd35f40c9c63908d672717813%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636822229006110766&sdata=LbHb%2Bqz8G4nIn%2BGCMtv8g%2BY0JvP7yzuTQamDr%2BXQNVs%3D&reserved=0>

--
        Viktor.

Reply via email to