Bounce handling is not working | Bounce messages are not forwarded to END POINT/ROUTING ADDRESS

[XenyFord]

Dear Respected Team,

I don't know whether it's a bug or lack of a feature or any wrong configuration made on my end, but ultimately bounce messages are not forwarded to the Routing/ENDPOINT email ADDRESS, but they are perfectly identified and listed under 'Outgoing Messages' in the postal dashboard.

After everything done by setting-up email server, domain, user credentials, Routing and ENDPOINT email address, I made a test sending an email to an invalid email address([email protected]) using my 'Credentials' and 'FROM address([email protected])' on https://smtper.net , and got bounce message shown in the dashboard under 'Outgoing Messages' marked as HARD FAIL, but still the bounce messages are not forwarded to ROUTING/ENDPOINT EMAIL ADDRESS.

To Reproduce

Below are the screenshot of the entire process I went through for your reference..

Step 1: Created a mail server named(my email server), domain and credentials as shown in the pics below;

• a. https://prnt.sc/1qjbxkp
• b. https://prnt.sc/1qjc24h
• c. https://prnt.sc/1qjc7az

Step 2: I have created ROUTING & ENDPOINT ADDRESSES as shown in the pic below;

• d. https://prnt.sc/1qjhmjr

Step 3: made a test sending an email to an invalid address([email protected]) as shown in the below pic;

• e. https://prnt.sc/1qjcp7p

Step 4: I had the bounce back message displayed under 'Outgoing Messages' in the postal dashboard as shown in the pic below;

• f. https://prnt.sc/1qjcu8r

Step 5: No bounce messages are received/forwarded to the email address([email protected]) given in the postal settings;

• g. https://prnt.sc/1qjcyz6

Expected behavior

I think, as usual, It must be allowed us to have bounce messages forwarded to the given Routing/ENDPOINT email address([email protected])... Or It's better allow us to have a custom bounce email address instead of auto generated email([email protected]) by postal.

Screenshots

1. https://prnt.sc/1qjbxkp
2. https://prnt.sc/1qjc24h
3. https://prnt.sc/1qjc7az
4. https://prnt.sc/1qjhmjr
5. https://prnt.sc/1qjcp7p
6. https://prnt.sc/1qjcu8r
7. https://prnt.sc/1qjcyz6

Environment details

• OS: [Ubuntu 21.04]
• Browser [chrome, safari]
• Version [N/A]
• Type [desktop, mobile etc...]

Additional information/context

Please let me have the right solution for this ASAP. Also, if required, I will provide you with all the details like live server login and other credential, etc. to allow you have access to our server to solve this issue, If possible.

Thank you in advance!

[adamcooke]

This is not a bug, you just don't seem to understand what a bounce is. I'm converting this to a discussion as this is not a bug in Postal.

If you have a hard fail, it won't bounce, the SMTP server will just reject it straight away when we connect.

[XenyFord]

Mr. Will,
Or, please let me know on how to remove the current SSL(Caddy) and install a new the NEW one? because it seem to be a lot of confusing stuff involved. Thank you in advance!

[willpower232]

The key file is apparently the problem one, what is the head of that?

[XenyFord]

Mr. Will,
The head of the smtp.key is as below..

Please guide me in this case. Thank you in advance!

[willpower232]

Unfortunately Postal can't use that kind of key (#1248), I don't know enough about Caddy to know if you can create and use an RSA-based certificate instead.

[XenyFord]

Mr. Will,
No problem I simply switch it back to RSA from EC keys. It's working now. But, few other problems as shown in the images are is still existed..

Could you please let me know on how to solve this? Thank you in advance!