On Fri, Oct 11, 2019 at 02:17:16PM -0400, Viktor Dukhovni wrote:
> > that Gmail enabled SNI on their SMTP client is an indicator that using SNI
> > may not cause relevant trouble. But it's also known, Gmail is able to do
> > such stuff very selective to prevent damage.
>
> Indeed I am not
> What is the legitimate reason to use base64 encoded emails ?
i see quite a lot of legitimate email as base64 encoded
> Seems to me, it is only being used by spammers to complicate
> body_checks
any modern checker can and will decode base64 or indeed other message
details (the cost of doing so
On 17 Oct 2019, at 08:35, Bill Cole
wrote:
> On 17 Oct 2019, at 7:51, @lbutlr wrote:
>> Also., of course, some plaintext messages still have to be en=E2=85=BDoded=
>> .
>>
>> Like this one.
>
> But not always in Base64. :)
True, the sender rarely has any control over how the message is
micah anderson:
> Eray Aslan writes:
>
> > On Wed, Dec 19, 2018 at 02:36:50PM -0500, Viktor Dukhovni wrote:
> >> If there are no objections, I can change the default to "may" when
> >> TLS is compiled in.
> >
> > No objections for setting smtp_tls_security_level. Thanks for your
> > effort.
>
Eray Aslan writes:
> On Wed, Dec 19, 2018 at 02:36:50PM -0500, Viktor Dukhovni wrote:
>> If there are no objections, I can change the default to "may" when
>> TLS is compiled in.
>
> No objections for setting smtp_tls_security_level. Thanks for your
> effort.
I just wanted to circle back to
On 10/17/2019 5:19 AM, (lists) Denis BUCHER wrote:
I suppose that it would be more correct this way :
* smtpd_recipient_restrictions = check_recipient_access
hash:/etc/postfix/recipient_access
* smtpd_relay_restrictions = permit_mynetworks
permit_sasl_authenticated
Use a HASH table before implementing this in SQL.
/etc/postfix/main.cf:
transport_maps =
hash:/etc/postfix/transport ..whatever you already have...
/etc/postfix/transport:
u...@test.comsmtp:[the old machine]
# postmap hash:/etc/postfix/transport
# postfix reload
# postmap
On 17 Oct 2019, at 7:51, @lbutlr wrote:
Also., of course, some plaintext messages still have to be
en=E2=85=BDoded=
.
Like this one.
But not always in Base64. :)
Many clients only do QP or only do Base64 when the content makes it
necessary, some make a judgment call based (usually) on the
On 17 Oct 2019, at 4:48, Fourhundred Thecat wrote:
Hello,
I would like to ask what the Postfix community thinks about base64
encoded emails.
They are necessary.
What is the legitimate reason to use base64 encoded emails ?
Any characters outside of the US-ASCII set must be encoded using
On 10/17/19 4:48 AM, Fourhundred Thecat wrote:
> Hello,
>
> I would like to ask what the Postfix community thinks about base64
> encoded emails.
>
> What is the legitimate reason to use base64 encoded emails ?
>
> Seems to me, it is only being used by spammers to complicate body_checks
>
> Would
On 17 Oct 2019, at 02:48, Fourhundred Thecat <400the...@gmx.ch> wrote:
> I believe email should be plaintext. I don't like HTML emails either. If
> somebody feels that his message needs fancy formatting, he should send
> it as pdf attachment. But emails should stay plaintext.
Have fun with that
Asai:
>
> > The following uses two transport maps and no changes in
> > relay_recipient_maps:
> >
> > Assuming that both machines will accept mail for every
> > user@the-domain-in-question:
> >
> > - One transport map on the new machine, that sends mail for
> > non-migrated
Le 17.10.2019 à 00:16, Noel Jones a écrit :
On 10/16/2019 4:48 PM, (lists) Denis BUCHER wrote:
Hello everyone,
I read a lot of emails on this ML and on the web without finding the
solution, or I do something wrong.
I just want that all emails to a specific recipient are put on hold.
I
Dnia 17.10.2019 o godz. 10:48:21 Fourhundred Thecat pisze:
>
> I believe email should be plaintext. I don't like HTML emails either. If
> somebody feels that his message needs fancy formatting, he should send
> it as pdf attachment. But emails should stay plaintext.
I second that emails should
Dnia 16.10.2019 o godz. 15:46:19 Asai pisze:
>
> Our organization is deploying a new upgraded Postfix server and
> we're looking for various options to migrate users from the old to
> the new. One possibility, we hope, is to do it on a per user basis
> rather than doing it all at once for a
Hi
on 2019/10/17 16:48, Fourhundred Thecat wrote:
I believe email should be plaintext. I don't like HTML emails either. If
somebody feels that his message needs fancy formatting, he should send
it as pdf attachment. But emails should stay plaintext.
non-latin message body should be encoded
Hello,
I would like to ask what the Postfix community thinks about base64
encoded emails.
What is the legitimate reason to use base64 encoded emails ?
Seems to me, it is only being used by spammers to complicate body_checks
Would it be crazy to want to configure Postfix to not accept base64 ?
17 matches
Mail list logo