![]() # This is the right place to customize your installation of SpamAssassin. It's for sure easy to activate this feature: Christian Heutger is stated another address then the from address, which has been really used (or faked). header from is still an issue, especially with PMG, as it only shows the envelope from and ESPs like Amazon SES or Mailchimp use this addresses to measure and manage bounces and "hide" that they if the sender misuse their service or a legit sender uses their service to deliver newsletter, status messages etc.), so placing there usually the senders name, e.g. It's called FromNameSpoof and is about the misuse of the name field to place addresses, which do not match the real from address (not only the technical one so envelope from vs. ![]() I thought about for a long time, but after recognizing, that for the large amount of option possibilities and combinations there are in contrast to my last introduced SpamAssassin features already some rules shipped with SpamAssassin and seem to have their score(s) comment out, so I can first have a try on any occurrence, I decided to activate this feature. There was one feature, I still saw being introduced with SpamAssassin 3.4.2 and I also so on Warden Anti-Spam for Plesk and considered, if I should use or not. This way required some adjustments on source.list to include the stretch-backports packages as it was a required dependency: Apt-get install packaging-dev debian-keyring devscripts equivsĪpt-get -t stretch-backports install debhelperĭch -local ~bpo9+ -distribution stretch-backports "Rebuild for stretch-backports."Īpt install. ![]()
0 Comments
Leave a Reply. |