Local Ghost 3.0 - subscribing/signin does not work with non mailgun config settings

This is about more clarification on previous thread.

@Hannah et’all

Thanks for detailed information about the mail config explanation.

My Question is to understand the BulkMail &Mailgun.
Please do Correct me, When you say Bulkmail and Mailgun configuration. The settings fall under /ghost >lab/Members(beta) > email-settings. I easily understand which is expected a Mailgun account details in given fields.

I hope this is config is only effect when new Post is submitted by members and its expected to send email to all subscribers using Mailgun [/ghost >lab/Members(beta) > email-settings].

Please correct me if im wrong…

Im coming back to transaction email.
This config is allowed with custom requirements with standard help documentation. and its used as per login/signup/subscribe/passwd resets…

So when New User hit a blog-site and hit again a subscribe/signup or Signin/Login, This mail config will get effect to communicate for subscribers/login with welcome note and Links , is that correct ?

If the Above understanding is correct, Then i get error when i click Subscribe/login, " Please enter a valid email address!" Ghost logs for ref.
Note :1, If i have to fix this , then i have to use mailgun smtp account settings, then and there no issues i able to signin/subscribe with email receiving, So my question is why the dependency.? Is there feasible option to configure with non mailgun accounts…?
2, With below smtp config, Test mail configuration works ( Lab > Testing tools> Test email configuration ) i receiving emails.

FYI : ghost ver. 3.16.1

my config.production.json:

“mail”: {
“from”: “postmaster@mydomain.com”,
“transport”: “SMTP”,
“options”: {
“service”: “mail”,
“host”: “smtp.mydomain.com”,
“port”: 465,
“secureConnection”: true,
“auth”: {
“user”: “postmaster@mydomain.com”,
“pass”: “xxxxxxxx”
}
}
},

[2020-05-27 01:03:53] INFO “POST /members/api/send-magic-link/” 500 98ms
[2020-05-27 01:04:08] INFO “PUT /ghost/api/v3/admin/settings/” 200 100ms
[2020-05-27 01:04:20] WARN Ghost has shut down
[2020-05-27 01:04:24] INFO Ghost is running in production…
[2020-05-27 01:04:24] INFO Your site is now available on https://blog.knowledgesociety.tech/
[2020-05-27 01:04:24] INFO Ctrl+C to shut down
[2020-05-27 01:04:24] INFO Ghost boot 2.44s
[2020-05-27 01:04:24] INFO Bootstrap client was closed.
[2020-05-27 01:04:26] WARN Cookie ghost-members-ssr not found
[2020-05-27 01:04:26] INFO “GET /signup/” 200 92ms
[2020-05-27 01:04:26] WARN Cookie ghost-members-ssr not found
[2020-05-27 01:04:26] WARN Cookie ghost-members-ssr not found
[2020-05-27 01:04:26] WARN Cookie ghost-members-ssr not found
[2020-05-27 01:04:26] INFO “GET /assets/built/infinitescroll.js?v=1f3f558cfc” 200 16ms
[2020-05-27 01:04:26] INFO “GET /public/members.min.js?v=1f3f558cfc” 200 20ms
[2020-05-27 01:04:26] INFO “GET /assets/built/screen.css?v=1f3f558cfc” 200 25ms
[2020-05-27 01:04:26] INFO “GET /assets/built/jquery.fitvids.js?v=1f3f558cfc” 200 24ms
[2020-05-27 01:04:26] INFO “GET /favicon.ico” 200 10ms
[2020-05-27 01:04:34] ERROR

NAME: EmailError
MESSAGE: Failed to send email. Reason: Can’t send mail - all recipients were rejected.

level: normal

“Please see https://ghost.org/docs/concepts/config/#mail for instructions on configuring email.”
EmailError: Failed to send email. Reason: Can’t send mail - all recipients were rejected.
at EmailError.GhostError (/var/www/blog1/versions/3.16.1/node_modules/@tryghost/errors/lib/errors.js:10:26)
at new EmailError (/var/www/blog1/versions/3.16.1/node_modules/@tryghost/errors/lib/errors.js:34:20)
at createMailError (/var/www/blog1/versions/3.16.1/core/server/services/mail/GhostMailer.js:51:12)
at MailComposer.transport.sendMail [as returnCallback] (/var/www/blog1/versions/3.16.1/core/server/services/mail/GhostMailer.js:93:28)
at SMTPConnectionPool._onConnectionError (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/pool.js:334:17)
at SMTPClient.emit (events.js:198:13)
at SMTPClient.EventEmitter.emit (domain.js:448:20)
at SMTPClient._onError (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/client.js:373:10)
at SMTPClient._actionRCPT (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/client.js:1054:18)
at SMTPClient._onData (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/client.js:354:29)
at TLSSocket.emit (events.js:198:13)
at TLSSocket.EventEmitter.emit (domain.js:448:20)
at addChunk (_stream_readable.js:288:12)
at readableAddChunk (_stream_readable.js:269:11)
at TLSSocket.Readable.push (_stream_readable.js:224:10)
at TLSWrap.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

RecipientError: Can’t send mail - all recipients were rejected
at SMTPClient._actionRCPT (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/client.js:1054:27)
at SMTPClient._onData (/var/www/blog1/versions/3.16.1/node_modules/simplesmtp/lib/client.js:354:29)
at TLSSocket.emit (events.js:198:13)
at TLSSocket.EventEmitter.emit (domain.js:448:20)
at addChunk (_stream_readable.js:288:12)
at readableAddChunk (_stream_readable.js:269:11)
at TLSSocket.Readable.push (_stream_readable.js:224:10)
at TLSWrap.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

[2020-05-27 01:04:34] INFO “POST /members/api/send-magic-link/” 500 126ms

Update:
With above mail configuration, I able to invite with email address under /ghost admin panel under Staff menu. So the mail config is working inside admin panel operations. but not from external subscribe/login screens.

Hey @ravinayag :wave:
Are you still encountering issues with this? Have you updated to the latest version of Ghost?

I am still having this same issue, only with Gmail addresses though. I posted my own ticket here per @Hannah 's instructions: Help with email subs via mailgun

@DavidDarnes.

Could you share on which release the issue have fix so i can do update.
FYI : currently i’m at 3.16.1.

Whatever version you are on, you should always update to the absolute latest version of Ghost.

Our upgrade policy is that we support upgrading from any version of 1.x or later to latest, not that you can upgrade from any version to any version. This would be impossible to maintain!

1 Like

I upgraded to 3.31.2 (latest), Still the issues exists.