mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-27 01:06:01 +03:00
[GH-ISSUE #294] Invalid from address #193
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#193
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dejudicibus on GitHub (May 13, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/294
I installed mailpit and started it. I can see the MailPit interface on localhost:8025 as expected.
Then I created a file email.txt as follows
but if I call MailPit as follows
I get the error message
and no messages in the browser interface. Changing the from address to ANY real or fake address makes no change.
Platform: Windows 10 Pro with WampServer 3.2.6 64bit
@axllent commented on GitHub (May 13, 2024):
That's really strange - I just tried with a copy/paste of your syntax and it works perfectly for me. I can't see any reason it would/should fail, unless potentially the txt file you created contains maybe some strange or unsupported hidden character encoding - what did you use to create the text file?
What happens if you try with this file? 1-test.txt
@asuheel commented on GitHub (May 13, 2024):
I am also getting same error
invalid from addressTried with 1-test.txt
Still same error
For refrence : I have done setup using docker-compose with this docker-compose.yaml
@axllent commented on GitHub (May 13, 2024):
@bmunshi on what platform is the
mailpit sendmail...being run? I assume for both of you that you're on a recent version of Mailpit too?@dejudicibus commented on GitHub (May 14, 2024):
I found out what the problem was. If I call just
mailpitI get the error.To avoid the error I have to call
I thought that localhost was the default, whereas the default is 0.0.0.0 in both cases (1025 & 8025)
@axllent commented on GitHub (May 15, 2024):
I am confused @dejudicibus -
0.0.0.0means the Mailpit server should listen on all network interfaces which is the default (ie: not just to "localhost") which should work on Windows too, and the argument you are running is to start the Mailpit server, not to send messages viamailpit sendmail < email.txt(which is the issue you reported).So
mailpit -s localhost:1025 -l localhost:8025starts mailpit and listens to "localhost" only (other machines in your network cannot connect), andmailpit sendmail < email.txtshould then be able to send to Mailpit.@axllent commented on GitHub (May 15, 2024):
@dejudicibus & @bmunshi - I have found the cause. When using sendmail in this way (without specifying a sender's email in the command with
-f), it will automatically detect your username from the system. The issue here is that Windows returns the "user" in the formathostname\username- and\is not a valid character in an email ~ so you get the error.I have just pushed a fix (work-around) in v1.18.2 which will fix this issue for both of you. Please confirm this works for you? Thanks.
@axllent commented on GitHub (May 17, 2024):
@powerquell I don't think this is related to this issue at all. From what I see, your Mailpit requires authentication (
250-AUTH LOGIN PLAIN), but you're not authenticating via telnet first before issuing theMAIL FROM.@axllent commented on GitHub (May 17, 2024):
Ahh right - sorry @powerquell, that was not obvious from your original message. Your formatting is incorrect, try
MAIL FROM:<test@example.com>- the SMTP protocol requires<>around the addresses (includingRCPT TO) (see this).@github-actions[bot] commented on GitHub (May 25, 2024):
This issue has been marked as stale because it has been open for 7 days with no activity.
@github-actions[bot] commented on GitHub (May 28, 2024):
This issue was closed because there has been no activity since being marked as stale.