On Saturday 05 of September 2020 20:52:02 William Morder via tde-users
wrote:
On Saturday 05 September 2020 10:57:30 Slávek Banko
via tde-users wrote:
> On Saturday 05 of September 2020 04:05:36 William Morder via
> trinity-users
>
> via tde-users wrote:
> > On Friday 04 September 2020 03:07:14 Slávek Banko via tde-users
wrote:
> On Friday 04 of September 2020 11:59:20 Felix
Miata via tde-users
wrote:
> >
To subscribe to the new MLs either use the webinterface:
> >
> >
https://mail.trinitydesktop.org/mailman3/
>
> This method gives option to login first. Is this login different
> from the one for Bugzilla? It isn't accepting my Bugzilla
> username/password.
>
> :-(
It is not necessary to create an account - it is possible to
subscribe without creating an account.
The account is useful only if you would like to adjust the
parameters of posting or use the web interface for reading /
replying. In any case, there is no possible link to Bugzilla
accounts - these are separate accounts.
Cheers
I tried to subscribe by sending an email to the address provided,
but after several tries, I got blank email responses, then a
response to which I tried to send back my own response ... then
Kmail crashed. I tried sending another subscription email, but never
get a response.
The email sent to me by the server now contains no content. (See
attachment for screenshot.)
Bill
Hi Bill,
that's very strange. What appears when you open the source code of a
message ('v' key)? You can look at the eml / mbox content of the
message - what does it look like? You'd better send the results to a
private email.
Cheers
Hi Slavek,
I don't know if I can retrieve the rogue email in question. I already
moved it to trash (following Michael's suggestion), and when I rebooted,
it had disappeared. So, problem solved on my end, at least for that one
item. Whether that is a sign of some deeper problem is another matter.
Source code of email doesn't look unusual. I could paste it here, but
it's long.
Bill
_______________________________________________
The important thing is that it has been resolved - we probably don't need
to investigate further. I assumed it could be some problem with the
mailbox index in KMail.
Cheers
--
Slávek