Changes between Version 9 and Version 10 of filter-check

Timestamp:

Jan 11, 2018, 3:15:26 PM (8 years ago)

Author:

Jamie McClelland

Comment:

--

filter-check

@@ -28 +28 @@
 
 {{{
-filter-check --sendto SENDTO --sleep 30
+filter-check --sendto SENDTO --sendvia SENDVIA--sleep 30
 }}}
+
+For example, if the error is:
+
+{{{
+0 gil:~# grep filter-check /var/log/syslog
+Jan 11 09:14:37 gil filter-check: Exit code '1' fetching messageid '<20180111131202.9683.90646@gil.mayfirst.org>' from 'gmail' via 'localhost'
+0 gil:~#
+}}}
+
+That means a message sent to gmail via localhost ended up in the spam box. You can check to see if that is still happening with:
+
+{{{
+0 gil:~# filter-check --sendto gmail --sendvia localhost --sleep 30
+Message sent (Thu, 11 Jan 2018 15:13:32 -0000)
+Message-id: <20180111151332.17519.37006@gil.mayfirst.org>
+Sleeping for 30.0 seconds.
+Found in: Inbox
+
+ARC-Authentication-Results: i=1; mx.google.com;
+       spf=neutral (google.com: 216.66.23.48 is neither permitted nor denied by best guess record for domain of jamie@workingdirectory.net) smtp.mailfrom=jamie@workingdirectory.net
+Received-SPF: neutral (google.com: 216.66.23.48 is neither permitted nor denied by best guess record for domain of jamie@workingdirectory.net) client-ip=216.66.23.48;
+Authentication-Results: mx.google.com;
+       spf=neutral (google.com: 216.66.23.48 is neither permitted nor denied by best guess record for domain of jamie@workingdirectory.net) smtp.mailfrom=jamie@workingdirectory.net
+0 gil:~# 
+}}}
+
+This demonstrates that now messages are being properly delivered.
+
 
 If the exit code is "2" - you can manually login to the provider (see [wiki:keyringer] for all passwords) and see if the message eventually made it. Then you can debug the delay.