Since a couple of days, notifications are not sent from JTrac. We use JTrac
version 2.2.0-dev11
A few weeks ago our mail provider released the following statement:
Access without encryption and TLS 1.0 and 1.1 are no longer accepted for our
POP3, IMAP and SMTP email servers
Dear customer, Access without encryption and TLS 1.0 and 1.1 are no longer
accepted for our POP3, IMAP and SMTP email servers. If you have problems
receiving or sending emails through an external email program, the The
source of the problem could be access without encryption or through obsolete
protocols such as TLS 1.0 or 1.1 to your email account. For security
reasons, we now only support the latest encryption protocols, TLS 1.2 and
TLS 1.3. In order for the transmission of emails between your devices or
email programs and our email servers to continue working, they must support
the TLS 1.2 protocol or higher and encryption (SSL/TLS) must be activated.
I'm not sure what version 2.2.0-dev11 is - there never has been such a
version from the official source. so if you got that elsewhere, that would
be the place to ask questions about it.
official versions, such as the current release version 2.2.1, use
javamail's settings for secure mail access. jtrac admins have access to
those from the Options page. check with your mail provider which ones are
appropriate. they don't allow the precise selection of the protocol suite
to be used - that's negotiated under the hood. if the provider has turned
off older ones, the newer ones should be used automatically , provided the
settings are correct .
you may also want to run the jvm with the mail.debug flag set to true, so
you'll get lots of debugging output about what Javamail does .
Since a couple of days, notifications are not sent from JTrac. We use JTrac
version 2.2.0-dev11
A few weeks ago our mail provider released the following statement:
Access without encryption and TLS 1.0 and 1.1 are no longer accepted for
our
POP3, IMAP and SMTP email servers
Dear customer, Access without encryption and TLS 1.0 and 1.1 are no longer
accepted for our POP3, IMAP and SMTP email servers. If you have problems
receiving or sending emails through an external email program, the The
source of the problem could be access without encryption or through
obsolete
protocols such as TLS 1.0 or 1.1 to your email account. For security
reasons, we now only support the latest encryption protocols, TLS 1.2 and
TLS 1.3. In order for the transmission of emails between your devices or
email programs and our email servers to continue working, they must support
the TLS 1.2 protocol or higher and encryption (SSL/TLS) must be activated.
Ok I understand, the truth is I don't know where that version came from, I am the new IT manager in the company where I work and nobody gives me an account of the person who installed that version at the time.
install the official version 2.2.1 on a new server.
I have a detail regarding the words with accents, the system puts them as symbols despite having defined the language es_MX in jtrac as default. Are there any additional adjustments I need to make?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I vaguely recall there being a bug with i18n, possibly post-2.2.1. I'm
traveling right now ,and can't look into it , but I'll take a look over the
weekend or early next week .
Ok I understand, the truth is I don't know where that version came from, I
am the new IT manager in the company where I work and nobody gives me an
account of the person who installed that version at the time.
install the official version 2.2.1 on a new server.
I have a detail regarding the words with accents, the system puts them as
symbols despite having defined the language es_MX in jtrac as default. Are
there any additional adjustments I need to make?
There was indeed a bug having to do with accents post-2.2.1. I just tested the current development version, and it sends emails with accented characters fine, both in the subject and the details.
So you can either build the development version from the source code (it's stable), or use 2.3 when it comes out (which should be within in the next few weeks).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello:
Since a couple of days, notifications are not sent from JTrac. We use JTrac
version 2.2.0-dev11
A few weeks ago our mail provider released the following statement:
Access without encryption and TLS 1.0 and 1.1 are no longer accepted for our
POP3, IMAP and SMTP email servers
Dear customer, Access without encryption and TLS 1.0 and 1.1 are no longer
accepted for our POP3, IMAP and SMTP email servers. If you have problems
receiving or sending emails through an external email program, the The
source of the problem could be access without encryption or through obsolete
protocols such as TLS 1.0 or 1.1 to your email account. For security
reasons, we now only support the latest encryption protocols, TLS 1.2 and
TLS 1.3. In order for the transmission of emails between your devices or
email programs and our email servers to continue working, they must support
the TLS 1.2 protocol or higher and encryption (SSL/TLS) must be activated.
Does JTrac 2.2.0-dev11 support TLS 1.2 or 1.3?
Greetings.
I'm not sure what version 2.2.0-dev11 is - there never has been such a
version from the official source. so if you got that elsewhere, that would
be the place to ask questions about it.
official versions, such as the current release version 2.2.1, use
javamail's settings for secure mail access. jtrac admins have access to
those from the Options page. check with your mail provider which ones are
appropriate. they don't allow the precise selection of the protocol suite
to be used - that's negotiated under the hood. if the provider has turned
off older ones, the newer ones should be used automatically , provided the
settings are correct .
you may also want to run the jvm with the mail.debug flag set to true, so
you'll get lots of debugging output about what Javamail does .
On Tue, 6 Sept 2022, 01:03 Hugo Nevarez, hnevarez@users.sourceforge.net
wrote:
Ok I understand, the truth is I don't know where that version came from, I am the new IT manager in the company where I work and nobody gives me an account of the person who installed that version at the time.
install the official version 2.2.1 on a new server.
I have a detail regarding the words with accents, the system puts them as symbols despite having defined the language es_MX in jtrac as default. Are there any additional adjustments I need to make?
I vaguely recall there being a bug with i18n, possibly post-2.2.1. I'm
traveling right now ,and can't look into it , but I'll take a look over the
weekend or early next week .
Ulf
On Tue, 13 Sept 2022, 21:33 Hugo Nevarez, hnevarez@users.sourceforge.net
wrote:
There was indeed a bug having to do with accents post-2.2.1. I just tested the current development version, and it sends emails with accented characters fine, both in the subject and the details.
So you can either build the development version from the source code (it's stable), or use 2.3 when it comes out (which should be within in the next few weeks).