[pfx] Re: Process and deliver email but return error to the client?

ust fulfill the requirements..." ;-) Thanks. -- Hawky Am 20.09.2024 16:25 schrieb Wietse Venema via Postfix-users: hawky--- via Postfix-users: Hi! I'm looking for a way to process and deliver an incoming email, but return an error (with a meaningful) message to the client. By looking

[pfx] Process and deliver email but return error to the client?

aybe it is possible in a non-obvious way? Is it possible? And if yes, can someone give me a hint howto implement? Thank you. -- Hawky ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org

[pfx] [postfix] 3.4.23: SpamAssassin - Re-submission with sendmail - Append"receive_override_options = no_address_mappings"?

Hi, We've a SpamAssassin setup with the after-queue approach. When re-submission a mail, that has been content filtered by SpamAssassin, with sendmail we see that the mail is delivered twice to the recipient, if the user has a forwarding email set. From our understanding that is a result of

[pfx] Re: [postfix] 3.4.23: virtual, pipe and ${original_recipient} vs. ${recipient}

Thanks for your advice. Am 25.01.2024 22:56 schrieb Viktor Dukhovni via Postfix-users: On Thu, Jan 25, 2024 at 04:48:39PM -0500, Bill Cole via Postfix-users wrote: > - Are you expected exactly one recipient per-invocation of the > spamassassin filter? I'm not sure how spamc handles multipl

[pfx] [postfix] 3.4.23: virtual, pipe and ${original_recipient} vs. ${recipient}

Hi, we're in the process to integrate SpamAssassin in our mail system. We decided to use the after-queue attempt with smtpd -o content_filter= The problem we're facing right now is that pipe is getting the alias name as recipient instead of the username - both are the same: postfix/pipe[

Re: [postfix] 3.5.13: Unable to append "X-Original-To" message header

Hi, just to wrap this up: The flags for lmtp were perfektly set, my "fault" was to use dovecot lmtp instead of postfix lmtp for mailbox transport - so no instance were setting the required message headers. Wietse, thanks for your help! Am 16.10.2022 14:11 schrieb Wietse Venema: ha...@po

[postfix] 3.5.13: Unable to append "X-Original-To" message header

Hi, we heavily use the alias feature and want to know who was the original recipient for filtering. Our old postfix instance (version 2.11.3) set this from the beginning - as far as I remember we never changed the configuration to archive this. Our new instance (version 3.5.13, not yet live)

[Virtual + Spamassassin] Alias table is evaluated twice

Hi, we're about to use Spamassassin in our postfix mail system. For that reason we "copied" our mail system to a virtual machine in order to see how Spamassassin is configured correctly. After we enabled Spamassassin we're facing the problem that the virtual table is evaluated a second time