Оно. Рекомендую написать листмастеру. Я писал. Вот результат:
> On Tue, 13 Jun 2017, artiom wrote: >> 13.06.2017 18:42, Don Armstrong пишет: >>> On Tue, 13 Jun 2017, artiom wrote: >>>> Problem repeated. >>> >>> I think this is happening because procmail thinks the body is empty of >>> these messages. Can you attach the messages in a mail to >>> [email protected]? [This will help us see the complete headers >>> of the message and how the body was structured, instead of however >>> thunderbird decides to mangle them inline.] >> >> first.eml - initial message. >> second.eml - additional message (reply to first). > > Awesome; thanks. I think that's definitely what's going on with the > second message; not sure about the first one. I'll try to figure out how > to adjust the procmail recipe to better handle non-ASCII languages. > > Ok, thank you. Возможно, ещё несколько писем от разных людей его сподвигнут пофиксить баг. 21.06.2017 00:26, sergio пишет: > On 21/06/17 00:24, sergio wrote: >> On 21/06/17 00:19, artiom wrote: >>> >>> >>> 20.06.2017 23:10, sergio пишет: >>>> >>>> рассылка-хуилка ведёт себя как говно-хуивно >>>> этот текст тут для того, что бы письмо ушло в рассылку >>>> >>>> >>> Присылает хелп? >> >> я уже стёр, не помню, что-то типа того >> >> > > такое письмо от [email protected] > > General info > ------------ > Subscription/unsubscription/info requests should always be sent to > the -request address of a mailing list. > > If a mailing list is called for example "[email protected]", then > the -request address can be inferred from this to be: > "[email protected]". > > To subscribe to a mailing list, simply send a message with the word > "subscribe" > in the Subject: field to the -request address of that list. > > To unsubscribe from a mailing list, simply send a message with the word (you > guessed it :-) "unsubscribe" in the Subject: field to the -request > address of > that list. > > In the event of an address change, it would probably be the wisest to first > send an unsubscribe for the old address (this can be done from the new > address), and then a new subscribe to the new address (the order is > important). > > Most (un)subscription requests are processed automatically without human > intervention. > > Do not send multiple (un)subscription or info requests in one mail. > Only one will be processed per mail. > > NOTE: The -request server usually does quite a good job in discriminating > between (un)subscribe requests and messages intended for the > maintainer. > If you'd like to make sure a human reads your message, make it look > like a reply (i.e. the first word in the Subject: field should be > "Re:", > without the quotes of course); the -request server does not react to > replies. > > > The archive server > ------------------ > Every submission sent to this list is archived. The size of the archive > depends on the limits set by the list maintainer (it is very well possible > that only, say, the last two mails sent to the list are still archived, the > rest might have expired). > > You can look at the header of every mail coming from this list to see > under what name it has been archived. The X-Mailing-List: field contains > the mailaddress of the list and the file in which this submission was > archived. > > If you want to access this archive, you have to send mails to the -request > address with the word "archive" as the first word of your Subject:. > To get you started try sending a mail to the -request address with > the following: > Subject: archive help > > > The listmaster > -------------- > To reach a human being answering your mail you may contact the address > [email protected]. We will process your request as soon as > we can. > > Mail sent to this address is pre-parsed, a little mail robot will > automatically answer all mails sent with the following Subject lines: > > help sends this help > > lists sends information on how to get a list of mailing lists > > >
