Mailrise is an SMTP server that converts the emails it receives into Apprise notifications

Config:

configs:
  pushover:
    urls:
      - pover://xxxxxxxxxxxxxxxx@yyyyyyyyyyyyyyyyy
tls:
  mode: starttls
  certfile: /etc/ssl/cert.pem
  keyfile: /etc/ssl/key.pem
smtp:
  hostname: nxdomain.info
  auth:
    basic:
      pushover: xxxxxxxxxxxxxxxxxxx

msmtp:

<-- 220 nxdomain.info Mailrise 0.0.post1.dev1+g8928d73
--> EHLO localhost
<-- 250-nxdomain.info
<-- 250-SIZE 33554432
<-- 250-8BITMIME
<-- 250-SMTPUTF8
<-- 250-STARTTLS
<-- 250 HELP
--> QUIT
<-- 221 Bye
msmtp: the server does not support authentication

Observation: 250-AUTH LOGIN PLAIN is missing

Log:

[2022-12-20 16:34:36] ERROR:asyncio:Fatal error: protocol.data_received() call failed.
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f5392c1b710>
transport: <_SelectorSocketTransport fd=10 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1009, in _read_ready__data_received
    self._protocol.data_received(data)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'SSLProtocol' object has no attribute 'data_received'
[2022-12-20 16:34:36] ERROR:mail.log:('172.18.0.1', 37216) SMTP session exception
Traceback (most recent call last):
  File "/home/mailrise/.local/lib/python3.11/site-packages/aiosmtpd/smtp.py", line 895, in smtp_STARTTLS
    await waiter
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1009, in _read_ready__data_received
    self._protocol.data_received(data)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'SSLProtocol' object has no attribute 'data_received'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/mailrise/.local/lib/python3.11/site-packages/aiosmtpd/smtp.py", line 728, in _handle_client
    await method(arg)
  File "/home/mailrise/.local/lib/python3.11/site-packages/aiosmtpd/smtp.py", line 899, in smtp_STARTTLS
    raise TLSSetupException() from error
aiosmtpd.smtp.TLSSetupException

Steps to reproduce:

I generated a self-signed certifcate, changed the owner to the mailrise container user and mounted it:

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 3650 -nodes -subj '/CN=nxdomain.info'
sudo chown 999:999 *.pem

  mailrise:
    container_name: mailrise
    image: yoryan/mailrise
    restart: always
    volumes:
      - ./mailrise.conf:/etc/mailrise.conf
      - ./cert.pem:/etc/ssl/cert.pem
      - ./key.pem:/etc/ssl/key.pem

I would like to see a way to use some kind of authentication when you send emails to the mailrise. At least some type of local username/password list in the configuration file or maybe even a LDAP(S) integration if it can be implemented easily.

I know that this is meant to be used in a private network where there shouldn't be unauthorised access, but I still would want to use authentication.

Since I'm a relative noob to writing config files for docker containers it would be nice to have an example of /etc/mailrise.conf to work from. So I could cut down some different errors of syntax, etc... Thanks for making such a great project!

First off, this can't be merged as is because the CI script will fail (it's pointing to this fork's package repo) -- but I still wanted to get this here for you to consider. Here are the changes in this fork:

• Docker image size reduced from 919MB to 58.9MB for amd64
• Made dockerfile compatible with arm64, arm32
• Github Actions to automatically build & publish a multiplatform image for amd64/arm64/arm32
• Removed the hardcoded mailrise.xyz domain from destination addresses
  • If the config key appears to have a domain, e.g. [email protected], it will just use that address
  • If the config key does not have a domain, e.g. phil, then the default domain is appended resulting in something like [email protected]
  • Added a config entry for default_domain that is set to mailrise.xyz when omitted to be consistent with the previous behavior

Great project, thanks for your work!

I'm experiencing an issue when I'm trying to use mailrise as an SMTP->Telegram gateway. I'd like mailrise to forward emails with attached images from my security cameras to a Telegram group conversation. I'm using Blue Iris as an NVR software and mailrise is running on the same machine as BI on windows x64 with Python 3.9.7.

configs:
  telegram:
    urls:
      - tgram://BOTID/CHATID/?image=Yes

When sending an email I'm experiencing the following error:

[2021-09-02 22:42:41] INFO:mailrise.skeleton:Loaded configuration with 1 recipient(s)
[2021-09-02 22:42:41] INFO:mail.log:Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
[2021-09-02 22:42:41] INFO:mail.log:Peer: ('::1', 62137, 0, 0)
[2021-09-02 22:42:41] INFO:mail.log:('::1', 62137, 0, 0) handling connection
[2021-09-02 22:42:41] INFO:mail.log:('::1', 62137, 0, 0) EOF received
[2021-09-02 22:42:41] INFO:mail.log:('::1', 62137, 0, 0) Connection lost during _handle_client()
[2021-09-02 22:42:41] INFO:mail.log:('::1', 62137, 0, 0) connection lost
[2021-09-02 22:42:46] INFO:mail.log:Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
[2021-09-02 22:42:46] INFO:mail.log:Peer: ('127.0.0.1', 62141)
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) handling connection
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) >> b'HELO nvr.local'
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) >> b'MAIL FROM:<blueiris@nvr>'
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) sender: blueiris@nvr
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) >> b'RCPT TO:<[email protected]>'
[2021-09-02 22:42:46] INFO:mailrise.skeleton:Accepted recipient: [email protected]
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) recip: [email protected]
[2021-09-02 22:42:46] INFO:mail.log:('127.0.0.1', 62141) >> b'DATA'
[2021-09-02 22:42:47] ERROR:mail.log:('127.0.0.1', 62141) SMTP session exception
Traceback (most recent call last):
  File "C:\Python39\lib\site-packages\aiosmtpd\smtp.py", line 728, in _handle_client
    await method(arg)
  File "C:\Python39\lib\site-packages\aiosmtpd\smtp.py", line 1438, in smtp_DATA
    status = await self._call_handler_hook('DATA')
  File "C:\Python39\lib\site-packages\aiosmtpd\smtp.py", line 465, in _call_handler_hook
    status = await hook(self, self.session, self.envelope, *args)
  File "C:\Python39\lib\site-packages\mailrise\smtp.py", line 113, in handle_DATA
    notification = parsemessage(message)
  File "C:\Python39\lib\site-packages\mailrise\smtp.py", line 200, in parsemessage
    body = body_part.get_content().strip()
  File "C:\Python39\lib\email\message.py", line 1096, in get_content
    return content_manager.get_content(self, *args, **kw)
  File "C:\Python39\lib\email\contentmanager.py", line 25, in get_content
    raise KeyError(content_type)
KeyError: 'multipart/related'
[2021-09-02 22:42:47] INFO:mail.log:('127.0.0.1', 62141) EOF received
[2021-09-02 22:42:47] INFO:mail.log:('127.0.0.1', 62141) Connection lost during _handle_client()
[2021-09-02 22:42:47] INFO:mail.log:('127.0.0.1', 62141) connection lost

Any help would be appreciated.

Dockerhub has a rate limit of 100 pulls/6 hours and is continuing to make decisions that aren't on the best interest to FOSS. It would be great if you could push the docker image to GHCR as well. It should only be a few extra lines in your workflow file. Thanks!

I have deployed your docker and I am seeing the below error

/usr/local/bin/python: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory

Hi, really great project!

I have some applications which sends HTML encoded mails to mailrise. Sadly matrix is not able to output the content correct. So I get some random gibbish in the notification.

Would it be possible to only pass through the subject of the mail? Most of the informations are in there so it's okay when i don't get the body of the message. I think this solution is way easier then removing the HTML content.

Judging by the ~10s it takes to restart the container, the Mailrise process is not handling the incoming SIGTERM signal.

https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop

https://docs.python.org/3/library/signal.html

Borrowed the openssl command from https://aiosmtpd.readthedocs.io/en/latest/smtp.html#enabling-starttls and added an explanation on how to properly mount it in the container.

I'm basically hitting the problem described here:

https://marlam.de/msmtp/old-mailinglist/msg00533.html

I've configured mailrise to use basic authentication but msmtp fails to send mails.

EHLO as reported by msmtp -v:

<-- 220 a4360929b762 Mailrise 0.0.post1.dev1+gbf98187
--> EHLO localhost
<-- 250-a4360929b762
<-- 250-SIZE 33554432
<-- 250-8BITMIME
<-- 250-SMTPUTF8
<-- 250 HELP
--> QUIT
<-- 221 Bye
msmtp: the server does not support authentication
msmtp: could not send mail (account mailrise from /etc/msmtprc)

According to the msmtp devs the mailserver should report this as part of its EHLO.

Btw the Readme is a bit confusing. The example seems to be missing the auth key.

Readme:

smtp:
  basic:
    username: password
    AzureDiamond: hunter2

Correct config according to https://github.com/YoRyan/mailrise#configuration

smtp:
  auth:
    basic:
      username: password