Dre4m Shell
Server IP : 85.214.239.14  /  Your IP : 18.117.91.116
Web Server : Apache/2.4.62 (Debian)
System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64
User : www-data ( 33)
PHP Version : 7.4.18
Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
MySQL : OFF  |  cURL : OFF  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : OFF
Directory :  /proc/2/cwd/proc/2/root/proc/2/cwd/usr/share/doc/libmail-dkim-perl/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ HOME SHELL ]     

Current File : /proc/2/cwd/proc/2/root/proc/2/cwd/usr/share/doc/libmail-dkim-perl/common_verification_problems.txt
This document will attempt to record all root causes I've seen for
a "body of message has been altered" or "message has been altered"
DKIM verification result.


1. Incorrect use of Mail::DKIM's PRINT() method. The implementer fed
   the message in as it was received over SMTP, without reversing the
   "dot-stuffing".  So if the message contained any lines beginning
   with a period, the message would be signed or verified incorrectly.

Anon7 - 2022
AnonSec Team