Bug 19260

Summary:	Issues to post to dev mailing list
Product:	Infrastructure	Reporter:	Chris Denice <eatdirt>
Component:	Others	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11, pterjan, sysadmin-bugs
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	I don't know	CVE:
Status comment:

Description Chris Denice 2016-08-28 17:09:55 CEST

Description of problems:

Since the disappearance of the public frontends of gmane, and although the gmane server still works, I cannot post anymore using gmane. I think I am not alone in this situation and it would be nice to fix it, or to propose alternative solutions based on newsgroup style frontend. Getting thousand emails in a remote account is not an option for me.

Back to the standard method, posting and receiving directly mails from the mailing list has a weird behaviour. Although I can see my posted messages in the archives, for instance this one:

https://ml.mageia.org/l/arc/dev/2016-08/msg00732.html

these messages do not appear on gmane and some other users complained about not receiving my posts. I have no idea why...

Thanks!
Cheers,
chris.

Comment 1 Marja Van Waes 2016-08-29 16:10:40 CEST

I don't receive your messages, either, but when I manage to use the send back option on ml.mageia.org, then they end up in my spam box, because of 


    X-XS4ALL-Spam-Warning: Message moved to Spam location because of DMARC policy
	of protonmail.com


However, xs4all shouldn't bounce Mageia ml mails because of dmarc policies, and they still let the Yahoo DMARC ml mails of David Walser through, so I cannot understand what's going on.

CC: (none) => marja11

Comment 2 Pascal Terjan 2016-08-30 12:00:59 CEST

It seems to trigger a problem with sympa because of having Message-ID longer than 100 characters:

# grep bulkspool_table /var/log/mail/errors.log
Aug 28 16:47:53 alamut sympa[11177]: err Bulk::store() Unable to add message in bulkspool_table "INSERT INTO bulkspool_table (messagekey_bulkspool, messageid_bulkspool, message_bulkspool, lock_bulkspool, dkim_d_bulkspool, dkim_i_bulkspool, dkim_selector_bulkspool, dkim_privatekey_bulkspool, dkim_header_list_bulkspool) VALUES ('e850aa36ea37560d83de88e8eb7e9674', '<ISgNZf3Fhlz1okmiSt-w5QqF2r4tfbbCKPSQ7N-ZJtV5QOQgq4w9Zo3ANTyGI-Vmvub24wKglR_hw2IJ3AQZSA==@protonmail.com>', 'UmV0dXJuLVBhdGg6IDxlYXRkaXJ0QHByb3Rvbm1haWwuY29tPgpSZWNlaXZlZDogZnJvbSBsb2Nh#012bGhvc3QgKGxvY2FsaG9zdCB', 1, NULL ,NULL ,NULL, '', NULL)"; error : ERROR:  value too long for type character varying(100)
Aug 28 16:47:54 alamut sympa[11177]: err Bulk::store() Unable to add message in bulkspool_table "INSERT INTO bulkspool_table (messagekey_bulkspool, messageid_bulkspool, message_bulkspool, lock_bulkspool, dkim_d_bulkspool, dkim_i_bulkspool, dkim_selector_bulkspool, dkim_privatekey_bulkspool, dkim_header_list_bulkspool) VALUES ('c48c25d8995132b21aa8e2da629bc1c7', '<ISgNZf3Fhlz1okmiSt-w5QqF2r4tfbbCKPSQ7N-ZJtV5QOQgq4w9Zo3ANTyGI-Vmvub24wKglR_hw2IJ3AQZSA==@protonmail.com>', 'TUlNRS1WZXJzaW9uOiAxLjAKQXV0by1TdWJtaXR0ZWQ6IGF1dG8tcmVwbGllZApGcm9tOiBTWU1Q#012QSA8c3ltcGFAbWwubWFnZWl', 1, NULL ,NULL ,NULL, '', NULL)"; error : ERROR:  value too long for type character varying(100)
Aug 29 21:48:52 alamut sympa[11177]: err Bulk::store() Unable to add message in bulkspool_table "INSERT INTO bulkspool_table (messagekey_bulkspool, messageid_bulkspool, message_bulkspool, lock_bulkspool, dkim_d_bulkspool, dkim_i_bulkspool, dkim_selector_bulkspool, dkim_privatekey_bulkspool, dkim_header_list_bulkspool) VALUES ('e025b7d1742ce6c544c11e280f3f43fa', '<wVMak2HRkcN4G9QQoJ_Y1h8YyKDNBifg_PKRpn2MHObBwI3cH04x3MOTlhwfXjwq9ocDknAKlypIVaGzZv7CwQ==@protonmail.com>', 'UmV0dXJuLVBhdGg6IDxlYXRkaXJ0QHByb3Rvbm1haWwuY29tPgpSZWNlaXZlZDogZnJvbSBsb2Nh#012bGhvc3QgKGxvY2FsaG9zdCB', 1, NULL ,NULL ,NULL, '', NULL)"; error : ERROR:  value too long for type character varying(100)
Aug 29 21:48:53 alamut sympa[11177]: err Bulk::store() Unable to add message in bulkspool_table "INSERT INTO bulkspool_table (messagekey_bulkspool, messageid_bulkspool, message_bulkspool, lock_bulkspool, dkim_d_bulkspool, dkim_i_bulkspool, dkim_selector_bulkspool, dkim_privatekey_bulkspool, dkim_header_list_bulkspool) VALUES ('f660fa585b9d7d91847de37208db53f9', '<wVMak2HRkcN4G9QQoJ_Y1h8YyKDNBifg_PKRpn2MHObBwI3cH04x3MOTlhwfXjwq9ocDknAKlypIVaGzZv7CwQ==@protonmail.com>', 'TUlNRS1WZXJzaW9uOiAxLjAKQXV0by1TdWJtaXR0ZWQ6IGF1dG8tcmVwbGllZApGcm9tOiBTWU1Q#012QSA8c3ltcGFAbWwubWFnZWl', 1, NULL ,NULL ,NULL, '', NULL)"; error : ERROR:  value too long for type character varying(100)

This looks like a bug in sympa as I am not aware of such limitation on Message-ID length in RFCs.

CC: (none) => pterjan

Comment 3 Pascal Terjan 2016-08-30 12:03:14 CEST

It seems this is no longer stored in DB starting in Sympa 6.2, so I guess another problem that will get fixed when we manage to upgrade...

Comment 4 Pascal Terjan 2016-08-30 12:04:35 CEST

Or maybe not, as we switched to 6.2 for Mageia 6 but Mageia 5 still has 6.1.x,,,