[pfx] Re: Postfix, Amavis DKIM and DMARC

>Conceptually you can. I tested it yesterday and it worked. At first I >encountered said phenomenon that the >mails in my inbox had no DMARC AR >header, but that was because the content_filter Amavis removed them. >After >disabling DKIM verification on the content_filter, headers looked like

[pfx] Re: Postfix, Amavis DKIM and DMARC

>That's what Dino is trying to do. Make amavis-over-milter add an DKIM >AR-header, then make OpenDMARC evaluate DMARC using that header. It may be >true that SpamAssassin 4 has a DMARC test, but Amavis >does not use such test >hit for a policy enforcement. >Amavis has support for rspamd as a

[pfx] Re: Postfix, Amavis DKIM and DMARC

-Original Message- From: Matus UHLAR - fantomas via Postfix-users Sent: Tuesday, November 14, 2023 8:04 AM To: postfix-users@postfix.org Subject: [pfx] Re: Postfix, Amavis DKIM and DMARC >this does not make sense unless you use it somewhere. Can you elaborate? >what do logs say?

[pfx] Re: Postfix, Amavis DKIM and DMARC

By “getting skipped” I mean I have no logs of opendmarc doing anything. I don’t understand how I would disable dkim in my content_filter policy. Dkim verification is either enabled or disabled in Amavis unless I’m not understanding what you mean. From: Damian via Postfix-users Sent:

[pfx] Postfix, Amavis DKIM and DMARC

Hello, I have been using OpenDKIM and OpenDMARC as smtpd_milters in Postfix and Amavis as a content filter. I'm trying to replace OpenDKIM with Amavis for DKIM verify and signing. The problem is that since Amavis is setup as an after-queue content_filter and OpenDMARC is a pre-queue

Re: Filter mail with dangerous attachments

Normally you would use a content filter like Amavis along side postfix accomplish this. From: Tan Mientras Sent: Wednesday, December 14, 2022 9:22 AMTo: postfix-us...@cloud9.netSubject: Filter mail with dangerous attachmentsHello Excuse my generic question, but I dont know where to startIs it

RE: Postscreen DNSBL do not seem to be working

>It's absolutely not forwarding. It's resolving recursively. I'm using unbound with pfsense and I'm suspecting there is something wrong with it. >When I point to MS DNS server or 9.9.9.9, it's resolving correctly. The issue has been resolved. Just in case someone finds the solution useful,

RE: Postscreen DNSBL do not seem to be working

>In any case, the OP may well be using a local resolver, but they didn't say whether it's resolving recursively or forwarding (e.g. to 8.8.8.8), and I'd bet it's the latter. It's absolutely not forwarding. It's resolving recursively. I'm using unbound with pfsense and I'm suspecting there is

RE: postfix-policyd-spf-python

-Original Message- From: owner-postfix-us...@postfix.org <> On Behalf Of Matus UHLAR - fantomas >perhaps a but I don't see So you agree, it should be passing but it's not for some reason.

Re: postfix-policyd-spf-python

On 5/13/2022 9:41 AM, Matus UHLAR - fantomas wrote: perhaps you can post logs? local part of mail address may be censored... Sure. NOQUEUE: reject: RCPT from smtp15-ia5-sp1.mta.salesforce.com[13.110.78.238]: 550 5.7.23 : Recipient address rejected: Message rejected due to: SPF fail - not

postfix-policyd-spf-python

Hi, Not sure if this is the right place to post the question concerning postfix-policyd-spf-python but I can't seem to find any working links for the openspf project. Our postfix-policyd-spf-python server recently rejected an e-mail from a sender that was using SPF macros. I tried to find out

10s of REJECT messages multiple times a day

Hello, We have various IPs that throughout the day hammer our server attempting to deliver messages to non-existent recipients. The messages get rejected because the recipients do not exist. This results with having 30 to 100 rejected emails at a time. What is the recommended way to combat

RE: Postgrey - whitelisting subdomains

Did you try using .dhs.gov In /usr/local/etc/postfix/postgrey_whitelist_clients.local? -Original Message- From: owner-postfix-us...@postfix.org On Behalf Of James B. Byrne Sent: Friday, November 26, 2021 2:33 PM To: postfix-us...@cloud9.net Subject: Postgrey - whitelisting

RE: HELO and nothing else

> I am working on a spam filter and so I find myself spending a lot more > quality time with mail logs than I used to. One of the things I have noticed > is that I will get a lot of connections that send a HELO command and then > disconnect. Sometimes I get this > repeated several times a

Postfix relay to external and internal

Hi, I have a postfix server that acts as a relay server for several domains and relays e-mail to several external e-mail servers based on the domain. This setup has been working for years with no problems. Now I have a need to install a local mailserver (dovecot?) server on this relay server

RE: Add additional smtp port in postfix

> Then why don't you setup a relay using port 587 elsewhere which you login to > to send/get emails? I don't think Verizon blocks that port at all... Cause it would be easier to setup the relay to listen on 2525 in addition to port 25 rather than setting up authentication on 587. They are

RE: Add additional smtp port in postfix

>The main question is, why do you need port other than 25? Cause Verizon blocks all incoming and outgoing traffic to port 25 unless it's to their SMTP servers and I have an Exchange server that needs to send/receive email through an outside relay.

Add additional smtp port in postfix

Hello all, I need to add an additional port for postfix to listen for incoming connections (port 2525). Most of the stuff I've seen on the Internet simply states to add the following in my master.cf smtp inet n - n - - smtpd 2525 inet n-

RE: Postfix, mailman, and aliases problem

Are you using system users or virtual users in your system? /etc/aliases are for system users in the system. You may be looking for virtual_alias_maps instead? -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of James Dore

451 4.3.5 Server configuration error

Hello, Having a strange issue with a server. Multiple times a day I get the following errors in mail.log: 451 4.3.5 Server configuration error; from= to= proto=ESMTP helo= I also get the following email in my admin mailbox: From: Mail Delivery System