- Message from Viktor Dukhovni -
Date: Mon, 22 Mar 2021 00:13:00 -0400
From: Viktor Dukhovni
Reply-To: postfix-users@postfix.org
Subject: Re: upgrade 2.10 - 3.3 config compatibility
To: postfix-users@postfix.org
On Mon, Mar 22, 2021 at 12:32:18PM +1000, Simon Wilson
> On Mar 22, 2021, at 12:53 AM, Phil Biggs wrote:
>
> Yes, I do have it configured as you say. I suspect that's a carry-over from
> an
> old pfSense package config I used as the basis for my first postfix server.
>
> As I don't have any known email problems at present, I'll wait
> for 3.6
Monday, March 22, 2021, 2:56:17 PM, Viktor Dukhovni wrote:
Viktor Dukhovni> On Mon, Mar 22, 2021 at 01:35:12PM +1100, Phil Biggs wrote:
>> Mar 21 14:50:35 postfix/postscreen[3804]: CONNECT from [18.205.72.90]:43471
>> to [192.168.11.2]:25
>> Mar 21 14:50:41 postfix/postscreen[3804]: PASS NEW [1
On Mon, Mar 22, 2021 at 12:32:18PM +1000, Simon Wilson wrote:
> I have temporarily set it at 0 after reading
> http://www.postfix.org/COMPATIBILITY_README.html to ensure that I pick
> up in logging if/when backwards-compatibility is triggered by the
> legacy settings as follows (from
> htt
On Mon, Mar 22, 2021 at 01:35:12PM +1100, Phil Biggs wrote:
> Mar 21 14:50:35 postfix/postscreen[3804]: CONNECT from [18.205.72.90]:43471
> to [192.168.11.2]:25
> Mar 21 14:50:41 postfix/postscreen[3804]: PASS NEW [18.205.72.90]:43471
> Mar 21 14:50:43 postfix/smtpd[3806]: connect from
> keeper-
- Message from Phil Biggs -
Date: Mon, 22 Mar 2021 14:34:44 +1100
From: Phil Biggs
Subject: Re: Double-bounce to ISP's server
To: postfix-users@postfix.org
Monday, March 22, 2021, 1:49:53 PM, Simon Wilson wrote:
Your IP address resolves back to aussiebb:
You need
Monday, March 22, 2021, 1:49:53 PM, Simon Wilson wrote:
> Your IP address resolves back to aussiebb:
> You need Aussie BB to setup your reverse DNS. I am with Aussie BB too:
Thanks, Simon. Now I see it!
I'm using Namecheap's name servers for my domain, with dynamic DNS updates
managed by p
- Message from Simon Wilson -
Date: Mon, 22 Mar 2021 12:49:53 +1000
From: Simon Wilson
Reply-To: si...@simonandkate.net
Subject: Re: Double-bounce to ISP's server
To: postfix-users@postfix.org
- Message from Phil Biggs -
Date: Mon, 22 Mar 2021 13:35:
- Message from Phil Biggs -
Date: Mon, 22 Mar 2021 13:35:12 +1100
From: Phil Biggs
Subject: Double-bounce to ISP's server
To: postfix-users@postfix.org
Hello all,
I'm running the postfix-sasl-3.5.8,1 pkg on FreeBSD 12.2-RELEASE-p4 GENERIC
Yesterday I plugged my public
Hello all,
I'm running the postfix-sasl-3.5.8,1 pkg on FreeBSD 12.2-RELEASE-p4 GENERIC
Yesterday I plugged my public IP into the mxtoolbox diags page and my logs
recorded this:
Mar 21 14:50:35 postfix/postscreen[3804]: CONNECT from [18.205.72.90]:43471 to
[192.168.11.2]:25
Mar 21 14:50:41 post
- Message from Viktor Dukhovni -
Date: Sun, 21 Mar 2021 21:15:36 -0400
From: Viktor Dukhovni
Reply-To: postfix-users@postfix.org
Subject: Re: upgrade 2.10 - 3.3 config compatibility
To: postfix-users@postfix.org
On Mon, Mar 22, 2021 at 10:17:16AM +1000, Simon Wilson
Dnia 21.03.2021 o godz. 18:43:40 Viktor Dukhovni pisze:
> On Sun, Mar 21, 2021 at 04:22:06PM +0100, Jaroslaw Rafa wrote:
>
> > If you want "maennerchor-kirchseeon.de" to be a local domain instead, you
> > need to make "the-grue.de" a virtual domain,
>
> This is not true. Multiple local domains a
Dnia 21.03.2021 o godz. 18:48:12 Viktor Dukhovni pisze:
> On Sun, Mar 21, 2021 at 05:14:39PM +0100, Jaroslaw Rafa wrote:
>
> >
> > /^examplelist.*@list\.maennerchor-kirchseeon\.de$/DUNNO
> > /@list\.maennerchor-kirchseeon\.de$/550 5.1.1 User unknown in local
> > recipient table
> > /^exa
On Mon, Mar 22, 2021 at 10:17:16AM +1000, Simon Wilson wrote:
> I've removed mynetworks_style based on improved knowledge as noted
> above; commented out append_dot_mydomain and relay_domains, have set
> compatibility_level to 0, and will monitor for messages.
The right compatibility level to
- Message from Matus UHLAR - fantomas -
Date: Sun, 21 Mar 2021 15:26:12 +0100
From: Matus UHLAR - fantomas
Subject: Re: upgrade 2.10 - 3.3 config compatibility
To: postfix-users@postfix.org
I have a well established 2.10 Postfix instance on 2.10 (CentOS7)
which is to b
It appears that Wietse Venema said:
>With uniform or compressed payloads, 256 bytes become 261 on average,
>thus it takes 978.9 bytes on average to expand into 998. Add CR
>and LF to the 998, and we have an expansion of 1000/978.9=1.022 or
>just a little over 2%.
That was my estimate too. I was
On Sun, Mar 21, 2021 at 07:25:31PM -0400, Demi Marie Obenour wrote:
> Another approach would be to create a “wrapped” MIME type that
> just wraps another message in base64. That has the advantage of
> working with multipart/signed et al. quoted-printable also has line
> continuations.
It is an
On 3/21/21 2:25 PM, Wietse Venema wrote:
> John Levine:
>> It appears that Wietse Venema said:
>>> Demi Marie Obenour:
How useful would BINARYMIME support be? It does mean that DKIM signing
would need to be done in the sending path, but I cannot think of any
reasons that would be a
On Sun, Mar 21, 2021 at 05:14:39PM +0100, Jaroslaw Rafa wrote:
>
> /^examplelist.*@list\.maennerchor-kirchseeon\.de$/DUNNO
> /@list\.maennerchor-kirchseeon\.de$/550 5.1.1 User unknown in local
> recipient table
> /^examplelist/550 5.1.1 User unknown in local recipient table
There's
On Sun, Mar 21, 2021 at 04:22:06PM +0100, Jaroslaw Rafa wrote:
> If you want "maennerchor-kirchseeon.de" to be a local domain instead, you
> need to make "the-grue.de" a virtual domain,
This is not true. Multiple local domains are fine.
--
Viktor.
On Sun, Mar 21, 2021 at 03:44:06PM +0100, Markus Grunwald wrote:
> I've set up postfix to serve mail for the local domain the-grue.de
> and for the virtual domains maennerchor-kirchseeon.de and
> goldschmiede-grunwald.de
>
> Now I'd like to run a mailman mailing list for
> maennerchor-kirchseeo
On Sun, Mar 21, 2021 at 10:21:54AM -0400, Wietse Venema wrote:
> > When using Postfix "smtpd_tls_security_level = encrypt" in main.cf
> > is it possible to make an exception for an incoming mail server
> > connection that does not support encryption?
>
> Use "smtpd_tls_security_level = may" and u
On Sun, Mar 21, 2021 at 04:38:56PM -0400, Wietse Venema wrote:
> With non-uniform input, or with input from a smaller alphabet, I
> expect that YMMV (the expansion can be less or more than 2%). For
> example 1000 null bytes expand into 2000 (100%), and when content
> requires no escaping, 998 byte
John Levine:
> It appears that Wietse Venema said:
> >> BINARYMIME avoids the 33% size increase of base64. If people cared
> >> about that, since every MTA now supports 8BITMIME it would be easy
> >> to invent a quoted-unprintable content-transfer-encoding which
> >> escaped only the few characte
It appears that Wietse Venema said:
>> BINARYMIME avoids the 33% size increase of base64. If people cared
>> about that, since every MTA now supports 8BITMIME it would be easy
>> to invent a quoted-unprintable content-transfer-encoding which
>> escaped only the few characters that are special in
John Levine:
> It appears that Wietse Venema said:
> >Demi Marie Obenour:
> >> How useful would BINARYMIME support be? It does mean that DKIM signing
> >> would need to be done in the sending path, but I cannot think of any
> >> reasons that would be a blocker. Having DKIM and DMARC built-in to
Hello Wietse and everyone,
Thank you all for your suggestions. I've kept the
reject_unknown_helo_hostname commented and things are working just
fine.
Thanks.
Dave.
On 3/21/21, ludic...@gmail.com wrote:
> I tried to work with reject_unknown_helo_hostname time and time again.
> But way too many
OK, I found the solution. So the command needed for me was:
user=debian-spamd argv=/usr/bin/spamc -u ${user} -f -e
/usr/sbin/sendmail -oi -f ${sender} ${recipient}
${recipient} returns the full email address whereas I just wanted the
bit before the @ sign (the user name).
user=d
On 21 Mar 2021, at 12:54, Steve Dondley wrote:
I'd like to configure postfix so the configuration settings in the
per-user configuration file at ~/.spamassassin/user_prefs get applied.
This user_prefs config file is used with the spamassassin command as
evidenced with spamassassin -D < spam.t
spamassassin unix - n n - - pipe
user=debian-spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail
-oi -f ${sender} ${recipient}
I modified the above to:
user=debian-spamd argv=/usr/bin/spamc -u ${recipient} -f -e
/usr/sbin/sendmail -oi -f ${sender} ${rec
It appears that Wietse Venema said:
>Demi Marie Obenour:
>> How useful would BINARYMIME support be? It does mean that DKIM signing
>> would need to be done in the sending path, but I cannot think of any
>> reasons that would be a blocker. Having DKIM and DMARC built-in to
>> Postfix would be a n
I'd like to configure postfix so the configuration settings in the
per-user configuration file at ~/.spamassassin/user_prefs get applied.
This user_prefs config file is used with the spamassassin command as
evidenced with spamassassin -D < spam.txt. But as far as I can tell, the
user_prefs fil
Dnia 21.03.2021 o godz. 15:44:06 Markus Grunwald pisze:
> Now I'd like to run a mailman mailing list for
> maennerchor-kirchseeon.de. Their mailing list tells me, that to
> avoid problems...
>
> >Whatever you set for VIRTUAL_MAILMAN_LOCAL_DOMAIN must be a local
> >domain, not a virtual domain.
>
Dnia 21.03.2021 o godz. 15:44:06 Markus Grunwald pisze:
> So I'd like to have maennerchor-kirchseeon.de as local domain and
> the-grue.de as virtual domain. I thought it might be as simple as
> s/the-grue.de/maennerchor-kirchseeon.de/ in these two lines from
> main.cf:
>
> myhostname = the-grue.d
Hello,
I've set up postfix to serve mail for the local domain the-grue.de
and for the virtual domains maennerchor-kirchseeon.de and
goldschmiede-grunwald.de
Now I'd like to run a mailman mailing list for
maennerchor-kirchseeon.de. Their mailing list tells me, that to
avoid problems...
Wha
Matus UHLAR - fantomas:
> >With those set, all services in master.cf explicitly chroot=n, and
> >compatibility_level set to 99
>
> don't do this. You never know what changes in the future and will require
> your intervention.
Indeed. Postfix 3.6 comes with a handful breaking changes. The
compat
I have a well established 2.10 Postfix instance on 2.10 (CentOS7)
which is to be migrated to a new machine running Postfix 3.3 (on
RHEL8).
I've been reading http://www.postfix.org/COMPATIBILITY_README.html,
and from what I can see the backward compatibility issues I may run
into are (with exi
Henry Liu:
> When using Postfix "smtpd_tls_security_level = encrypt" in main.cf
> is it possible to make an exception for an incoming mail server
> connection that does not support encryption?
Use "smtpd_tls_security_level = may" and use reject_plaintext_session
in smtpd_sender_restrictions.
/etc
When using Postfix "smtpd_tls_security_level = encrypt" in main.cf is it
possible to make an exception for an incoming mail server connection that does
not support encryption?
Thank you
Henry
- Message from Simon Wilson -
Date: Fri, 19 Mar 2021 13:40:11 +1000
From: Simon Wilson
Reply-To: si...@simonandkate.net
Subject: upgrade 2.10 - 3.3 config compatibility
To: postfix-users@postfix.org
I have a well established 2.10 Postfix instance on 2.10 (CentOS7)
I tried to work with reject_unknown_helo_hostname time and time again.
But way too many regular servers don't comply.
It does not seem as there is much progress.
OTOH, reject_invalid_helo_hostname does a good job in my realm of mail traffic.
I have yet to see a complaint about turning these away.
41 matches
Mail list logo
