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

[Bug]: 邮件提醒通知无法提醒博主 || [Bug]: Email reminder notification cannot remind bloggers #2143

Open
Akimio521 opened this issue Nov 2, 2023 · 8 comments
Labels
bug Something isn't working Inactive

Comments

@Akimio521
Copy link

Akimio521 commented Nov 2, 2023

问题描述 | Describe the bug

如题,其他人在博客下留言,博主无法收到邮件通知,博主回复评论其他人正常。
已填写参数AUTHOR_EMAIL
登陆邮箱后台发现只给其他人发送了邮件,没给博主发邮件

问题网站 | Website URL

AUTHOR_EMAIL

服务部署在哪里? | Where your waline deploy?

Vercel (Default)

数据存储在哪里?| Where your comment data store?

MongoDB


Problem description | Describe the bug

Just like the title, if other people leave comments on the blog, the blogger cannot receive email notifications, but the blogger can reply to other people's comments normally.
Parameter AUTHOR_EMAIL has been filled in
When I logged in to my mailbox, I found that I had only sent emails to other people, but not to the blogger.

Question Website | Website URL

AUTHOR_EMAIL

Where is the service deployed? | Where your waline deploy?

Vercel (Default)

Where is the data stored? | Where your comment data store?

MongoDB

@Akimio521 Akimio521 added the bug Something isn't working label Nov 2, 2023
@github-actions github-actions bot changed the title [Bug]: 邮件提醒通知无法提醒博主 [Bug]: 邮件提醒通知无法提醒博主 || [Bug]: Email reminder notification cannot remind bloggers Nov 2, 2023
@lizheming
Copy link
Collaborator

lizheming commented Nov 2, 2023

提供下 Vercel 后台的日志吧


Please provide the Vercel background log

@Akimio521
Copy link
Author

Akimio521 commented Nov 3, 2023

image
后台日志好像也没什么特别的


image
The background log seems to be nothing special

@lizheming
Copy link
Collaborator

lizheming commented Nov 3, 2023

博主通知有配置什么其他的通知方式吗?


Are there any other notification methods configured for blogger notification?

@Akimio521
Copy link
Author

Akimio521 commented Nov 3, 2023

没太懂你什么意思,环境变量填了下面这些:

SITE_NAME=
SITE_URL=
LEVELS=
MONGO_HOST=
MONGO_PORT=
MONGO_USER=
MONGO_PASSWORD=
MONGO_DB=
MONGO_OPT_SSL=
MONGO_AUTHSOURCE=
SMTP_HOST=
SMTP_PORT=
SMTP_USER=
SMTP_PASS=
SMTP_SECURE=
SENDER_NAME=
SENDER_EMAIL=
AUTHOR_EMAIL=
MAIL_SUBJECT=
MAIL_TEMPLATE=
MAIL_SUBJECT_ADMIN=
MAIL_TEMPLATE_ADMIN=
WEBHOOK=

顺便想问一下,WebHook是没办法传输评论人、具体评论这些信息吗


I don’t quite understand what you mean. The environment variables are filled with the following:

SITE_NAME=
SITE_URL=
LEVELS=
MONGO_HOST=
MONGO_PORT=
MONGO_USER=
MONGO_PASSWORD=
MONGO_DB=
MONGO_OPT_SSL=
MONGO_AUTHSOURCE=
SMTP_HOST=
SMTP_PORT=
SMTP_USER=
SMTP_PASS=
SMTP_SECURE=
SENDER_NAME=
SENDER_EMAIL=
AUTHOR_EMAIL=
MAIL_SUBJECT=
MAIL_TEMPLATE=
MAIL_SUBJECT_ADMIN=
MAIL_TEMPLATE_ADMIN=
WEBHOOK=

By the way, I would like to ask, is there no way for WebHook to transmit the information of the reviewer and specific comments?

@moeyy01
Copy link

moeyy01 commented Nov 3, 2023

同样的问题, vercel部署


Same problem, vercel deployment

@Guangsudalao
Copy link

Guangsudalao commented Nov 4, 2023

+1,在vercel上部署就有这个问题,评论时无法收到邮件,但是在deta.space上部署就可以收得到邮件


+1, I have this problem when deploying on vercel. I cannot receive emails when commenting, but I can receive emails when deploying on deta.space

@Celetherin
Copy link

Celetherin commented Nov 14, 2023

我也遇到了同样的问题,vercel部署,博主收不到评论通知,但其他人可以收到邮件。


I also encountered the same problem with vercel deployment. The blogger could not receive comment notifications, but other people could receive emails.

@ccbikai
Copy link

ccbikai commented Nov 25, 2023

同样的问题, vercel部署

Same problem, vercel deployment

发件人和收件人不要使用同一个域名试试


Same problem, vercel deployment

Same problem, vercel deployment

Don’t use the same domain name for the sender and recipient. Try

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Inactive
Projects
None yet
Development

No branches or pull requests

6 participants