mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #378] Date vs arrival: A little confusing and perhaps a bug when moving messages #319
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#319
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 (Feb 24, 2020).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/378
Originally assigned to: @jasonmunro on GitHub.
A few things:
When viewing one message, and in the message list, we can see the sent date, but not the arrival date. I wonder if we should add as an option?
I moved messages from one IMAP account to another (via Cypht): I didn't expect this to change any dates, but the arrival date seems to have changed. On one hand, it makes sense because I did move the emails. But it was not received on the date I moved... This is an edge case... What do you think?
Thanks!
Marc
@jasonmunro commented on GitHub (Mar 2, 2020):
Good point. It is a bit of an edge case, but maybe date makes more sense. I settled on arrival a long time ago over the date header, but I'm not sure the reasoning from 15 years ago still applies.
@dumblob commented on GitHub (Mar 3, 2020):
My preference would be to support either both or at least change
DatetoArrival date😉.@marclaporte commented on GitHub (Mar 13, 2020):
@marclaporte commented on GitHub (Mar 13, 2020):
Indicating "arrival date" vs "sent date" is an easy thing to fix, and we'll do it.
My other topic is that when I move the email from one account to another, the data of one of the dates changes. Is this a bug or a feature?
Thanks!
@Yamakasi commented on GitHub (Apr 22, 2020):
This is seriously a legal thing that needs to be overthought a couple of times.
Sent or Arrival date can be much earlier when you use mailrelays which are spooling for a a while because some other relay of the IMAP server is not available.
If someone asks for a delivery notice things can go terrible wrong, it's also how you setup your whole mailcluster so I think Date is the most safe one to use.
@jasonmunro commented on GitHub (May 5, 2020):
@marclaporte the arrival date is managed by the IMAP server, so moving the message from one account to another resets it. It is not a part of the real E-mail headers per say.
@Yamakasi I think originally, a LONG time ago, I chose arrival date instead of the sent date because it was a performance boost for IMAP servers at the time, and was usually very similar. We should probably switch to the date header.
@marclaporte commented on GitHub (May 6, 2020):
@jasonmunro yes, let's please use sent date by default.
@kroky commented on GitHub (Jul 31, 2020):
Please check PR #418 . Marc, the arrival date has been added as part of the extended headers. Not sure we want to spam short headers with one more date field.
@marclaporte commented on GitHub (Jul 31, 2020):
Indeed, short header should how just one date (sent date)
@marclaporte commented on GitHub (Oct 29, 2020):
The default is now "sent date".