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
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?
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
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 por
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 b
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 bre
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
