[pfx] Re: IMPORTANT, drop "resolve [!UNAVAIL=return]" from Linux nsswitch.conf files
On Mon, Apr 22, 2024 at 03:50:34PM GMT, Viktor Dukhovni via Postfix-users wrote: > and this (specifically, !UNAVAIL=return) turns soft DNS failures into > hard errors. > > The solution, on any production mail server, is to remove (with > prejudice) > > resolve [!UNAVAIL=return] This doesn't sound right... All that says is once you've gotten a response from systemd-resolve that the lookup chain should end, which, if it's actually running, is what you want. As the lookup via DNS already happened there after all, there's no reason to repeat it. It doesn't have an impact whatsoever on soft vs hard fail, resolve either gives you the domain after the lookup or whatever response it got from the upstream server (DNS or what have you). ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
Re: bad BCC address
On Wed, Nov 09, 2022 at 08:05:20AM +, pat...@patpro.net wrote: > Does the error mean my BCC address must be me0example.org instead of > me0foo.example.org? Ehr, you do realize that you have 0's where you'd expect an @ yes?
Re: FYI: ArchLinux modularizes Postfix packages (Arch Users should read this)
Arch users should primarily read the output of pacman... > WARNING: The following features are now only available via optdepends: cdb, > ldap, lmdb, mysql, pcre, pgsql, sqlite. Cheers, Reto
Re: Reject Chinese mail
On 21 November 2019 07:11:43 CET, Viktor Dukhovni wrote: >Blocking mail by language risks false-positives and should be generally >avoided, but it is not evil. Blocking based on geolocation / domain endings is something I seriously despise. Email is decentralized for a reason, blocking huge portions of it due to spammers abusing a few *is* evil in my opinion. I'm fed up with all those threads with people who want to block the most amount of people possible just because they personally happen to be lucky enough to live in a different country than the usual botnets come from or could still buy a .com or similar domain prior to the namespaces getting exhausted. The point I wanted to make is that we should not let the history repeat itself (yet again...) especially in the political climate we happen to be in. My intention wasn't to slur anyone, don't get me wrong there. I apologise if that was the case.
Re: Reject Chinese mail
On 21 November 2019 05:51:56 CET, merr...@fn.de wrote: >We speak not Chinese, do you think if it is possible to reject all mails from >China? Apparently you also don't speak English properly. Do you want people to spam block the full .de domain because of that? Think hard before you block 1.5 billion people, some of which may participate on this list and could give you support if you weren't blocking them. Could you do that? Sure. Is it worth blocking by association due to where one grew up? Hm, didn't Germany learn its lesson yet somewhen in the 50s don't you think?
Re: Big problem with this mailing list and Majordomo regarding DMARC
On Sat, Apr 20, 2019 at 07:31:06AM -0400, Richard Damon wrote: > Where the issue comes is with DMARC, which restricts the DKIM protocol > to be aligned with the From line of the message, and thus the MLM can't > make the message pass the DMARC settings of the sending domain. It is > DMARC which breaks the traditional operation of a MLM, and the use of > which implies that the sender should not be using such tools. Now that's a bit dramatic isn't it? A mailing list *can* work with dmarc just fine if it doesn't modify the protected headers. That doesn't seem to be particularely complicated assuming Headers like List-Unsubscribe et al can still be added. Just don't modify the subject and the body and you should be fine.
Postfix MySQL Map (check_sender_access and check_recipient_access)
Hi Postfix programmers/users Does anyone of you thought to implement in the postfix mysql map the ability to query for recipient and sender and not just sender or reciient for check_recipient_access and check_sender_access. Cause my goal is to create whitelists for specific users based on their email. The only solution i found is to create an postfix policy deamon. I want to solve this with mysql and not static with postfix restriction classes.
