On 9/04/23 14:02, tom--- via Postfix-users wrote:
I have this setting in main.cf:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
check_policy_service unix:private/policyd-spf,
reject_rbl_client zen.spamhaus.org,
Sunday, April 9, 2023, 12:02:20 PM, tom--- via Postfix-users wrote:
> I have this setting in main.cf:
> smtpd_recipient_restrictions =
> permit_mynetworks,
> permit_sasl_authenticated,
> reject_unauth_destination,
> check_policy_service unix:private/policyd-spf,
>
On Sun, Apr 09, 2023 at 09:35:49AM +0800, tom--- via Postfix-users wrote:
> >> 2. Content-Transfer-Encoding: 7bit
> >
> > The 2nd is more of a property assertion, than an encoding. The
> > MIME-part content is transmitted as-is, but is asserted to consist
> > entirely of 7-bit octets (i.e.
greetings,
(1) reject_unknown_helo_hostname:
Reject the request when the HELO or EHLO hostname has no DNS A or MX
record.
This seems reasonable.
(2) reject_unknown_client_hostname:
Reject the request when 1) the client IP address->name mapping fails, or
2) the name->address mapping fails,
I have this setting in main.cf:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
check_policy_service unix:private/policyd-spf,
reject_rbl_client zen.spamhaus.org,
reject_rbl_client bl.spamcop.net
When I sent message from
And there is a discussion on stackoverflow:
https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit
regards.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
2. Content-Transfer-Encoding: 7bit
The 2nd is more of a property assertion, than an encoding. The
MIME-part content is transmitted as-is, but is asserted to consist
entirely of 7-bit octets (i.e. still 8-bit octets, but in the range
0–127). Similarly, the "8bit" transfer encoding is also
HUGE RETRACTION: I've really messed this up...
At the time of the HELO/EHLO command, SMTPD_FLAG_SMTPUTF8 should always
be false, that feature may be negotiated after HELO/EHLO.
As such, the UTF8 handling code of reject_non_fqdn_hostname is ALWAYS
DISABLED during HELO/EHLO and so
Viktor Dukhovni via Postfix-users:
> Apparently, reading RFC5321 and RFC5322 is too tedious.
Reading RFCs is so old-school. It's much easier to be ignorant.
Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send
> On Apr 8, 2023, at 13:15, Viktor Dukhovni via Postfix-users
> wrote:
>
> On Sat, Apr 08, 2023 at 12:16:30PM -0700, Doug Hardie via Postfix-users wrote:
>
Are there any others and how close am I?
>>>
>>>
>>>
On Sat, Apr 08, 2023 at 12:16:30PM -0700, Doug Hardie via Postfix-users wrote:
> >> Are there any others and how close am I?
> >
> >
> > https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-7
>
> Wow, I never would have guessed there would be that many.
> On Apr 8, 2023, at 11:59, Viktor Dukhovni via Postfix-users
> wrote:
>
> On Sat, Apr 08, 2023 at 11:51:06AM -0700, Doug Hardie via Postfix-users wrote:
>
>> A couple of questions. Looking in the postfix generated Received:
>> header, the SMTP id often has a few other letters included:
On Sat, Apr 08, 2023 at 11:51:06AM -0700, Doug Hardie via Postfix-users wrote:
> A couple of questions. Looking in the postfix generated Received:
> header, the SMTP id often has a few other letters included: ESMTPA
> etc. I am guessing that the extra letters mean:
>
> E - EHLO used
A couple of questions. Looking in the postfix generated Received: header, the
SMTP id often has a few other letters included: ESMTPA etc. I am guessing
that the extra letters mean:
E - EHLO used rather the HELO
S - SSL was used in the connection
A - the originator
On Sat, Apr 08, 2023 at 11:49:49AM +1000, Sean Gallagher via Postfix-users
wrote:
> I think the outcome of the discussion in this thread was that
> valid_utf8_hostname() really has no "official" use case.
Not all hostnames are HELO hostnames. The domain part of an email
address is a
On Sat, Apr 08, 2023 at 02:59:49PM +0800, tom--- via Postfix-users wrote:
> 1. use MIME encoding for 8bit chars
That would be either quoted-printable or base64:
https://www.iana.org/assignments/transfer-encodings/transfer-encodings.xhtml
applicable to "leaf" MIME entities, but not
tom--- via Postfix-users skrev den 2023-04-08 14:57:
If message has image included, or has UTF8 chars, is base64 encoding
must be used? Thank you again.
utf-8 is 7bit, so no
The same is true for HTML entries, many news mails have utf8 and
qoutedprintble, and always its HTML, hmm:)
there is
raf via Postfix-users:
> > From reading the code, these two restrictions seem equivalent except when
> > SMTPUTF8 extension is used.
> > when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will convert a
> > hostname containing UTF to an internationalized domain name
> > before checking.
If message has image included, or has UTF8 chars, is base64 encoding
must be used? Thank you again.
On 2023-04-08 19:58, Wietse Venema via Postfix-users wrote:
tom--- via Postfix-users:
Hello,
1. use MIME encoding for 8bit chars
I suppose you mean that you encode message header or boody
tom--- via Postfix-users writes:
> Hello,
>
> for a mailbox user, such as my one t...@myposts.ovh, where to define
> the forwarding? for example, I want messages sent to this mailbox to
> be copied to gmail.
Hellow tom,
DKIM is good for you if you are domain's owner.
This is general
tom--- via Postfix-users:
> Hello,
>
> 1. use MIME encoding for 8bit chars
I suppose you mean that you encode message header or boody content
using Base64 or Quoted-Printable.
> 2. Content-Transfer-Encoding: 7bit
Both base64 and quoted-printable are 7-bit transfer encodings.
> Do they mean
Hello,
1. use MIME encoding for 8bit chars
2. Content-Transfer-Encoding: 7bit
Do they mean the same stuff?
Should I use 8bit encoding, or 7bit? If I am composing the Chinese
message.
Thank you.
Tom Reed
___
Postfix-users mailing list --
22 matches
Mail list logo
