Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong From Adress #43

Open
Yanik39 opened this issue Jan 11, 2022 · 1 comment
Open

Wrong From Adress #43

Yanik39 opened this issue Jan 11, 2022 · 1 comment
Labels
troubleshooting There might be bug or it could be user error, more info needed type: notification

Comments

@Yanik39
Copy link

Yanik39 commented Jan 11, 2022

Part 2 of #36

Resolving host smtp.mailbox.org . . . done.
Connecting to 80.241.60.196:465 . . . connected.
Comparing DNS name: "*.mailbox.org"
220 smtp1.mailbox.org ESMTP Postfix
>>> HELO backup.example.com
250 smtp1.mailbox.org
>>> MAIL FROM:<root@backup.example.com>
250 2.1.0 Ok
>>> RCPT TO:<notifications@example.com>
554 5.7.1 <unknown[$IP]:5787>: Client host rejected: Access denied
smtp-server: 554 5.7.1 <unknown[$IP]:5787>: Client host rejected: Access denied
"/root/dead.letter" 11/392
. . . message not sent.
mail sending failed

Hello again,

My env file has "from" adress. And it works when i use it manually. But somehow with container i get above error which is app uses my docker hostname.
My Docker hostname: backup.example.com
My Env file from adress: info@example.com

App doesnt use env file from adress, somehow overwrites with hostname: root@backup.example.com. So access is denied by smtp server. But everything works when i send email manually like at my #36 post.

Any idea why?

@ttionya
Copy link
Owner

ttionya commented Jan 12, 2022

hey @Yanik39 ,

I'm sorry to hear that you are still having trouble with sending emails. The previous error "send-mail: applet not found" has been fixed.

I checked the from and sender sections of the mailx documentation. mailx looks like it sets the from field to machine's hostname, try changing your docker container hostname to make sure it is not valid at the Internet. Or see if the sender field solves the problem.

@ttionya ttionya added the troubleshooting There might be bug or it could be user error, more info needed label Feb 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
troubleshooting There might be bug or it could be user error, more info needed type: notification
Projects
None yet
Development

No branches or pull requests

2 participants