Hi All
Im using Mailman core 3.3.4 on Ubuntu 20.04 with python 3.8 anf have this problem with email command join.
When send command to ml-request@
join address=some.email@domain.com
Response is: Confirmation email sent to 3dsome.email@domain.com
It add characters 3d to email and realy sent confirmation to it.
Also help command for join return me join [digest=<no|mime|plain>] [address=user@example.com]
But digest doesnt work as after command
join digest=no address=some.email@domain.com
i get
join bad argument: digest=no
I will be thankfull for any help/advice. S.
On 5/27/21 7:43 AM, sky.x--- via Mailman-users wrote:
Hi All
Im using Mailman core 3.3.4 on Ubuntu 20.04 with python 3.8 anf have this problem with email command join.
When send command to ml-request@
join address=some.email@domain.com
Response is: Confirmation email sent to 3dsome.email@domain.com
It add characters 3d to email and realy sent confirmation to it.
There is apparently a bug in command processing. The issue here is your join command is getting quoted-printable encoded by your MUA so it looks like
join address=3dsome.email@domain.com
where the =3d is the quoted-printable encoding of =. We need to
ensure that commands, are properly decoded.
Also help command for join return me join [digest=<no|mime|plain>] [address=user@example.com]
But digest doesnt work as after command
join digest=no address=some.email@domain.com
i get
join bad argument: digest=no
I think this is the same issue.
I also think this is fixed by the fix for https://gitlab.com/mailman/mailman/-/issues/859 at https://gitlab.com/mailman/mailman/-/merge_requests/822. This fix decodes the message body including commands in the message body. Commands in the message Subject: were already properly decoded in Mailman core 3.3.4 except possibly if the Subject: contained non-ascii.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
"sky" == sky x--- via Mailman-users <mailman-users@mailman3.org> writes:
sky> Hi All Im using Mailman core 3.3.4 on Ubuntu 20.04 with python sky> 3.8 anf have this problem with email command join.
Looks like your mailer is sending quoted-printable instead of plain text email. Quoted-printable will change all '=' characters into '=3D'. Can you send it as plain text?
(By the same token, MM3 should look at the mime-type and convert quoted printable to something it can understand)
Peter C
Thank you all.
@Mark, im fixed it from that issue and it works now.
@Peter, hmm interesting, im used Kopano webmail and message format is set to plain/text, also when i open bcc copy of raw message it looks as plain/text. I will test another client at the night hours.
On 5/28/21 5:34 AM, sky.x--- via Mailman-users wrote:
@Peter, hmm interesting, im used Kopano webmail and message format is set to plain/text, also when i open bcc copy of raw message it looks as plain/text. I will test another client at the night hours.
The QP encoding probably occurs because you have non-ascii in the message body - perhaps in a signature? If you view the raw message source of the Bcc, what do you see? In particular is there a
Content-Transfer-Encoding: quoted-printable
header?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yes you are correct, in header there is:
Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable
In message body i dont have any other non-ascii character. It looks like Kopano webmail set it by default and im not able to override it.
Anyway, the fix mentioned by you work. Thank you.
participants (3)
-
Mark Sapiro -
peter＠chubb.wattle.id.au -
sky.x＠nazelenej.sk