Closed jims-1234 closed 4 years ago
I'm not sure what you're asking for here -- what doesn't work?
Hi Jaben, apologies, for the limited info. Issue is papercut doesn't accept this email, Microsoft Exchange does.
Note my client is not 100% compliant with the RFC, so understand if you don't want to "fix" this.
Firstly my client says hello before papercut, this may cause the rest of the conversation to fail..?
HELO hostname.example.com
220 Papercut.Service v6.0.0.0 ESMTP ready
MAIL FROM: user@hostname.example.com
250 Hello hostname.example.com, haven't we met before?
RCPT TO: user2@hostname.example.com
501 , 4 retry(ies) remaining.
Client then says from ..., and paper says hello.. :)
Client then says rcpt to .., and paper cut says 501, 4 retries remaining..
So not sure what the problem is, it maybe the client talking first, it may be lack of '<' in email address, it maybe something else?
As I say, this works with exchange, just not papercut..!
Cheers
James
Now Papercut just uses SmtpServer (https://github.com/cosullivan/SmtpServer), now.
You'd have to pull request there.
On May 6, 2019 8:53:05 PM jims-1234 notifications@github.com wrote:
Hi Jaben, apologies, for the limited info. Issue is papercut doesn't accept this email, Microsoft Exchange does. Note my client is not 100% compliant with the RFC, so understand if you don't want to "fix" this. Firstly my client says hello before papercut, this may cause the rest of the conversation to fail..? HELO hostname.example.com 220 Papercut.Service v6.0.0.0 ESMTP ready MAIL FROM: user@hostname.example.com 250 Hello hostname.example.com, haven't we met before? RCPT TO: user2@hostname.example.com 501 , 4 retry(ies) remaining.
Client then says from ..., and paper says hello.. :) Client then says rcpt to .., and paper cut says 501, 4 retries remaining.. So not sure what the problem is, it maybe the client talking first, it may be lack of '<' in email address, it maybe something else? As I say, this works with exchange, just not papercut..! Cheers James — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Aloha! I'm ScissorBot :scissors: -- the bot in charge of keeping the issues tidy. It looks like this issue is stale due to lack of activity. Unfortunately, I'll be closing it if there is no further activity. 😞 Please contribute to the issue to keep it open. Thanks!
Let me know if this is still an issue.
This was partially working with version 5.3.x, but i upgraded it in the hope it would fix it..
wireshark reports:
log only mentions: