[pfx] inet_interfaces and loopback

2024-05-16 Thread Alex via Postfix-users
Hi, I have a fedora38 system with postfix-3.7.9 that fails to start on boot because of the below problem. I have intentionally set inet_interfaces to only 127.0.0.1 because it's my outbound interface that communicates with amavisd on 10025. This must be related to the fedora systemd scripts using

[pfx] Re: pushing changes to remote system

2024-05-14 Thread Alex via Postfix-users
sers > |> @postfix.org> wrote: > |> Alex via Postfix-users: > |>> Hi, > |>> I have a few postfix systems on fedora38 with nearly identical > |>> configurations. I'd like to be able to push changes to them from a > third > |>> system without

[pfx] recipient_bcc_maps with multi-instance

2024-05-10 Thread Alex via Postfix-users
Hi, I'm using postfix-3.7.9 multi-instance on fedora38 and can't figure out why always_bcc and recipient_bcc_maps aren't working on the outbound instance. It would work best in the outbound instance because of other processing that's happening in the inbound instances. # postmulti -l -

[pfx] Implementing ARC with postfix to allow/assist with forwarding

2024-05-03 Thread Alex via Postfix-users
Hi, I'm using postfix-3.7.9 on fedora38 and would like to implement ARC to assist with authenticating emails being forwarded by users to Gmail and others. The research I've done points to OpenARC as a dead project. This looks like a great guide to get started, but I'm having trouble identifying

[pfx] Re: sender_login_maps and dovecot and roundcube

2024-04-01 Thread Alex via Postfix-users
Hi, > > I've set up a domain with a catch-all to deliver emails to any address > > to a > > single recipient address by specifying it in my virtual_alias_maps. > > However, the user wants to be able to send mail as any user in that > > domain. > > The problem is that it's rejected with "sender

[pfx] sender_login_maps and dovecot and roundcube

2024-03-28 Thread Alex via Postfix-users
HI, I've set up a domain with a catch-all to deliver emails to any address to a single recipient address by specifying it in my virtual_alias_maps. However, the user wants to be able to send mail as any user in that domain. The problem is that it's rejected with "sender address rejected" because

[pfx] pushing changes to remote system

2024-03-06 Thread Alex via Postfix-users
Hi, I have a few postfix systems on fedora38 with nearly identical configurations. I'd like to be able to push changes to them from a third system without having to login to them directly to do so. What's the best/most secure way to do this? For example, I'd like to push the recipient access file

[pfx] Re: ARC or DKIM or SRS?

2024-02-12 Thread Alex via Postfix-users
Hi, On Mon, Feb 12, 2024 at 5:39 AM Jaroslaw Rafa via Postfix-users < postfix-users@postfix.org> wrote: > Dnia 11.02.2024 o godz. 17:47:05 Alex via Postfix-users pisze: > > My concern would be with multiple MX records for the same domain - is it > > possible it would c

[pfx] Re: ARC or DKIM or SRS?

2024-02-11 Thread Alex via Postfix-users
Hi, > It has multiple benefits against bots, like: > > - few seconds delay for refusing clients that send helo/ehlo before > > esmtp greeting (I have used this for years with sendmail) > > - dnwsl/dnsbl scoring system. > > > > These are pretty safe to use. > > These are the tests that are enabled

[pfx] ARC or DKIM or SRS?

2024-02-07 Thread Alex via Postfix-users
Hi, I'm hoping I could ask for some advice. We have a pretty large percentage of users who forward mail through our systems to personal Gmail accounts. Sometimes it is mail from bulk senders like mailgun and lanyon/cvent. Would ARC help here, or is DKIM enough for DMARC alignment with forwarded

[pfx] client checks with suspect IPs

2024-01-16 Thread Alex via Postfix-users
Hi, I need help with making a decision involved in determining whether to add an IP to my client_checks to bypass a blocklist entry on the Barracuda blocklist that is impacting one of our users. The problem is that this would also bypass the checks for other Zix hosted customers. Jan 16 12:04:30

[pfx] python-policyd-spf and whitelisting

2023-10-13 Thread Alex via Postfix-users
Hi, I'm using python-policyd-spf with postfix as a check_policy_service and having some trouble with domains very broadly being whitelisted. My policy is to reject on mailfrom fail. However, we have few domains that need to be whitelisted, like mycuservices.com, because they are sending from an

[pfx] Re: tls and cert problem for submission

2023-10-05 Thread Alex via Postfix-users
Hi, > I think I'm having a problem with my certificate for submission not > > being configured properly. I'm trying to install roundcube but having > > a problem with properly configuring the cert for submission, but when > > using openssl to check, it reports a cert problem. This is a cert from

[pfx] tls and cert problem for submission

2023-10-05 Thread Alex via Postfix-users
Hi, I think I'm having a problem with my certificate for submission not being configured properly. I'm trying to install roundcube but having a problem with properly configuring the cert for submission, but when using openssl to check, it reports a cert problem. This is a cert from Digicert.

