| uid | sender | to | subject | cc | bcc | status | error_msg | attachments | create_time | update_time |
|---|---|---|---|---|---|---|---|---|---|---|
c11511f2...6bcd9a20 | 寄件者顯示名稱 <sender@example.com> | 郵件主旨 | pending | 2024-05-24T11:39:40.913120 | 2024-05-24T11:39:40.913120 | |||||
bbc43627...d9b9cf16 | 寄件者顯示名稱 <terry.lin@goodfinance.com> | terry.lin@goodfinance.com | 郵件主旨 | success | 2024-05-13T17:27:01.110995 | 2024-05-13T17:27:01.110995 | ||||
4597513d...0b7c8ec0 | 寄件者顯示名稱 <sender@example.com> | terry.lin@goodfinance.com | 郵件主旨 | failed | S3 operation failed; code: NoSuchKey, message: The specified key does not exist., resource: /owl-email-attachment/4597513d-f54b-46d4-b6d5-38120b7c8ec0/, request_id: 17CF0211D9373CE6, host_id: 86ed6149-01da-4aea-b20c-e8ef7880bc41, bucket_name: owl-email-attachment, object_name: 4597513d-f54b-46d4-b6d5-38120b7c8ec0/ | 2024-05-13T17:24:12.993064 | 2024-05-13T17:24:12.993064 | |||
4aaf0810...83ae330d | 寄件者顯示名稱 <sender@example.com> | terry.lin@goodfinance.com | 郵件主旨 | failed | S3 operation failed; code: NoSuchKey, message: The specified key does not exist., resource: /owl-email-attachment/4aaf0810-c875-4c63-9a60-ae3d83ae330d/, request_id: 17CF020254133A37, host_id: 86ed6149-01da-4aea-b20c-e8ef7880bc41, bucket_name: owl-email-attachment, object_name: 4aaf0810-c875-4c63-9a60-ae3d83ae330d/ | 2024-05-13T17:23:11.040493 | 2024-05-13T17:23:11.040493 | |||
c5ed0b10...be30ac1f | 寄件者顯示名稱 <sender@example.com> | terry.lin@goodfinance.com | 郵件主旨 | failed | S3 operation failed; code: NoSuchKey, message: The specified key does not exist., resource: /owl-email-attachment/c5ed0b10-8ce0-4c08-8c84-b3a4be30ac1f/, request_id: 17CF01D2BF01C6C9, host_id: 86ed6149-01da-4aea-b20c-e8ef7880bc41, bucket_name: owl-email-attachment, object_name: c5ed0b10-8ce0-4c08-8c84-b3a4be30ac1f/ | 2024-05-13T17:19:47.531655 | 2024-05-13T17:19:47.531655 | |||
ae617ddd...637637f3 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, receiver1@example.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | success | 檔案名稱.pdf | 2024-05-13T17:19:01.440782 | 2024-05-13T17:19:01.440782 | |
d4473841...d0f15aed | Owl Service <sender@example.com> | chris.luo@goodfinance.com, ming.tsou@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-23T17:00:54.801374 | 2024-04-23T17:00:54.801374 | |
5e44c780...1d737c96 | Owl Service <sender@example.com> | chris.luo@goodfinance.com, tony@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | success | 檔案名稱.pdf | 2024-04-23T17:00:44.464792 | 2024-04-23T17:00:44.464792 | |
0ae068cb...c9458e75 | 寄件者顯示名稱 <sender@example.com> | Chris Luo <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | success | 檔案名稱.pdf | 2024-04-22T09:53:12.854814 | 2024-04-22T09:53:12.854814 | |
ac153210...6b659f84 | 寄件者顯示名稱 <sender@example.com> | Chris Luo <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | success | 檔案名稱.pdf | 2024-04-22T09:52:32.338874 | 2024-04-22T09:52:32.338874 | |
7ad1dbf2...950e9f9f | 寄件者顯示名稱 <sender@example.com> | Chris Luo <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | success | 檔案名稱.pdf | 2024-04-22T09:50:20.403265 | 2024-04-22T09:50:20.403265 | |
ec37c0b5...28503731 | 寄件者顯示名稱 <sender@example.com> | Chris Luo <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-22T09:47:29.603892 | 2024-04-22T09:47:29.603892 | |
1ab29a3a...b7afe4ff | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:29:10.264584 | 2024-04-19T18:29:10.264584 | |
898700bb...85e2dbd9 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:28:27.693944 | 2024-04-19T18:28:27.693944 | |
cfe6103d...90f41014 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:24:40.652918 | 2024-04-19T18:24:40.652918 | |
a8b69339...55d3c420 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, tony@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:24:18.173422 | 2024-04-19T18:24:18.173422 | |
d0a64fa2...05cf07d4 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, tony@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:23:48.925847 | 2024-04-19T18:23:48.925847 | |
06320ccd...963e0122 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱.pdf | 2024-04-19T18:21:52.715992 | 2024-04-19T18:21:52.715992 | |
1bbaa1a1...d80d4ca4 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱1.pdf | 2024-04-19T18:21:31.377798 | 2024-04-19T18:21:31.377798 | |
7f38d429...094d5ff2 | 寄件者顯示名稱 <sender@example.com> | 收件者顯示名稱 <receiver1@example.com>, chris.luo@goodfinance.com | 郵件主旨 | 副本收件者顯示名稱 <receiver1@example.com> | 密件副本收件者顯示名稱 <receiver1@example.com> | invalid | 檔案名稱1.pdf | 2024-04-19T18:20:50.791014 | 2024-04-19T18:20:50.791014 |