User Tools

Site Tools


troubleshooting_known_issues

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
troubleshooting_known_issues [2015/11/10 18:12]
lucy [Mail communication issues]
troubleshooting_known_issues [2019/07/25 12:49] (current)
Line 25: Line 25:
    * LUCY is sending mails in most cases via SMTP (port 25). If you place LUCY in a company LAN keep in mind that in most cases port 25 to your official MX (mail server) is not opened from the LAN to the DMZ or wherever your mail server is located. LUCY also needs to be able to resolve DNS (port 53) to make that MX lookup.    * LUCY is sending mails in most cases via SMTP (port 25). If you place LUCY in a company LAN keep in mind that in most cases port 25 to your official MX (mail server) is not opened from the LAN to the DMZ or wherever your mail server is located. LUCY also needs to be able to resolve DNS (port 53) to make that MX lookup.
   * Did you define your own company domain as a sender? Example: you try to phish your employees with the domain mycompany.com,​ which actually is the official domain for your company? Problem is: there might be a DNS record (example SPF) that defines, which mail server is allowed to send mails on behalf of this domain. If such a record exists your mail server will deny mails coming from a different server using this domain. The solution here: if you still want to perform a phishing test with a domain like the one from your company we recommend reserving a similar domain like “my-company.com” or place a typo in there like “myconpany.com”. Most users won’t recognize the difference and you have an additional feature to test the awareness.   * Did you define your own company domain as a sender? Example: you try to phish your employees with the domain mycompany.com,​ which actually is the official domain for your company? Problem is: there might be a DNS record (example SPF) that defines, which mail server is allowed to send mails on behalf of this domain. If such a record exists your mail server will deny mails coming from a different server using this domain. The solution here: if you still want to perform a phishing test with a domain like the one from your company we recommend reserving a similar domain like “my-company.com” or place a typo in there like “myconpany.com”. Most users won’t recognize the difference and you have an additional feature to test the awareness.
-  * Did you also modify your DNS entries to match the scenario? Some SPAM filters for example will test if there is a valid PTR (reverse DNS) set for the host that sends a mail. If it doesn'​t exist, it will be rejected. Most providers allow you to define MX, TXT, A records for your domain/​host. But not only the PTR is required. Your SMTP banner sometimes also gets checked, if it matches the hostname. To change the hostname within the mail service you can set the hostname within /​etc/​postfix/​main.cf ​ like this: "​myhostname=server.example.com"​. Then restart the mailserver: "​postfix stop && postfix start"+  * Did you also modify your DNS entries to match the scenario? Some SPAM filters for example will test if there is a valid PTR (reverse DNS) set for the host that sends a mail. If it doesn'​t exist, it will be rejected. Most providers allow you to define MX, TXT, A records for your domain/​host. But not only the PTR is required. Your SMTP banner sometimes also gets checked, if it matches the hostname. To change the hostname within the mail service you can set the hostname within /​etc/​postfix/​main.cf ​ like this: "​myhostname=server.example.com"​. Then restart the mail server: "​postfix stop && postfix start"
  
 ==== LUCY says “mail test failed” when I start a campaign ==== ==== LUCY says “mail test failed” when I start a campaign ====
troubleshooting_known_issues.txt · Last modified: 2019/07/25 12:49 (external edit)