iobroker-community-adapters/iobroker.email

Send emails from ioBroker

iobroker.email's Issues

Make adapter ready for Admin v3

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

TLS ciphers broken

It seems that supported TLS ciphers are incomplete/outdated. After STARTTLS, the connector is unable to find a common cipher suite:

Error 140486513518400:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:802:

I am using https://github.com/buanet/docker-iobroker Docker image, not sure if this is related to outdated Node environment (as I am not a Node expert).

This is what the mailserver actually offers:

# for v in ssl2 ssl3 tls1 tls1_1 tls1_2; do
#  for c in $(openssl ciphers 'ALL:eNULL' | tr ':' ' '); do
#  openssl s_client -connect 1.2.3.4:25 -starttls smtp \
#  -cipher $c -$v <<< "Q" > /dev/null 2>&1 && echo -e "$v:\t$c"
#  done
# done

tls1:	ECDHE-ECDSA-AES256-SHA
tls1:	ECDHE-ECDSA-AES128-SHA
tls1:	ECDHE-ECDSA-DES-CBC3-SHA
tls1_1:	ECDHE-ECDSA-AES256-SHA
tls1_1:	ECDHE-ECDSA-AES128-SHA
tls1_1:	ECDHE-ECDSA-DES-CBC3-SHA
tls1_2:	ECDHE-ECDSA-AES256-GCM-SHA384
tls1_2:	ECDHE-ECDSA-AES256-SHA384
tls1_2:	ECDHE-ECDSA-AES256-SHA
tls1_2:	ECDHE-ECDSA-AES128-GCM-SHA256
tls1_2:	ECDHE-ECDSA-AES128-SHA256
tls1_2:	ECDHE-ECDSA-AES128-SHA
tls1_2:	ECDHE-ECDSA-DES-CBC3-SHA

Any other cipher suites are disabled for security reasons (which is quite common I believe).

emailadapter iobroker funktioniert nicht mit ionos

*habe die letzte Version erfolgreich installiert. die Testmail wird auch abgesendet ohne jegliche Fehlermeldung, aber es kommt nichts an. Der emailaccount bei ionos funktioniert mit anderen emailclients normal.
Adapterversion : 1.1.3
Js-Controller: 4.0.23
nodeversion: 16.5.1
OS: rasberrypi 4

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version:
• JS-Controller version:
• Node version:
• Operating system:

Additional context
Add any other context about the problem here.

Update stable version in repo from 1.2.1 to 1.2.2

Think about update stable version to 1.2.2

Version: stable=1.2.1 (47 days old) => latest=1.2.2 (30 days old)
Installs: stable=4282 (51.39%), latest=690 (8.28%), total=8332

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence

Update stable version in repo to 1.0.6

Think about update stable version to 1.0.6

Version: stable=1.0.5 (168 days old) => latest=1.0.6 (57 days old)
Installs: stable=2047 (56.72%), latest=953 (26.41%), total=3609
Click to edit

Please add NPM package to iobroker-community-adapters:developers team

verifying all repos and NPM ownership we noticed the NPM package of this repo is not part of our team.

please execute :

npm access grant read-write iobroker-community-adapters:developers iobroker.<adaptername>

or add the package by web :

https://www.npmjs.com/settings/iobroker-community-adapters/teams/team/developers/access

STARTTLS at userdefined SMTP configuration not working

Using version 1.1.2 & 1.1.1_
Problem: SMTP connection which requires STARTTLS is no longer working

When using user defined SMTP configuration there is no option to configure STARTTLS.
While downloading the system.adapter.email.0.json file I can see, that the option "requireTLS":false, is set, which is not working.
After Rolling back to version 1.1.0 it's working again.

web.de does not work

It is not possible to send emails from web.de.
Server: smtp.web.de
Port: 587
Secure: true

Update stable version in repo from 1.0.6 to 1.0.7

Think about update stable version to 1.0.7

Version: stable=1.0.6 (171 days old) => latest=1.0.7 (15 days old)
Installs: stable=2449 (60.11%), latest=842 (20.67%), total=4074
Click to edit

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter email for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.email

-

ERRORS:

• ❗ [E184] "common.wakeup" is deprecated and ignored. Please remove from io-package.json.

WARNINGS:

