Path: ...!eternal-september.org!feeder2.eternal-september.org!eternal-september.org!usenet.ovh!news.usenet.ovh!.POSTED!not-for-mail From: Christophe PEREZ Newsgroups: fr.comp.mail.serveurs Subject: Re: Spamassassin et utilisateurs virtuels Date: Thu, 9 Nov 2023 18:43:56 -0000 (UTC) Organization: Alfa Network En Travaux Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Thu, 9 Nov 2023 18:43:56 -0000 (UTC) Injection-Info: news.usenet.ovh; posting-account="christophe"; logging-data="986982"; mail-complaints-to="abuse@usenet.ovh" User-Agent: Pan/0.153 (Mariupol; c5405f5) Cancel-Lock: sha256:W/Ng+zNH/cack+OYGTw9R/HKcDyrjcSd6RCBBb/PBjU= Bytes: 1800 Lines: 15 Le Thu, 9 Nov 2023 18:38:10 -0000 (UTC), Christophe PEREZ a écrit : > Tu l'as mis dans ton postfix, rechargé postfix, et ça ne change rien à > ton 2ème cas ? Tout ce que je trouve sur le sujet référence systématiquement cette option. spamassassin_destination_recipient_limit = 1 is required to make sure that every recipient gets individually processed by spamassassin. This is required due to the D flag above (Includes X-Original-To header). If you've the D flag and you don't set spamassassin_destination_recipient_limit = 1 email with multiple destinations won't be delivered! If you don't care about this header you can remove the flag and this isn't needed. https://unix.stackexchange.com/questions/247433/postfix-spamassassin- incoming-mail-headers-changes