[pfx] error:0A0000C1:SSL routines::no shared cipher:ssl/st atem/statem_srvr.c:2220:

2023-09-11 Thread Alex via Postfix-users
Hi, I have a postfix-3.7.4 server with openssl-3.0.9 on fedora38 and receiving the following errors in my logs: Sep 11 14:19:51 cipher postfix/smtps/smtpd[3992923]: warning: TLS library problem: error:0AC1:SSL routines::no shared cipher:ssl/statem/statem_srvr.c:2220: What kind of clients is

[pfx] Rate limiting gmail

2023-08-22 Thread Alex via Postfix-users
Hi, I'm hoping I could ask what is probably an FAQ but I haven't seen anything on it recently. I've already implemented some type of rate limiting for delivering to gmail, but it's apparently not working satisfactorily for them. Notice it's already going through my throttled transport. This mail

[pfx] Re: Troubleshooting mail loop issue

2023-08-15 Thread Alex via Postfix-users
Hi, On Tue, Aug 15, 2023 at 8:49 AM Bill Cole via Postfix-users < postfix-users@postfix.org> wrote: > On 2023-08-14 at 17:23:34 UTC-0400 (Mon, 14 Aug 2023 17:23:34 -0400) > Alex via Postfix-users > is rumored to have said: > > > Hi, > > I have what appears to be a

[pfx] Re: Troubleshooting mail loop issue

2023-08-15 Thread Alex via Postfix-users
e, the recipient does exist. I don't believe it's ever happened with a non-existent recipient. We aren't pulling the list of valid recipients, but instead just letting their system send us the reject for non-existent recipients. Thanks, Alex > Regards Paul > On 14/08/2023 22:23, A

[pfx] Re: Troubleshooting mail loop issue

2023-08-15 Thread Alex via Postfix-users
Hi, On Tue, Aug 15, 2023 at 11:02 AM Wietse Venema via Postfix-users < postfix-users@postfix.org> wrote: > Your loop, based on Received: headers, newer at the top, older at > the bottom: > > Received: from xavier.example.com (209.216.111.114) by > CO1PEPF44F7.mail.protection.outlook.com

[pfx] Troubleshooting mail loop issue

2023-08-14 Thread Alex via Postfix-users
Hi, I have what appears to be a complicated mail loop problem that I can't figure out. I suspect that their receiving system (M365) is somehow reinjecting the message back to our mail server after it's been successfully delivered to them. We are acting as MX for two small companies, and

[pfx] Re: bounce management

2023-08-07 Thread Alex via Postfix-users
Hi, > > We're only doing basic spam protection for them, > > What is the nature of the "basic spam protection"? Can it be done > pre-queue? > Yes, most likely, I would think. It's a basic spamassassin setup with a few rules looking for specific patterns, as well as some RBL network checks.

[pfx] bounce management

2023-08-07 Thread Alex via Postfix-users
Hi, I have a postfix-3.7.3 system on fedora37 and we're routing mail for a business using an Ironport device at their border. Instead of accepting all messages from us as their MX, there are some messages that it has determined are spam or otherwise undeliverable, which are resulting in them

[pfx] Re: content filter sends mail twice

2023-05-23 Thread Alex via Postfix-users
Hi, On Mon, May 22, 2023 at 9:47 PM Viktor Dukhovni via Postfix-users < postfix-users@postfix.org> wrote: > On Mon, May 22, 2023 at 06:06:00PM -0400, Alex wrote: > > > Yes, I wasn't aware that's how it worked. I've now explicitly defined the > > bcc-user to use the same transport, but the

[pfx] Re: content filter sends mail twice

2023-05-22 Thread Alex via Postfix-users
Hi, > > The BCC recipient is processed in much the same way as any other message > recipient. The only special handling that comes to mind is DSN, where > this recipient is treated as if NOTIFY=NEVER were specified. > > > local_transport = error:5.1.1 Mailbox unavailable > > default_transport =

[pfx] Re: per-domain header/body checks?

2023-05-21 Thread Alex via Postfix-users
Hi, > According to the subject, you appear to be looking for per-domain > header/body check. That is not the right tool, and I would not > spend my cycles on a design for that. > > Instead I recommend filters between a front and back-end instance, > using transport_maps to select a filter

[pfx] Re: per-domain header/body checks?

2023-05-21 Thread Alex via Postfix-users
Hi, > > > > internet -> front-end Postfix instance -> filter -> back-end > > > Postfix > > > > > instance > > > > > > > > > > The front-end Postfix instance uses transport_maps to select a > suitable > > > > > filter. > > > > > > > > > > example.com: smtp: > > > > > example.org: smtp:

[pfx] Re: per-domain header/body checks?

2023-05-21 Thread Alex via Postfix-users
Hi, On Sun, May 21, 2023 at 4:41 PM Wietse Venema via Postfix-users < postfix-users@postfix.org> wrote: > Alex via Postfix-users: > > > > I'd say, start with one instance per domain. The 'cost' of doing so > > > > is really small. > > > > > &

