Incident: inline.txt attached in mails

Ticketed at https://jira.kopano.io/browse/KC-624

darootler

@jengelh

Would it be possible to make that ticket public viewable?

Regards
Richard

That would make sense, yeah :-)

darootler

@jengelh

Thank you :thumbsup:

Regards
Richard

darootler

Hi,

in https://jira.kopano.io/browse/KC-624 @fbartels mentioned that this issue is fixed in version 8.4.0-792. I am not able to verify this fix because if i try to open the testmail via webapp i am getting “Could not open message”. On an iPhone i see an attachment called “inline.bin”.

Regards
Richard

fbartels

KC-624 is about inline images being shown as an attachment called inline.txt. This is now displayed as inline.jpg (or a different file extension based on the mime type). If you don’t see the mail body then it appears you are having a different error.

darootler

@fbartels

If you follow the steps described above, do you get an email with inline.bin? For me it doesn’t matter if the attachment is called “inline.txt” or “inline.bin”, i am still receiving an unreadable email.

So, what i have to do now to get the problem confirmed?

Regards
Richard

fbartels

I did not (yet) try your steps from above, I was merely pointing out that the ticket you are referencing seems to describe a different problem.

So, what i have to do now to get the problem confirmed?

having patience until some has free time to look at this or get a subscription and open a support call to raise priority.

darootler

@fbartels

Just to clarify:

The ticket https://jira.kopano.io/browse/KC-624 linked from @jengelh is just misleading and not fixing the issue described above.

And sorry for the following words but i have to point that out:

I am investing much time to do the “testing part” for you, seems like you do not have any testers for the daily builds, and all i earn is “get a subscription”. What i do is just work for you!

All this never happened during the times the product was called zarafa…

Regards
Richard

@darootler “Could not open message” is due to KC-709. Code for it exists, I temporarily uploaded that to https://github.com/jengelh/kopano-core/tree/kc-709 .

darootler

Seems like there a three issues mixed in this thread:

1.) inline.txt --> https://jira.kopano.io/browse/KC-624
2.) “Could not open message” --> https://jira.kopano.io/browse/KC-709
3.) inline.bin --> Seems like this is not covered

If you want to reproduce the “inline.bin” problem just follow the steps mentioned in the thread start.

Regards
Richard

https://jira.kopano.io/browse/KC-713 for this one then.

darootler

@jengelh

Thank you.

Regards
Richard

Your email (first post of this thread) uses “Content-Transfer-Encoding: 8bits”, which is not a standard recognized encoding. As such, the entire e-mail is placed into inline.bin, not just the QNAP logo.
I think you need to tell QNAP that it’s supposed to be “8BIT”, not “8bits”.

darootler

This post is deleted!

darootler

@jengelh

Thank you for pointing that out, i just submitted a ticket to QNAP.

Regards
Richard

fbartels

@darootler said in Incident: inline.txt attached in mails:

The ticket https://jira.kopano.io/browse/KC-624 linked from @jengelh is just misleading and not fixing the issue described above.

that’s what I was saying all along. it does describe something different, than in your first post.

I am investing much time to do the “testing part” for you, seems like you do not have any testers for the daily builds, and all i earn is “get a subscription”. What i do is just work for you!

The master branch is indeed only fully tested and qa’ed once it has been branched off for a release until that point it will only receive punctual tests (apart from a battery of automated tests).

But in open source its the mutual agreement that for the software/code that you receive you contribute back, either by giving feedback in case you encountered an error or pushing back code for such errors and new features.

All this never happened during the times the product was called zarafa…

Mostly since you now work on the master branch instead fenced off releases and we have been busy over the last few releases in refactoring the majority of the code.