LUCY

User Tools

Site Tools

Trace:
spam_check

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
spam_check [2017/10/20 17:18] – lucyspam_check [2019/07/25 12:49] – external edit 127.0.0.1
Line 48: Line 48:
 It is recommended to create a SMTP server name (that is the server name of LUCY). Most SMTP servers will accept your mail if you simply have a reverse DNS entry. It does not have to match the domain name on your e-mail address. Some SMTP servers will reject mail if the reverse DNS doesn't match the HELO/EHLO hostname used in the connection. If your mail server's hostname is mail.example.com then your reverse DNS, MX record, HELO/EHLO, and SMTP greeting banner should all be mail.example.com as well. According to RFC 2821 the SMTP client MUST, if possible, ensure that the domain parameter to the EHLO command is a valid principal host name (not a CNAME or MX name) for its host. If this is not possible (e.g., when the client's address is dynamically assigned and the client does not have an obvious name), an address literal SHOULD be substituted for the domain name and supplemental information provided that will assist in identifying the client. An SMTP server MAY verify that the domain name parameter in the EHLO command actually corresponds to the IP address of the client. You can save this under the mail Settings: It is recommended to create a SMTP server name (that is the server name of LUCY). Most SMTP servers will accept your mail if you simply have a reverse DNS entry. It does not have to match the domain name on your e-mail address. Some SMTP servers will reject mail if the reverse DNS doesn't match the HELO/EHLO hostname used in the connection. If your mail server's hostname is mail.example.com then your reverse DNS, MX record, HELO/EHLO, and SMTP greeting banner should all be mail.example.com as well. According to RFC 2821 the SMTP client MUST, if possible, ensure that the domain parameter to the EHLO command is a valid principal host name (not a CNAME or MX name) for its host. If this is not possible (e.g., when the client's address is dynamically assigned and the client does not have an obvious name), an address literal SHOULD be substituted for the domain name and supplemental information provided that will assist in identifying the client. An SMTP server MAY verify that the domain name parameter in the EHLO command actually corresponds to the IP address of the client. You can save this under the mail Settings:
  
-{{ settings_mail_host.png?600 }}+{{:mail_set1.png?600|}}
  
 **Review Your Email Content** **Review Your Email Content**
Line 59: Line 59:
 LUCY allows you to Review the mail Content with the local SPAM assassin engine: LUCY allows you to Review the mail Content with the local SPAM assassin engine:
  
-{{ spam_test.png?600 }}+{{:mail_set2.png?600|}}
  
 **Use a Corporate Email Account as Your Sender Address** **Use a Corporate Email Account as Your Sender Address**
Line 131: Line 131:
  
   * First check if the mail got send by clicking on the message log in the left navigation panel within a campaign   * First check if the mail got send by clicking on the message log in the left navigation panel within a campaign
- +{{:mail_set3.png?300|}}
-{{ mail_communication_issues:messagelog.png?200 }}+
  
   * Then check if there was a communication error by clicking on the error log in the left navigation panel within a campaign   * Then check if there was a communication error by clicking on the error log in the left navigation panel within a campaign
  
-{{ mail_communication_issues:error_log.png?200 }}+{{:mail_set4.png?300|}}
  
 There are three possible message scenarios in case mails are still being filtered: There are three possible message scenarios in case mails are still being filtered:
spam_check.txt · Last modified: 2020/08/07 13:01 by lucy