{"type":"rich","version":"1.0","provider_name":"phorkie","provider_url":"https:\/\/p.cweiske.de\/","title":"rspamd: FORGED_SENDER when using Amazon SES for sending mails","author_name":"Christian Weiske","cache_age":86400,"width":900,"height":900,"html":"<!-- embedding all files of https:\/\/p.cweiske.de\/735 -->\n<link rel=\"stylesheet\" href=\"https:\/\/p.cweiske.de\/css\/embed.css\"\/>\n<div class=\"phork\" id=\"735\">\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\">\n\n\n<p>rspamd says the sender is forged when we are using Amazon SES to send e-mails:<\/p>\n<pre class=\"literal-block\">\nFORGED_SENDER (0.3) [no-reply&#64;example.com,01070178f5b733b2-678af94f-a4f3-481a-b90a-570e0b21ad5a-000000&#64;eu-central-1.amazonses.com]\n<\/pre>\n<p>Explanation for the FORGED_SENDER rule:<\/p>\n<blockquote>\nSender is forged (different From: header and smtp MAIL FROM: addresses)<\/blockquote>\n<p>I'd like to know if there is a fix for that.<\/p>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/735\/rev-raw\/cf888466ca252da7e9c367022939621a123a2fb3\/README.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/735#README.rst\">README.rst<\/a>\n <\/div>\n<\/div>\n<\/div>\n"}