Re: SMTPUTF8
On Tue, Dec 27, 2022, Puru Shartha wrote: > Based on my current understanding, only Postfix+Courier seems to support > users with UTF8 requirements. sendmail has it too: 8.17.1/8.17.1 2021/08/17 Experimental support for SMTPUTF8 (EAI, see RFC 6530-6533) is available when using the compile time option USE_EAI
Re: what does "from=<>" mean?
On Wed, Jul 06, 2022, Harald Dunkel wrote: > I see quite a number of EMails mentioned in /var/log/maillog with a > string "from=<>", e.g. Maybe that's due to MAIL From:<> ?
Re: Encryption for OpenSMTPD on VPS
On Sun, Apr 03, 2022, Josey Smith wrote: > I'm currently setting up a somewhat unique personal email server. I > have a local server (Raspberry Pi) and a remote server (VPS running > OpenBSD). Emails are sent to the remote server and are then relayed to > my local server. When I send an email it goes from my local server to If your local server is online "most of the time" then you could use: - a proxy instead of an MTA relay on the VPS. - some VPN between the remote and your local server. i.e., don't store the mail ever on the VPS.
poolp: not sending e-mail using TLS
Why does poolp does not send mail after STARTTLS but then sends it without TLS? First: client_ip=199.247.13.58, client_name=mx-out.poolp.org. starttls=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384, cipher_bits=256, verify=NOT and then it aborts: status=no_TA_started next it sends the mail without TLS: client_ip=199.247.13.58, client_name=mx-out.poolp.org. mail= rcpt= msgid=<951cde3e200270a677e093218346e...@mostlybsd.com> -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: common format for maillog lines?
On Thu, Oct 08, 2020, Harald Dunkel wrote: > Lines with a message id, and lines without. Very painful. Maybe that's because there are sessions and transactions in SMTP. Only the latter belong to a specific message, the former can contain multiple transactions, so logging a specific message id for them is somehow wrong (unless you restrict the MTA to perform only one transaction per session). PS: some MTAs have/log ids specific to each part of the protocol: session, transaction, recipient (and even specific to the server and client side if needed).
Re: "bouncing messages from ..." (was: request (privately) for maillog)
Happened again for me. Anyone else?
design or error: no transaction started by opensmtpd
Sometimes I see these warnings in my logs status=no_TA_started which is similar to sendmail's notice "client did not issue MAIL/..." and surprisingly some are from mail.openbsd.org. Is that by design of opensmtpd (open a session because there's a message waiting but by the time the new session is established that message has been sent over a different connection) or is that some kind of error?
Re: "bouncing messages from ..." (was: request (privately) for maillog)
On Mon, Feb 24, 2020, Peter J. Philipp wrote: > I got another "bouncing messages from misc@opensmtpd.org" message. The Me too... and it's the second time I cannot find any error log about such a failed delivery (I asked for more info the previous time it happened but so far nobody replied) so together with this report it seems the problem might be on the server side?
