e, I will follow what Viktor suggests: monitoring
and dynamically deferring emails, and notify me of the issue while at
it. The email rate on this system should be low enough that the monitor
will notice the issue before any significant volume went through.
Regards,
--
Vincent Pelletier
ERP5 - op
stfix just stop sending emails altogether in such case,
than send them from an unexpected ip: a delay is preferable to me to
uncertainty as to how the emails were processed by recipient SMTPs.
Is there something else I should set so postfix stops falling back to
no binding ?
Regards,
--
Vi
opened on their tracker:
https://bugs.kde.org/show_bug.cgi?id=434234
Regards,
--
Vincent Pelletier
GPG fingerprint 983A E8B7 3B91 1598 7A92 3845 CAC9 3691 4257 B0C1
Mechanisms must ignore callbacks with id's they don't recognize.
*/
unsigned long id;
int (*proc)(void); /* Callback function. Types of arguments vary by 'id'
*/
void *context;
} sasl_callback_t;
So any callback "proc" member has to be explicitly cast as any
parameter at all will trigger a warning. Which seems an unfortunate
decision to my very limited C experience, but is not postfix'
responsibility.
Regards,
--
Vincent Pelletier
GPG fingerprint 983A E8B7 3B91 1598 7A92 3845 CAC9 3691 4257 B0C1
On Wed, 10 Mar 2021 00:31:18 +, Vincent Pelletier
wrote:
> Note how the caller (here, libkdexoauth2.so) is calling with:
> - context
> - id
> - result
> - null
> but xsasl_cyrus_client_get_passwd's signature is:
> sasl_conn_t *conn, void *context, int id, sasl_
On Wed, 10 Mar 2021 00:31:18 +, Vincent Pelletier
wrote:
> While debugging an smtp process segfault during sasl authentication
> with gmail servers in xoauth2 (xoauth2 authentication which I am in the
> process of setting up, so I have no idea if this is a recent
> regression)
lly, I'm sending this email using the very same postfix build,
using libxoauth2.so from
https://github.com/moriyoshi/cyrus-sasl-xoauth2
and with libkdexoauth2.so.3 out of the way, and authentication worked.
I do not like magic in my authentication.
Regards,
--
Vincent Pelletier
GPG fingerprint 983A E8B7 3B91 1598 7A92 3845 CAC9 3691 4257 B0C1
the contract: sender can complain that
recipient is losing their emails, which prevents them from fulfilling
the contract. Recipient puts their email admin in relation with the
unhappy sender, they are now not anonymous anymore, useful details get
exchanged, the badmouthing DNSBL nobody has a contract with anyway is
finally cast away, the cowboy gallops towards the setting sun, the end.
--
Vincent Pelletier
list (without even realising it) ?
Sure, they can count on it and drink water.
--
Vincent Pelletier
o monitor on-hold postfix queue.
The alternative would be "on tunnel up" script to release all on-hold
emails, which will eventually bite me if I ever have other reasons to
put mails on-hold.
Regards,
--
Vincent Pelletier
ntain and monitor, and an extra
SMTP hop, all of which I would very much like to avoid.
Has the situation evolved since then (not that I can find in the
documentation) ?
Is there a reason for it not to evolve ?
Regards,
--
Vincent Pelletier
leasing the source, it's really an ugly milter, but
I'm putting the idea out here - and maybe I'll learn it has already been
done and properly implemented...
Regards,
--
Vincent Pelletier
umented ?
Is it a small-enough implementation detail that it does not justify
documenting it (which would be perfectly fine for me) ?
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
> Google for "dmarc mailman fix".
Thanks a lot for the pointers.
It's good to know there is a mailman-level fix already, it will be very
useful once I updated this ageing setup.
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
smime.p7s
Description: S/MIME cryptographic signature
this part now does work as I intended.
I still have to check envelope sender value, and see if it matters.
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
smime.p7s
Description: S/MIME cryptographic signature
ke he's
> violating some really important rfc's.
This is my understanding of the issue so far, indeed.
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
smime.p7s
Description: S/MIME cryptographic signature
@foo.com pushes to their SMTP a mail for
nob...@nexedi.com - which they rightfully reject as a relay attempt.
Or I botched my configuration and/or missed an extra option.
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
smime.p7s
Description: S/MIME cryptographic signature
gle_from
socket: malformed response
What did I do wrong ?
Can I do anything without having to upgrade right now ?
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
smime.p7s
Description: S/MIME cryptographic signature
h both roles would need your
initial suggestion (which I setup successfully before noticing the
second reply).
Regards,
--
Vincent Pelletier
r than
smtp_tls_security_level = may
without also having separate transports (if I understand correctly).
So if I do not set noplaintext and someday one of the
usually-TLS-enabled relays doesn't offer TLS (config hickup...),
postfix will AUTH.
--
Vincent Pelletier
e, I would like to keep plaintext auth disallowed anywhere else.
Regards,
--
Vincent Pelletier
21 matches
Mail list logo
