Mailgun E-Mail notification URL

Hi,

I could use some help with my apprise E-Mail notification URL for the E-Mail service provider mailgun.

I followed the configuration instructions https://github.com/caronc/apprise/wiki/Notify_email and troubleshooting instructions https://github.com/caronc/apprise/wiki/Troubleshooting but unfortunately couldn’t nail down the misconfiguration.

Following command was used for testing: apprise -vvv -t "apprise test title" -b "apprise test body" mailtos://SMTP_PASSWORD@MY_DOMAIN?smtp=SMTP_SERVER&from=MY_NAME@MY_DOMAIN&name=NAME&to=ANOTHER_NAME@ANOTHER_DOMAIN&user=SMTP_USER.

The SMTP_USER has to be specified as a full E-Mail address. Furthermore MY_DOMAIN, SMTP_SERVER and ANOTHER_DOMAIN have different domains. Please note that the mailgun configuration is correct, i.e. manually sending E-Mails with those parameters is working as expected.

After issuing the test command, the SMTP server receives following message header: to: "PASSWORD@MY_DOMAIN" from: "Apprise Notifications <PASSWORD@MY_DOMAIN>" subject: "apprise test title"

I would expect the following message header: to: "ANOTHER_NAME@ANOTHER_DOMAIN" from: "NAME <MY_NAME@MY_DOMAIN>" subject: "apprise test title"

What am I missing here?

EDIT: I’ve added additional verbose parameters which results in the log below. Clearly the parameters specified above are not populated correctly. I guess I have a misunderstanding of those parameters described in https://github.com/caronc/apprise/wiki/Notify_email. How does the notification URL need to look like in my case?

# apprise -vvvvvvvvvv -t "apprise test title" -b "apprise test body" mailtos://SMTP_PASSWORD@MY_DOMAIN?smtp=SMTP_SERVER&from=MY_EMAIL@MY_DOMAIN&name=NAME&to=ANOTHER_EMAIL@ANOTHER_DOMAIN&user=SMTP_USER
[2]   Done                       apprise -vvvvvvvvvv -t "apprise test title" -b "apprise test body" mailtos://SMTP_PASSWORD@MY_DOMAIN?smtp=SMTP_SERVER&from=MY_EMAIL@MY_DOMAIN&name=NAME&to=ANOTHER_EMAIL@ANOTHER_DOMAIN&user=SMTP_USER
# 2019-04-25 18:24:53,813 - TRACE - URL mailtos://SMTP_PASSWORD@MY_DOMAIN?smtp=SMTP_SERVER unpacked as:
user="SMTP_PASSWORD"
password="None"
port="None"
host="MY_DOMAIN"
fullpath="None"
path="None"
query="None"
schema="mailtos"
url="mailtos://SMTP_PASSWORD@MY_DOMAIN"
qsd="{'smtp': 'SMTP_SERVER'}"
qsd+="{}"
qsd-="{}"
secure="True"
verify="True"
to="SMTP_PASSWORD@MY_DOMAIN"
from="SMTP_PASSWORD@MY_DOMAIN"
smtp_host="SMTP_SERVER"
tag="set()"
2019-04-25 18:24:53,814 - DEBUG - Loaded URL: mailtos://SMTP_PASSWORD@MY_DOMAIN/?format=html&overflow=upstream&to=SMTP_PASSWORD%40MY_DOMAIN&from=SMTP_PASSWORD%40MY_DOMAIN&mode=starttls&smtp=SMTP_SERVER&timeout=15&user=SMTP_PASSWORD&verify=yes
2019-04-25 18:24:53,814 - DEBUG - Email From: SMTP_PASSWORD@MY_DOMAIN <Apprise Notifications>
2019-04-25 18:24:53,814 - DEBUG - Email To: SMTP_PASSWORD@MY_DOMAIN
2019-04-25 18:24:53,814 - DEBUG - Login ID: SMTP_PASSWORD
2019-04-25 18:24:53,815 - DEBUG - Delivery: SMTP_SERVER:587
2019-04-25 18:24:53,815 - DEBUG - Connecting to remote SMTP server...
2019-04-25 18:24:53,872 - DEBUG - Securing connection with STARTTLS...
2019-04-25 18:24:54,117 - INFO - Sent Email notification to "SMTP_PASSWORD@MY_DOMAIN".

[caronc]

Merge completed in #103 ; closing ticket

[caronc]

Oh, no it should support multiple unique emails. Sorry I misunderstood your issue. I’m not home right now, but that’s a bug if it’s only sending one email from a unique list. I’ll get to it this afternoon I hope.