• 👀 [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
• 👀 [W134] Missing suggested translation into uk of "common.desc" in io-package.json.
• 👀 [W154] Missing suggested translation into uk of some "common.news" in io-package.json.
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

• 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:

@iobroker-bot recheck
@iobroker-bot recreate

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 13 Sep 2024 10:29:32 GMT based on commit 2e448a4
ioBroker.repochecker 3.0.5

Blockly optional more attachments than only 2

It would be perfect to have individual amount of attachment blocks. Maybe by adding it with a settings icon (cogwheel) as in other blockly blocks (e.g. multi text).

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Update stable version in repo from 1.2.0 to 1.2.1

Think about update stable version to 1.2.1

Version: stable=1.2.0 (204 days old) => latest=1.2.1 (15 days old)
Installs: stable=5974 (72.34%), latest=590 (7.14%), total=8258

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter email for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.email

-

👍 No errors found

WARNINGS:

• 👀 [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
• 👀 [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W853] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

• 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check at any time by adding the following comment to this issue:

@iobroker-bot recheck

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 06 Sep 2024 07:34:36 GMT

local sendmail?

I tried to configure the local sendmail on a linux (debian) box:
Server: localhost
Port: 25
SSL: no (no mark)
Username: empty
Pass: empty

Got: wrong Certificate

Ok, now I could install let's encrypt,... but: I just want to use the local postfix. Isn't there any easy way of doing it?

adapter.getMessage is deprecated and will be removed in js-controller 2.3

Warning in Log for upcoming JS-Controller version 2.3 with hint: "Please report this warning to the developer of this adapter!"

Microsoft Exchange

How to use TLS Port 25 ?
is it possible to add TLS in settings?

local network - smtp relay host anonymous access - Error undefined

email dispatch does not work if a mail server is configured in the adapter config without specifying user and password.

On the same host, sending e-mails via shell and mailutils works with the same settings without user and password.

config (anonymized):

transport: smtp
service: User defined
host: smtp.relay.local
port: 25
user: empty 
password: empty 

Test button (Instance settings: email):

Error Missing credentials for "LOGIN"

iobroker Log (anonymized):

error: email.0 (32848) Error undefined

States system redis pmessage io.messagebox.system.adapter.email.0/io.messagebox.system.adapter.email.0:{"command":"send","message":{"subject":"ioBroker","to":"user@local","from":"iobhost@local","text":"Das ist eine Test-Email!","options":{"host":"smtp.relay.local","port":"25","secure":false,"requireTLS":false,"auth":{"user":"","pass":""},"service":""}},"from":"system.adapter.admin.0","callback":{"message":{"subject":"ioBroker","to":"user@local","from":"iobhost@local","text":"Das ist eine Test-Email!","options":{"host":"smtp.relay.local","port":"25","secure":false,"requireTLS":false,"auth":{"user":"","pass":""},"service":""}},"id":63,"ack":false,"time":1677758212402},"_id":17612211}

• Adapter version: v1.1.4
• node: v16.19.1
• js-controller: 4.0.24
• Operating system: Linux Ubuntu x64

callback function is never called

Describe the bug
sendTo('email.0', 'send', {to: "[email protected]", subject: "test", body: "testbody" }, function(res) { /* handle res here */ });
the callback function is not called by the adapter (not called at all)

To Reproduce
just exec the above

Expected behavior
handle error or success in the callback function

Screenshots & Logfiles
none

Versions:

• Adapter version: 1.0.7
• JS-Controller version: 3.2.16
• Node version: 12.20.1
• Operating system: ubuntu 18.04.5 LTS

Additional context
none

Please add your adapter to ioBroker.discovery

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

Release script: Action required

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

Update stable version in repo from 1.0.10 to 1.1.3

Think about update stable version to 1.1.3

Version: stable=1.0.10 (344 days old) => latest=1.1.3 (15 days old)
Installs: stable=5302 (77%), latest=668 (9.7%), total=6886
Click to edit

Button pressed log and send via MQTT

Requested mail action okay feedback

This information is already displayed in the debug log.
Would it also be possible to receive this information as an object in order to execute the transmission again if it is not successful?

e.g
email.0 Response: 250 Requested mail action okay, completed:

In the event of an error only
email.0 Error undefined

Fehlermeldung bei Instanzeinstellungen für mail.ee

Describe the bug

Fehler Hostname/IP does not match certificate's altnames: Host: smtp.mail.ee. is not in the cert's altnames: DNS:mail.inbox.eu, DNS:mail.ee, DNS:mail.inbox.la, DNS:mail.inbox.lt

Expected behavior
Sending an eMail from the iOBroker Mail-Adapter without errors.

Screenshots & Logfiles

Versions:

• Adapter version: 1.0.10
• JS-Controller version: 4.0.21
• Node version: v 14.19.0
• Operating system: Debian

Additional context

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter email for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.email

-

👍 No errors found

WARNINGS:

• 👀 [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
• 👀 [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W522] Please consider migrating to admin 5 UI (jsonConfig).
• 👀 [W853] .npmignore found - consider using package.json object "files" instead.

Please review issues reported and consider fixing them as soon as appropiate.

Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Update stable version in repo from 1.3.0 to 1.3.1

Think about update stable version to 1.3.1

Version: stable=1.3.0 (55 days old) => latest=1.3.1 (15 days old)
Installs: stable=3969 (48.74%), latest=488 (5.99%), total=8144

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 1.3.1 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Please check ioBroker.email with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Mails are not send due to "authentification failed"

Describe the bug
After some time I'm getting errors:

email.0 | 2022-08-10 10:01:02.369 | error | (COMPACT) Error 535 5.7.8 Error: authentication failed:

When entering settings and pressing button "Test mail" a mail is correctly send (without changing any options). So, the error cannot result from spam protection of mail provider I'd say (all-inkl.com).
When restarting adapter it works some time until the error comes up again.

To Reproduce
Just wait some time

Expected behavior
Mails should always be sent

Versions:

• Adapter version: 1.1.3
• Node version: v16.16.0
• Operating system: Raspi OS (bullseye)

Additional context
Was also occuring under Stretch and without compact mode.

Add Support for Compact mode (js-Controller 2.0 Feature)

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Fehler unable to verify the first certificate

Describe the bug
I have a Synology NAS with a local eMail service. Fritzbox and HP printer are using this SMTP since months now without any problems. Now i try to establish a connection to my iobroker instance. But i get errors:

SMTP port 25: Fehler unable to verify the first certificate
port 465: Fehler unable to verify the first certificate
port 586; Fehler 140674551363456:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

I don't need a SSL transaction because it's local - but also on port 25 without "ssl" I got an "unable to verify the first certificate" error.

Screenshots & Logfiles

Versions:

• Adapter version: 1.0.7

warn | (793) adapter.getMessage is deprecated and will be removed in js-controller 2.3.

Hay i have this warning in my log File, is it important? I should post it to the developer.

2020-02-01 17:29:19.803	warn	(793) adapter.getMessage is deprecated and will be removed in js-controller 2.3. Please report this warning to the developer of this adapter!

Installed Version 1.0.5

Best regards.
Matdos

Update stable version in repo from 1.0.7 to 1.0.9

Think about update stable version to 1.0.9

Version: stable=1.0.7 (271 days old) => latest=1.0.9 (15 days old)
Installs: stable=3736 (72.22%), latest=842 (16.28%), total=5173
Click to edit

Update stable version in repo from 1.1.4 to 1.2.0

Think about update stable version to 1.2.0

Version: stable=1.1.4 (252 days old) => latest=1.2.0 (15 days old)
Installs: stable=5903 (74.46%), latest=559 (7.05%), total=7928
Click to edit

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.email

• [E152] common.dataSource type has an invalid type none
• [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2022 bluefox [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2014-2022 bluefox [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

How to use this adapter on accounts for Hotmail, Live.com, Office365 und Web-Outlook after September 16. ?

Microsoft will enforce the security of it's Email-Products, it will not be possible to use simply Username+Password after 16.September 2024. See here: https://techcommunity.microsoft.com/t5/outlook-blog/keeping-our-outlook-personal-email-users-safe-reinforcing-our/ba-p/4164184
Is there anything planned for the email-plugin of ioBroker? Or can these accounts no longer be used then?

1und1 / ionos

Describe the bug
got error: Error 501 Syntax error in parameters or arguments
To Reproduce
Steps to reproduce the behavior:
copied login data works with weblogin ionos (https://email.ionos.de/),
=> but not via the adapter

Expected behavior
it should possible to get the test passed
AND send emails

Versions:
-adapter Version 1.2.0 in D:/ioBroker/node_modules/iobroker.email,

• node: v18.17.0,
• js-controller: 4.0.24
  -Windows 11

New tls.option for service "Benutzerdefiniert"

It would be good to have an option to accept self signed certificates under service "Benutzerdefiniert".

Eg. a checkbox for tls.options {rejectUnauthorized: true/false}

Error 451 4.3.0 pymilter: untrapped exception in pythonfilter

With the latest version I get the following error message when I try to send a test email:

Error 451 4.3.0 pymilter: untrapped exception in pythonfilter

The log shows:

`

email.0	2020-06-30 14:46:33.765	error	(27011) Error 451 4.3.0 pymilter: untrapped exception in pythonfilter
`

Updating to the Github version did not resolve the error.

I am on js-controller 3.1.6 and nodejs 12.18.

Any ideas?

Veralteter Transportalgorithmus | web.de Voreinstellung fehlerhaft

Hallo zusammen,
ich wollte gerne meinen web.de Account für den E-Mail Versand von ioBroker nutzen.
Das System ist auf dem aktuellesten Stand mit Admin v.5.

Generell ist die Voreinstellung von web.de fehlerhaft. Ich denke da hier ggf. noch direkt Port 25 SMTP genutzt werden möchte, lehnt web.de die Verbindung ab.

Aufgrunddessen wollte ich die Einstellung selbstständig, wie in meiner FRITZ!Box vornehmen:

Es erscheint folgende Fehlermeldung:

Fehler 140003732326272:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

Da SSL mittlerweile out-of-support ist, gehe ich davon aus, dass hier der Algorithmus der benutzt wird angepasst werden muss, oder?

Danke! :)

1und1 is IONOS

1und1 change the name to ionos.

Verbindungsdaten für IONOS Mailserver

KONTOTYP	IMAP	POP3
Server	imap.ionos.de	pop.ionos.de
Port	993	995
Verbindungstyp / Verschlüsselung	SSL/TLS	SSL/TLS

Verbindungsdaten für IONOS Mailserver Posteinganggserver (IMAP, POP3) KONTOTYP IMAP POP3 Server imap.ionos.de pop.ionos.de Port 993 995 Verbindungstyp / Verschlüsselung SSL/TLS SSL/TLS Postausgangsserver (SMTP)

Server smtp.ionos.de
Port 465
Verbindungstyp SSL/TLS
Freie Wahl des Kontotyps
Wenn Sie ein E-Mail-Konto in Ihrem E-Mail-Programm einrichten, können Sie in der Regel zwischen den Kontotypen IMAP und POP3 wählen. Beides sind Methoden des E-Mail-Empfangs von einem Mailserver. Sie unterscheiden sich jedoch darin, wie Sie Ihren E-Mail-Bestand verwalten. Eine Erläuterung und Gegenüberstellung der beiden Methoden finden Sie im Artikel Unterschiede zwischen IMAP und POP3.

Wir empfehlen allgemein, IMAP zu verwenden. Geben Sie dazu einfach imap.ionos.de als Posteingangsserver und die Nummer 993 für den Server-Port in Ihrem E-Mail-Programm ein.

Anmeldeinformationen für IONOS Mailserver
Um E-Mails senden und empfangen zu können, ist eine Authentifizierung auf dem Mailserver von IONOS erforderlich. Daher müssen Sie bei der Einrichtung des E-Mail-Programms zusätzlich zu den Verbindungsdaten auch den Benutzernamenund das Passwort Ihres E-Mail-Kontos eingeben.

EINSTELLUNG IHRE EINGABE
Benutzername Ihre vollständige E-Mail-Adresse.
Beispiel: [email protected]
Passwort Das Passwort zu Ihrer E-Mail-Adresse bzw. Ihrem E-Mail-Postfach.

Quelle: https://www.ionos.de/hilfe/e-mail/allgemeine-themen/serverinformationen-fuer-imap-pop-und-smtp/

Send Email SSL error

Hi,
i try to send emails from iobroker via T-Online Mail Server.
(Already an open post at ioBroker Forum:
https://forum.iobroker.net/topic/40687/send-email-ssl-error/1)
When i do the SMTP server Test, i receive this error:
Error 139906210576256:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332

To Reproduce
i assume, that the SMTP-Server securesmtp.t-online.de does not accept TLS 1.3.
openssl s_client -tls1_3 -starttls smtp securesmtp.t-online.de:587
CONNECTED(00000003)
140032464790656:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1544:SSL alert number 40

While openssl s_client -tls1_2 -starttls smtp securesmtp.t-online.de:587
is working properly.

Expected behavior
Is there an option to enforce to use TLS 1.2?

Versions:

• Adapter version: 1.0.7
• JS-Controller version: 3.1.6
• Node version: v12.20.1
• Operating system: Debian 10 x64 Proxmox LXC (uname -a: Linux fhem-prod 5.4.78-1-pve #1 SMP PVE 5.4.78-1 (Mon, 30 Nov 2020 10:57:47 +0100) x86_64 GNU/Linux)

Additional context
Add any other context about the problem here.

Update stable version in repo from 1.0.9 to 1.0.10

Think about update stable version to 1.0.10

Version: stable=1.0.9 (148 days old) => latest=1.0.10 (15 days old)
Installs: stable=3659 (67.04%), latest=692 (12.68%), total=5458
Click to edit

Update stable version in repo from 1.1.3 to 1.1.4

Think about update stable version to 1.1.4

Version: stable=1.1.3 (191 days old) => latest=1.1.4 (60 days old)
Installs: stable=5087 (69.4%), latest=847 (11.56%), total=7330
Click to edit

notification-manager: host messages are trimmed wrongly

ioBroker.email/main.js

Line 96 in 6f6f1e5

const readableInstances = Object.entries(instances).map(([instance, entry]) => `${instance.substring('system.adapter.'.length)}: ${getNewestMessage(entry.messages)}`);

instance can be a host too
detect if starts with system.adapter or system.host and use substring or use everything after second dot. ;-)

adapter.getMessage is deprecated and will be removed in js-controller 2.3

Warning message in log, with js-controller 2.2.7:

email.0 | 2020-01-06 16:19:47.738 | warn | (27764) adapter.getMessage is deprecated and will be removed in js-controller 2.3. Please report this warning to the developer of this adapter!

Update stable version in repo from 1.2.2 to 1.3.0

Think about update stable version to 1.3.0

Version: stable=1.2.2 (141 days old) => latest=1.3.0 (15 days old)
Installs: stable=5358 (65.01%), latest=502 (6.09%), total=8242

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 1.3.0 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Cannot read property '__stopTimer'

Hi,
I get these errors. I have already updated the adapter to 1.0.6 and have done all other updates.
Does anyone have an idea what I can do?

(2518) Error undefined
(2518) uncaught exception: Cannot read property '__stopTimer' of undefined
(2518) TypeError: Cannot read property '__stopTimer' of undefined at stop (/opt/iobroker/node_modules/iobroker.email/main.js:52:17) at transport.sendMail (/opt/iobroker/node_modules/iobroker.e
Caught by controller[0]: TypeError: Cannot read property '__stopTimer' of undefined
Caught by controller[0]: at stop (/opt/iobroker/node_modules/iobroker.email/main.js:52:17)
Caught by controller[0]: at transport.sendMail (/opt/iobroker/node_modules/iobroker.email/main.js:188:9)
Caught by controller[0]: at transporter.send.args (/opt/iobroker/node_modules/nodemailer/lib/mailer/index.js:226:21)
Caught by controller[0]: at SMTPConnection.connection.once.err (/opt/iobroker/node_modules/nodemailer/lib/smtp-transport/index.js:175:24)
Caught by controller[0]: at Object.onceWrapper (events.js:277:13)
Caught by controller[0]: at SMTPConnection.emit (events.js:189:13)
Caught by controller[0]: at SMTPConnection._onError (/opt/iobroker/node_modules/nodemailer/lib/smtp-connection/index.js:774:14)
Caught by controller[0]: at Immediate.setImmediate (/opt/iobroker/node_modules/nodemailer/lib/smtp-connection/index.js:334:52)
Caught by controller[0]: at runCallback (timers.js:705:18)
Caught by controller[0]: at tryOnImmediate (timers.js:676:5)

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!