Package: smartlist
Version: 3.15-22
Severity: normal
Tags: patch upstream

Greetings Santiago,

long time no mail. I was trying out smartlist and I encountered a
problem in the confirmation process: I couldn't get subscribed when
replying to the confirmation mail. After some time trying to understand
what was going on (and getting familiar with procmail syntax), I finally
stumbled upon the condition "* B ?? < 4096" at the beginning of
rc.request.

So what happens is that the script checks for the size of the body of
the email before doing anything. So, since all my emails are signed by
default and the confirmation message include the original subscription
request, the body became too big and the confirmation wasn't checked.

Actually there is a comment saying it but I didn't realize it was
talking about the size of the body:

# We now check:
#       If the length is roughly within bounds.
#       That it is not a reply or something.
#       That we didn't send it ourselves.
#       That it wasn't sent by a daemon of some kind.

So of course it is clear from this comment that the patch I propose
would not be accepted upstream but maybe it's possible with a procmail
rule to cut the message to keep the first 4096 bytes instead of checking
the size is within this bound.

Best regards,

Thomas

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/SmartList/etc/rc.request b/SmartList/etc/rc.request
index 15e8521..57aca06 100644
--- a/SmartList/etc/rc.request
+++ b/SmartList/etc/rc.request
@@ -53,7 +53,6 @@ Maintainer=Maintainer
 }
 
 :0
-* B ?? < 4096
 * $$daemon_bias
 * $!^(X-(Loop: $\listaddr|Diagnostic:)|$X_COMMAND:)
 * -100^0 ^FROM_DAEMON

Reply via email to