[pfx] Re: per-domain header/body checks?

2023-05-21 Thread Alex via Postfix-users
Hi, On Sun, May 21, 2023 at 12:39 PM Wietse Venema via Postfix-users < postfix-users@postfix.org> wrote: > Wietse Venema via Postfix-users: > > Alex via Postfix-users: > > > Hi, > > > I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be &

[pfx] Re: content filter sends mail twice

2023-05-21 Thread Alex via Postfix-users
Hi, Can I follow up on this? I can't figure out why always_bcc mail is being sent through the default content filter while mail designated for my domain-specific transport is sent through another in my multi-instance postfix config. I'd like the always_bcc user mail to still benefit from being

[pfx] per-domain header/body checks?

2023-05-21 Thread Alex via Postfix-users
Hi, I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be able to control which header and body checks apply to which domain in a specific instance. I'm looking for advice on the best way to do this. I have about ten domains right now, and would probably need a number of

[pfx] Re: content filter sends mail twice

2023-05-18 Thread Alex via Postfix-users
Viktor, On Thu, May 18, 2023 at 7:16 PM Viktor Dukhovni via Postfix-users < postfix-users@postfix.org> wrote: > On Thu, May 18, 2023 at 09:20:38AM -0400, Alex via Postfix-users wrote: > > > Maybe my issue is that the always_bcc user is going through a transport > at > &

[pfx] Re: per-domain sender_checks?

2023-05-18 Thread Alex via Postfix-users
Hi, > Is there a way to control smtpd_recipient_restrictions on a per-domain > > basis so I can relax some of these restrictions for cases like this, > > instead of a more reactive approach where I'm always adding > > sender_checks.pcre entries? > > Instead of > > /etc/postfix/main.cf: >

[pfx] Re: content filter sends mail twice

2023-05-18 Thread Alex via Postfix-users
, May 18, 2023 at 8:00 AM Alex wrote: > > > On Thu, May 18, 2023 at 4:39 AM Matus UHLAR - fantomas via Postfix-users < > postfix-users@postfix.org> wrote: > >> On 17.05.23 22:11, Alex via Postfix-users wrote: >> >I'm using postfix (postmulti) with amavisd and

[pfx] Re: content filter sends mail twice

2023-05-18 Thread Alex via Postfix-users
On Thu, May 18, 2023 at 4:39 AM Matus UHLAR - fantomas via Postfix-users < postfix-users@postfix.org> wrote: > On 17.05.23 22:11, Alex via Postfix-users wrote: > >I'm using postfix (postmulti) with amavisd and trying to have separate > >content filters based on the domain so

[pfx] content filter sends mail twice

2023-05-17 Thread Alex via Postfix-users
Hi, I'm using postfix (postmulti) with amavisd and trying to have separate content filters based on the domain so I can make decisions on the destiny of the email from within amavisd. Currently all mail is processed by the same amavisd policy_bank. The problem now is that mail is being sent

[pfx] Re: per-domain sender_checks?

2023-05-16 Thread Alex via Postfix-users
Hi, On Tue, May 16, 2023 at 4:16 PM Viktor Dukhovni via Postfix-users < postfix-users@postfix.org> wrote: > On Tue, May 16, 2023 at 11:27:52AM -0400, Alex via Postfix-users wrote: > > > > > $ host info.apr.gov.rs > > > > Host info.apr.gov.rs not found: 2(

[pfx] Re: per-domain sender_checks?

2023-05-16 Thread Alex via Postfix-users
Hi, > I have a postfix-3.7.3 fedora37 system and have a few users who want me to > > disable reject_non_fqdn_sender because it seems many of their users have > > DNS problems. For example, email from nore...@info.apr.gov.rs fails to > > resolve with: > > > > $ host info.apr.gov.rs > > Host

[pfx] per-domain sender_checks?

2023-05-16 Thread Alex via Postfix-users
Hi, I have a postfix-3.7.3 fedora37 system and have a few users who want me to disable reject_non_fqdn_sender because it seems many of their users have DNS problems. For example, email from nore...@info.apr.gov.rs fails to resolve with: $ host info.apr.gov.rs Host info.apr.gov.rs not found:

[pfx] postscreen and checking proper operation

2023-05-01 Thread Alex via Postfix-users
Hi, I have postscreen implemented on postfix-3.7.3 on fedora37, and not sure I understand if it's working properly. Sometimes I see the postscreen/dnsblog combination ending with a simple DISCONNECT. In this case, it met the 8-point threshold to be rejected, but appears to only received a

[pfx] Re: Sender address rejected, but domain is found?

2023-04-25 Thread Alex via Postfix-users
Hi, On Tue, Apr 25, 2023 at 1:03 PM Gerald Galster via Postfix-users < postfix-users@postfix.org> wrote: > Hi, I realize this is probably one of the most frequently asked questions, > but I really can't figure out why this was rejected. > > Apr 25 12:06:01 petra postfix-226/smtpd[592344]: