Hiya gang...
I'm setting up a listserv group for a friend here. I already have one up and running so I know the configuration is correct. The issue I'm seeing is when someone "subscribes", the reply they're receiving is:
TequilaMockingbird Online ListServ 1.39 Response:
As you can see there is no message after response. If I'm not mistaken the line:
response.body.push(subscription_control(cmd, list, address)) should be returned as much as
TequilaMockingbird Online ListServ 1.39 Response: Subscribed, [listname], [address]
Is there a possible bug in the javascript?
Also, is there anywany of stripping the MIME content of incoming mail
before it posts/gets distributed to other subscribers. A one line message works out to be 89 lines after all that MIME garbage is included.
On 12-08-14 17:15, Digital Man wrote to Bill McGarrity <=-
Hiya gang...
I'm setting up a listserv group for a friend here. I already have one up and running so I know the configuration is correct. The issue I'm seeing is when someone "subscribes", the reply they're receiving is:
TequilaMockingbird Online ListServ 1.39 Response:
As you can see there is no message after response. If I'm not mistaken the line:
response.body.push(subscription_control(cmd, list, address)) should be returned as much as
TequilaMockingbird Online ListServ 1.39 Response: Subscribed, [listname], [address]
Is there a possible bug in the javascript?
There's always the possibility of a bug. But if you're running the same version as your friend and if it's working correctly for you, then
perhaps it's not a bug and instead a problem with the sender's mail content.
How are they unsubscribing exactly - using the message subject?
Also, is there anywany of stripping the MIME content of incoming mail
before it posts/gets distributed to other subscribers. A one line message works out to be 89 lines after all that MIME garbage is included.
There's no built-in MIME decoding feature in the list server, no. That sounds like a good idea for a potential new feature though.
Is there a possible bug in the javascript?
There's always the possibility of a bug. But if you're running the
same version as your friend and if it's working correctly for you,
then perhaps it's not a bug and instead a problem with the sender's mail content.
The listserv is on my system. He just asked me to set one up for him. Everything in the configuration is the same as the original one I've been running for years and even that one will not pass any response when either subscribing or unsubscribing as well.
How are they unsubscribing exactly - using the message subject?
Yes, that is activated.
This is what I get when using "help" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
This is what I get when "lists" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
List of lists:
NJBC New Jersey Boxer Club
SBI Superstition Boxers Information
!Bad command: This
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
Why would it show a !Bad Command: This ??
On 12-08-14 22:59, Digital Man wrote to Bill McGarrity <=-
The listserv is on my system. He just asked me to set one up for him. Everything in the configuration is the same as the original one I've been running for years and even that one will not pass any response when either subscribing or unsubscribing as well.
How are they unsubscribing exactly - using the message subject?
Yes, that is activated.
This is what I get when using "help" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
This is what I get when "lists" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
List of lists:
NJBC New Jersey Boxer Club
SBI Superstition Boxers Information
!Bad command: This
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
Why would it show a !Bad Command: This ??
What was in the messaghge body? The message body is processed as a sequence of commands as well, so you could have a command in the
subject and more commands in the message body. My guess is that your message body contained "This". If you don't want to include commands in the message body, just leave it blank or put a tear line (---). Nothing after the tear line should be processed.
On 12-08-14 22:59, Digital Man wrote to Bill McGarrity <=-
The listserv is on my system. He just asked me to set one up for him. Everything in the configuration is the same as the original one I've
been running for years and even that one will not pass any response when either subscribing or unsubscribing as well.
How are they unsubscribing exactly - using the message subject?
Yes, that is activated.
This is what I get when using "help" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
This is what I get when "lists" on the subject line:
TequilaMockingbird Online ListServ 1.39 Response:
List of lists:
NJBC New Jersey Boxer Club
SBI Superstition Boxers Information
!Bad command: This
Available commands:
lists
subscribe [address]
unsubscribe [address]
help
end
Why would it show a !Bad Command: This ??
What was in the messaghge body? The message body is processed as a sequence of commands as well, so you could have a command in the subject and more commands in the message body. My guess is that your message body contained "This". If you don't want to include commands
in the message body, just leave it blank or put a tear line (---). Nothing after the tear line should be processed.
There was nothing in the body at all. Only thing I can think of is the possibility of the MIME being interpreted as "Then" even if using ---
I was right... here is the first part of the message that appears in the message that is posted even though the body is blank with the tearline
<--->
[quote]
This is a multipart message in MIME format.
------=_NextPart_000_013B_01D01314.288E9150
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_013C_01D01314.288E9150"
------=_NextPart_001_013C_01D01314.288E9150
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
[end quote]
Notice the "This" as the first word. So the MIME is causing issues...
Thanks for your help...
On 12-09-14 22:25, Digital Man wrote to Bill McGarrity <=-
On 12-08-14 22:59, Digital Man wrote to Bill McGarrity <=-
[snip]The listserv is on my system. He just asked me to set one up for him. Everything in the configuration is the same as the original one I've
been running for years and even that one will not pass any response when either subscribing or unsubscribing as well.
There was nothing in the body at all. Only thing I can think of is the possibility of the MIME being interpreted as "Then" even if using ---
I was right... here is the first part of the message that appears in the message that is posted even though the body is blank with the tearline
<--->
[quote]
This is a multipart message in MIME format.
------=_NextPart_000_013B_01D01314.288E9150
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_013C_01D01314.288E9150"
------=_NextPart_001_013C_01D01314.288E9150
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
[end quote]
Notice the "This" as the first word. So the MIME is causing issues...
Thanks for your help...
Ah, that's a good clue. Try getting the latest listserver.js from http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/exec/listserver.js
and
set BodyCommand=false in your ctrl/listserver.ini file. This will allow command *only* in the subject (assuming SubjCommand=true) and thus
ignore any MIME-encoded body text in control messages.
Let me know how that works for ya,
Let me know how that works for ya,
OK... updated everything as you requested and no longer do I get the "!Bad Message" in the body when using the subject line commands. I still don't get a full response for either subscribe or unsubscribe though...
Sysop: | Ree |
---|---|
Location: | Toronto, ON |
Users: | 2 |
Nodes: | 10 (0 / 10) |
Uptime: | 143:48:18 |
Calls: | 369 |
Files: | 2 |
Messages: | 38,453 |