On 2/17/20 3:00 AM, Jeffrey D wrote:
Hi,
Today I sending an e-mail to "mylist-request@domain.tld" with the subject "help" and I received the expected e-mail with the following content;
confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: -- No such command: vriendelijke
Only I think my mail signature broke something in Mailman (see the No such command).
Something may be broken, but it was not your email command with signature that broke it.
Mail to the -request address processes the Subject: as a command if it appears to be one and then processes each of the first several (default 10) lines of the body as a command until it encounters a 'stop' or 'end' command or other command whos process says don't continue.
In this case your signature was reported as no such command. This is normal and expected.
Because every e-mail with a subject like "help", "stop" or "join", gives a reply with random characters. The Mailman logs doesn't show any error, so I'm not sure what is wrong. Deleting the mailinglist and create a new one won't fix the issue, also restarting Mailman doesn't help.
An example of the random characters: Nz zf&ju[zZ0:v,jzkb^}nJyazZCj}{m5t5C x<{iysG5o[w}jgn+g[lrwf *mz rL k)rjwliazZZnjyW(fvrh{aXXWj+&j)b b-'jX+zwl &v {rx &~y6.r(fu4:'
Is this a bug in Mailman? Or something in my Mailman config...
To understand what's going on, We would like to see the complete, raw response message. Also, the headers of the message sent to the -request address, in particular the Content-Type: header of the first text/plain part and its charset param.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan