使用其他SMTP服务器发送电子邮件以避免一半或网络钓鱼警告

时间:2021-10-17 18:16:25

I am creating a tool for project managers. For notifications, we have done automated email module. Whenever email gets sent to team members, it says

我正在为项目经理创建一个工具。对于通知,我们已完成自动电子邮件模块。它说,每当电子邮件发送给团队成员时

 FROM :  "Sushant Danekar" "<"notification@mytestserver.com">"

or in some software it Says

或者在某些软件中它说

 on behalf of 'Sushant Danekar'.

I had added sender's email address in Reply-To field while I had added "notification@mytestserver.com" email address in FROM field.

我在回复字段中添加了发件人的电子邮件地址,而我在FROM字段中添加了“notification@mytestserver.com”电子邮件地址。

To avoid above mentioned issue I changed From address to Sender's email address

为了避免上述问题,我将地址更改为发件人的电子邮件地址

But now, Gmail has marked my message as spam and it says "this message may not have been sent by".

但现在,Gmail已将我的邮件标记为垃圾邮件,并说“此邮件可能尚未发送”。

I need a suggession to avoid both of these issue 1) On behalf of 2) this message may not have been.

我需要一个建议来避免这两个问题1)代表2)这个消息可能不是。

I am open for all suggestions

我愿意接受所有建议

I also thought of accepting SMTP details [username, password and SMTP server details] from user and while sending an email.

我还想过用户和发送电子邮件时接受SMTP详细信息[用户名,密码和SMTP服务器详细信息]。

Is it the right way? Does it create problem for our tool in future ? What are the RFC standards ?

这是正确的方法吗?它是否会在未来为我们的工具带来问题?什么是RFC标准?

1 个解决方案

#1


0  

The header line you are showing has a number of syntax errors.

您显示的标题行有许多语法错误。

  • There can be no space between From and :
  • 从和之间不能有空格:

  • You have excessive quoting, some of which prevents correct parsing of the address
  • 您有过多的引用,其中一些阻止正确解析地址

The proper way to format this address would be

格式化此地址的正确方法是

From: Sushant Danekar <notification@mytestserver.com>

(or you could keep the quotes around your name, but that would imply to a human reader that it isn't really your name1).

(或者你可以在你的名字周围保留引号,但这意味着一个人类的读者,这不是你真正的名字1)。

If fixing that does not correct the problem, maybe post a new question with full headers of a failed message, detailed diagnostics from a spam filter, and/or a screen shot which shows the problem in an email client (indicate which one; include several if you can).

如果修复不能解决问题,可以发布一个新问题,其中包含失败邮件的完整标题,来自垃圾邮件过滤器的详细诊断信息,和/或显示电子邮件客户端中的问题的屏幕截图(指明哪一个;包括几个如果你可以的话)。


1 There were situations where traditionally a person's name had to be quoted, but only if it contained symbols which have a special meaning to RFC5321, such as a single quote.

1在某些情况下,传统上必须引用一个人的姓名,但前提是它包含对RFC5321具有特殊含义的符号,例如单引号。

From: "Paddy O'Reilly" <padster@example.com>

These days, the solution to that is to use RFC2047 encoding on human-readable fields where necessary.

目前,解决方案是在必要时在人类可读字段上使用RFC2047编码。

From: =?utf-8?B?Paddy_O=27Reilly?= <padster@example.com>

Any modern client will transparently decode that for proper human display.

任何现代客户端都会透明地解码,以便正确显示人体。

#1


0  

The header line you are showing has a number of syntax errors.

您显示的标题行有许多语法错误。

  • There can be no space between From and :
  • 从和之间不能有空格:

  • You have excessive quoting, some of which prevents correct parsing of the address
  • 您有过多的引用,其中一些阻止正确解析地址

The proper way to format this address would be

格式化此地址的正确方法是

From: Sushant Danekar <notification@mytestserver.com>

(or you could keep the quotes around your name, but that would imply to a human reader that it isn't really your name1).

(或者你可以在你的名字周围保留引号,但这意味着一个人类的读者,这不是你真正的名字1)。

If fixing that does not correct the problem, maybe post a new question with full headers of a failed message, detailed diagnostics from a spam filter, and/or a screen shot which shows the problem in an email client (indicate which one; include several if you can).

如果修复不能解决问题,可以发布一个新问题,其中包含失败邮件的完整标题,来自垃圾邮件过滤器的详细诊断信息,和/或显示电子邮件客户端中的问题的屏幕截图(指明哪一个;包括几个如果你可以的话)。


1 There were situations where traditionally a person's name had to be quoted, but only if it contained symbols which have a special meaning to RFC5321, such as a single quote.

1在某些情况下,传统上必须引用一个人的姓名,但前提是它包含对RFC5321具有特殊含义的符号,例如单引号。

From: "Paddy O'Reilly" <padster@example.com>

These days, the solution to that is to use RFC2047 encoding on human-readable fields where necessary.

目前,解决方案是在必要时在人类可读字段上使用RFC2047编码。

From: =?utf-8?B?Paddy_O=27Reilly?= <padster@example.com>

Any modern client will transparently decode that for proper human display.

任何现代客户端都会透明地解码,以便正确显示人体。