mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 21:15:56 +03:00
[GH-ISSUE #421] Sometimes, I attach a file to an email, and it's confirmed uploaded. But then, when I send, the attachment is not part of sent email #349
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#349
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marclaporte on GitHub (Aug 11, 2020).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/421
Originally assigned to: @jasonmunro on GitHub.
Seen by at least Jason and myself. No pattern to reproduce yet.
https://gitter.im/cypht-org/community?at=5f307abefe39ca5d65902d7c
@marclaporte commented on GitHub (Jan 21, 2021):
But I am 99% sure root cause is identical to this other bug we can replicate: https://github.com/jasonmunro/cypht/issues/420
@marclaporte commented on GitHub (Feb 10, 2021):
Ok, looks like I was wrong in previous message (!) But I am now 99% sure [ will I ever learn? :-) ] that it's related to https://github.com/jasonmunro/cypht/issues/436
To see some weirdness with attachments: On a message, click "forward", then back (with your browser), then forward again, etc. It is possible that on your first "forward" click, the email will be blank, and you'll have an attachment (mail.mime message/rfc822), then, on each browser "back" and Cypht "forward", you may end up with an extra attachment.
@marclaporte commented on GitHub (Mar 10, 2021):
I got this again with latest Tiki 21.x which includes https://github.com/jasonmunro/cypht/pull/453
But I can't find a pattern to reproduce.
@marclaporte commented on GitHub (Jun 22, 2021):
Related commit:
gitlab.com/tikiwiki/tiki/-@caf8c79387This likely solves the issue for Cypht in Tiki. But Jason had noticed this (or a similar issue) in standalone Cypht. So there is perhaps another issue, but that we can't reproduce.
So I will close this for now, and re-open if I see the behavior again.
@marclaporte commented on GitHub (Aug 27, 2021):
Victor found the issue. Merge request coming soon.
@marclaporte commented on GitHub (Sep 15, 2021):
Here is, with a good discussion: https://github.com/jasonmunro/cypht/pull/508
@marclaporte commented on GitHub (Oct 7, 2021):
@henrique-borba: With latest code, these are two issues:
How to reproduce:
1- Click to compose a new email
2- Fill out text fields
3- Click Save (it will confirm it saved a drat)
4- Upload an image
5- Send
Issues:
1- Email is sent without attachment
2- Draft email subsists in draft folder
Thanks!
@marclaporte commented on GitHub (Nov 4, 2021):
This will be solved by https://github.com/jasonmunro/cypht/pull/524
@marclaporte commented on GitHub (Feb 2, 2022):
It also needed https://github.com/jasonmunro/cypht/pull/548
@marclaporte commented on GitHub (Jul 10, 2022):
@NasserNgandu found a pattern which related to folder permissions where files are temporarily stored. He will add an error message if folder is not writable.
@marclaporte commented on GitHub (Jul 16, 2022):
Possible fix: https://github.com/jasonmunro/cypht/pull/575
@marclaporte commented on GitHub (Aug 19, 2022):
I haven't seen this issue in a while, so presuming fixed. Will re-open if I encounter again