about summary refs log tree commit homepage
path: root/t
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2017-06-23 02:25:33 +0000
committerEric Wong <e@80x24.org>2017-06-23 02:32:35 +0000
commit666844ae42b5b17fd2e9b7ea6cf04727487b5322 (patch)
tree887824678cd482404c8f4b789eae1ed29114c1c4 /t
parent59b3f7584817735a69b45388fd2d4c40750cf6e4 (diff)
downloadpublic-inbox-666844ae42b5b17fd2e9b7ea6cf04727487b5322.tar.gz
reply: handle address obfuscation :<
We can show users a lightly-obfuscated Bourne shell command
for invoking "git send-email" for address obfuscation.  However,
I'm not sure if the mailto: arg will work effectively since
URL encoding is probably too well-known to be effective.
Diffstat (limited to 't')
-rw-r--r--t/reply.t12
1 files changed, 12 insertions, 0 deletions
diff --git a/t/reply.t b/t/reply.t
index 640069cb..719b4e47 100644
--- a/t/reply.t
+++ b/t/reply.t
@@ -64,4 +64,16 @@ $ibx->{replyto} = 'new@example.com';
 $exp = [ '--in-reply-to=blah@example.com', '--to=new@example.com' ];
 is_deeply($arg, $exp, 'explicit address works, too');
 
+$ibx->{replyto} = ':all';
+$ibx->{obfuscate} = 1;
+($arg, $link) = PublicInbox::Reply::mailto_arg_link($ibx, $hdr);
+$exp = [
+    '--in-reply-to=blah@example.com',
+    '--to=from@example$(echo .)com',
+    '--cc=cc@example$(echo .)com',
+    '--cc=to@example$(echo .)com'
+];
+is_deeply($arg, $exp, 'address obfuscation works');
+is($link, '', 'no mailto: link given');
+
 done_testing();