• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Forwarded to devs SPF_FAIL for internally forwarded emails

@Kaspar Thank you very much. Finally, the developers could reproduce the bug and confirmed its existence. I'm looking forward to the fix.
 
Thank you. The bug PPPM-13801 has been confirmed and submitted.
 
Noticed this occurring recently since we bumped up the SPF_FAIL score. What's odd to me is that the mail server still records the Received-SPF header as a pass, yet Spamassassin apparently ignores this for its scoring. This is odd because `ignore_received_spf_header` is 0 and `use_newest_received_spf_header` is 0 by default. This would imply that it should be using the existing header, and yet it's not.
 
Back
Top