Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Would be for another room, but any pictures worth sharing yet of what is coming?
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Fri Apr 12 2024 11:05:58 EDT from IGnatius T Foobar Subject: Re: mail delivery errors - message ID header not RFC 5322 conformSo it can be circumscribed: The problem occurs using mail clients like
Thunderbird or K-9 Mail for writing and sending emails via SMTP.
You are absolutely correct, and I am now able to reproduce the problem. When an external SMTP agent submits a message with the message ID in angle brackets, the bracket on the right is not properly stripped.
What an excellent troubleshoot and bug report. We'll get this fixed right away.
I would like to thank you very much for the quick and professional support!
Some large software companies could take a role model here.
It's great if CalDAV would be included in Citadel. I use it with separate software, which i could quit.
For implementing the update: Is it possible to reinstall the easy install routine on a running raspberry, if citserver and webcit are stopped, without loosing the mail configuration and the content of the IMAP mail boxes? Or is the clean way a fresh installation of the whole system?
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Would be for another room, but any pictures worth sharing yet of what is coming?
Yes, thanks for asking :)
https://www.citadel.org/roadmap.html
Has a few screen shots of the Forum and Mail applets.
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
For implementing the update: Is it possible to reinstall the easy install
routine on a running raspberry, if citserver and webcit are stopped, without
loosing the mail configuration and the content of the IMAP mail boxes? Oris
the clean way a fresh installation of the whole system?
Yes, if you originally installed Citadel using the Easy Install method, you can run Easy Install again at any time to upgrade. Your existing data will be preserved.
Obviously you're going to take a backup first, of course.
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Sun Apr 14 2024 21:37:31 EDT from IGnatius T Foobar Subject: Re: mail delivery errors - message ID header not RFC 5322 conformFor implementing the update: Is it possible to reinstall the easy install
routine on a running raspberry, if citserver and webcit are stopped, without
loosing the mail configuration and the content of the IMAP mail boxes? Oris
the clean way a fresh installation of the whole system?
Yes, if you originally installed Citadel using the Easy Install method, you can run Easy Install again at any time to upgrade. Your existing data will be preserved.
Obviously you're going to take a backup first, of course.
Ok, thanks!
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
I must have missed that in previous talks. Tks.
How well will it resize to phones? We all know, for better or worse, that is what our new users will be using.
Sun Apr 14 2024 21:32:30 EDT from IGnatius T Foobar Subject: Re: mail delivery errors - message ID header not RFC 5322 conformWould be for another room, but any pictures worth sharing yet of what is coming?
Yes, thanks for asking :)
https://www.citadel.org/roadmap.html
Has a few screen shots of the Forum and Mail applets.
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
The intention for mobile is for it to behave like most other software does: when on a small screen, the sidebar is collapsed into a hamburger menu until you need it.
I am frustrated by the fact that we can't release little bits of this into production until it's finished, and I'm aware that this is the reason you're never supposed to start over (i.e. the Netscape effect -- although I still believe that Netscape failed because of hubris). I still stand by the decision though, because WebCit-classic has some very fundamental problems stemming from design decisions made more than 25 years ago.
We're also changing the fundamental approach of the user interface. Elements which made sense in 1996 when it was just a web version of a BBS client don't make sense today. Although it will still use the same Citadel Server, the user-facing experience will be a set of applications that all work together in a common framework. This is more in line with what the public expects in the current era.
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
But, sometimes its the only way.
Mon Apr 15 2024 13:53:27 EDT from IGnatius T Foobar Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
I am frustrated by the fact that we can't release little bits of this into production until it's finished, and I'm aware that this is the reason you're never supposed to start over
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Fri Apr 12 2024 17:41:07 EDT from IGnatius T Foobar Subject: Re: mail delivery errors - message ID header not RFC 5322 conformWhat an excellent troubleshoot and bug report. We'll get this fixed
right away.
...and right away is now. Citadel 999 is now available for download, in both Docker and Easy Install formats.
I guess the next release is going to have to be something really special since it'll be version 1000 :)
Both company servers, which rejected my SMTP written mails in version 998, accept it now with version 999.
Well done, succes across the board!
Subject: Re: mail delivery errors - message ID header not RFC 5322 conform
Both company servers, which rejected my SMTP written mails in version 998,
accept it now with version 999.
Glad to hear it! Thanks for using Citadel, and spread the word.
Hello All,
2 Questions, how do you search in these rooms to acoid repeating questions?
Any recommendations on SMART Hosts that is no google so that the sender appears under my domain and not the External SMTP Servers Domain?
Not a big deal, and cant say when it happened, but did the auto purge wax our contact list in the last year or so? Just curious.
Just happened to click in there by accident, noticed it was empty. Used to have a couple of entries. *shrug*
Good day,
just installed and I am receiving emails without issue but can't send.
I added my domain name Fully qualified domain name and local host alias (then restarted) but still not working. I assume its a configuration issue. I noticed that when I try to send it still uses my @raspberrypi and not my domain name
Any help would be appreicated
Good day,
I finally got email sending to work with using and external SMTP service but it will only process email from known address. I have auto forward setup and it forward emails to the service perfectly but maintains the original From address. Is there away to only have my domain email address in the from. My SMTP service only allows email from specific email address from my domain.
error.jpg (image/jpeg, 69532 bytes) [ View | Download ]
Attached is a sample of a forwarded email from Citadel and from Thunderbird. In the Citadel forward email it has included the original sender in the forward address line. In the Thunderbird forwarded email it has not. IMO Citadel is incorrectly forming the forward messages as it basically changing it instead of leaving intact.
Email1.jpg (image/jpeg, 111384 bytes) [ View | Download ]
(We're on it now, in fact. That's why I'm writing in DKIM signature support, which will appear in a new version of Citadel coming in just a few days.)
Hi,
I was checking my mail server (due to some domains saying they are no receiving my mail) and found that mxtoolbox reported that my server doesnt support TLS. How can I check this? I have a cert set up in the correct folder.
"Your SMTP email server does advertise support for TLS. After connecting to your mail server we issue an EHLO command to introduce ourselves and to request that your server announce which commands and protocols it supports. Your server's response did not include "250-STARTTLS" indicating TLS support."
thanks
Craig.