-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to reply with full, raw headers #85
Comments
I have scheduled it for coming release. |
That's fantastic. Thank you very much. Sent from my iPad
|
Can you please try v5.0-beta and share your feedback? |
The installation/upgrade went without a problem. I wish I had better news to report on the testing, but as soon as I check the "Include all headers" box, I can no longer reply, reply-all, or forward. The buttons visually indicate being pressed, but nothing happens. I tried with various combinations of other from, to & CC, and header quoting sequence and labels, including all on default. I was unable to get a response to reply, reply-all, or forward buttons. It did not matter if the buttons were pressed on the main mail screen or on an individual message windows brought up by double-clicking a message. I am running: Please let me know if there is any additional information or testing you need and I will make it a priority.
|
Can you please enable RWH debug using below command and restart the Mail.app?
Now watch Console.app for any errors from Mail.app. |
Certain message headers were causing an issue in Yosemite. I have applied the fix. Can you please download updated beta version here (https://app.box.com/s/qta2i4osh2lz9f2jojjg1j98fd762sdo) Kindly let me know the outcome! |
Sorry for the delay in replying. With the box unchecked, it looks good. With it checked, pressing the Reply button results in: 5/29/15 2:05:00.170 AM Mail[2837]: *** Assertion failure in -[MCMessageHeaders headersForKey:], /SourceCache/Mail/Mail-2100/MailCore/Message/MCMessageHeaders.m:735
|
Hi. Sorry to report that it is still not working. But the console contains a much more lengthy set of messages now when the Reply button is pressed: 5/29/15 2:12:04.431 AM Mail[3610]: MHHeadersEditor.m: 87 msgComposeType: 1
5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 214 Composing mail isHTMLMail YES 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 220 initVars Header border text: 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 176 isBlockquotePresent = YES 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 386 No of child nodes: 1 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 391 getBlockquoteTagNode:: BLOCKQUOTE Node found at 0 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 315 Handling remaining locale by Regex 5/29/15 2:12:04.513 AM Mail[3610]: MHQuotedMailOriginal.m: 325 Before while loop, Text range is {76, 2} 5/29/15 2:12:04.514 AM Mail[3610]: MHQuotedMailOriginal.m: 343 Node name: DIV, Node Type: 1, Node Value: On May 29, 2015, at 2:02 AM, Jeevanandam M. [email protected] wrote: 5/29/15 2:12:04.514 AM Mail[3610]: MHHeaderString.m: 188 From User defaults choosenLocaleIdentifier en 5/29/15 2:12:04.515 AM Mail[3610]: MHHeaderString.m: 225 Before cleanup allHeaderKeys:: ( received, date, "dkim-signature", from, "reply-to", to, cc, "message-id", "in-reply-to", references, subject, "mime-version", "content-type", "content-transfer-encoding", precedence, "x-github-sender", "x-github-recipient", "x-github-reason", "list-id", "list-archive", "list-post", "list-unsubscribe", "x-auto-response-suppress", "x-github-recipient-address", "x-rcpt-to", "return-path" ) 5/29/15 2:12:04.515 AM Mail[3610]: MHHeaderString.m: 243 Key: reply-to, Values: jeevatkm/ReplyWithHeader [email protected] 5/29/15 2:12:04.516 AM Mail[3610]: MHHeaderString.m: 248 After cleanup allHeaderKeys:: ( received, "dkim-signature", "message-id", "in-reply-to", references, "mime-version", "content-type", "content-transfer-encoding", precedence, "x-github-sender", "x-github-recipient", "x-github-reason", "list-id", "list-archive", "list-post", "list-unsubscribe", "x-auto-response-suppress", "x-github-recipient-address", "x-rcpt-to", "return-path" ) 5/29/15 2:12:04.516 AM Mail[3610]: **\* Assertion failure in -[MCMessageHeaders headersForKey:], /SourceCache/Mail/Mail-2100/MailCore/Message/MCMessageHeaders.m:735 5/29/15 2:12:04.516 AM Mail[3610]: Use -messageIDListForKey: for message ID header keys 5/29/15 2:12:04.517 AM Mail[3610]: ( 0 CoreFoundation 0x00007fff9282e03c **exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff971f376e objc_exception_throw + 43 2 CoreFoundation 0x00007fff9282de1a +[NSException raise:format:arguments:] + 106 3 Foundation 0x00007fff90cf88cb -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195 4 MailCore 0x00007fff9260177d -[MCMessageHeaders headersForKey:] + 350 5 ReplyWithHeader 0x0000000115576854 ReplyWithHeader + 10324 6 ReplyWithHeader 0x000000011557aa7a ReplyWithHeader + 27258 7 Mail 0x000000010ee83948 Mail + 514376 8 Mail 0x000000010ee832f2 Mail + 512754 9 Mail 0x000000010ee80452 Mail + 500818 10 CoreFoundation 0x00007fff927057bc __invoking_** + 140 11 CoreFoundation 0x00007fff92705612 -[NSInvocation invoke] + 290 12 MailCore 0x00007fff92656a14 -[MCThrowingInvocationOperation main] + 48 13 MailCore 0x00007fff925e815e -[MCMainThreadInvocationOperation main] + 55 14 Foundation 0x00007fff90cc2d00 **NSThreadPerformPerform + 293 15 CoreFoundation 0x00007fff9274aa01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION** + 17 16 CoreFoundation 0x00007fff9273cb8d __CFRunLoopDoSources0 + 269 17 CoreFoundation 0x00007fff9273c1bf __CFRunLoopRun + 927 18 CoreFoundation 0x00007fff9273bbd8 CFRunLoopRunSpecific + 296 19 HIToolbox 0x00007fff986ef56f RunCurrentEventLoopInMode + 235 20 HIToolbox 0x00007fff986ef2ea ReceiveNextEventCommon + 431 21 HIToolbox 0x00007fff986ef12b _BlockUntilNextEventMatchingListInModeWithFilter + 71 22 AppKit 0x00007fff8b4dc98b _DPSNextEvent + 978 23 AppKit 0x00007fff8b4dbf38 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 24 AppKit 0x00007fff8b4d1bd3 -[NSApplication run] + 594 25 AppKit 0x00007fff8b44e324 NSApplicationMain + 1832 26 libdyld.dylib 0x00007fff8c0445c9 start + 1 27 ??? 0x0000000000000001 0x0 + 1 ) 5/29/15 2:12:50.550 AM mDNSResponder[90]: _kerberos.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.550 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record _kerberos.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com. type 16 failed with error -65560 5/29/15 2:12:50.550 AM mDNSResponder[90]: Fred’s\032Mac\032Pro._device-info._tcp.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.551 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record Fred’s\032Mac\032Pro._device-info._tcp.279246790.members.btmm.icloud.com. type 16 failed with error -65560 5/29/15 2:12:50.551 AM mDNSResponder[90]: _services._dns-sd._udp.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.551 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record _services._dns-sd._udp.279246790.members.btmm.icloud.com. type 12 failed with error -65560 5/29/15 2:12:50.551 AM mDNSResponder[90]: _services._dns-sd._udp.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.551 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record _services._dns-sd._udp.279246790.members.btmm.icloud.com. type 12 failed with error -65560 5/29/15 2:12:50.551 AM mDNSResponder[90]: _autotunnel.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.551 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record _autotunnel.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com. type 1 failed with error -65560 5/29/15 2:12:50.551 AM mDNSResponder[90]: _autotunnel._udp.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com.: bad signature 5/29/15 2:12:50.551 AM mDNSResponder[90]: hndlRecordUpdateReply: Registration of record _autotunnel._udp.Freds-Mac-Pro-2.279246790.members.btmm.icloud.com. type 33 failed with error -65560
|
@Fmaxwell Thanks for your time. I'm sorry about back & forth. This is strange. Let's do following things to narrow down the problem. Step 1: Please turn off the RWH debug mode and Close Mail.app defaults write com.apple.mail MHDebugLog -bool false Step 2: Please download updated version v5.0-beta here (http://docs.myjeeva.com/rwh/ReplyWithHeader-v5.0-beta.zip) Thanks again! |
First, no apologies are necessary! You’re quickly implementing a feature that I requested and I am happy to help however I can (especially since I’m retired as of last year). It works! See below. Could I have caused the problem previously by not restarting mail after the installation of RWH 5.0 beta? If so, I apologize. I did the following: Downloaded the package Below is the console output followed by the message: 5/29/15 3:19:46.073 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
|
I'm happy it's working for you :) yes Mail.app requires restart every time after any plugin installation (including RWH). Coming to your concern, Github makes every conversation about this issue as public. Please have a look on this page #85 and let me know. So I clean up private thing into For private/direct conversation, please use my email id [email protected]. |
I am sorry that I cost you so much time. I installed and the preferences were immediately available, so I did not know. I’m used to the Firefox model where most plugins work without restart and those that require restart clearly indicate it. You may wish to modify your install script to tell the user to restart mail. Thanks so much. You’ve provided a tool that’s going to be invaluable for those of us who have to, or choose to, report spam, phishing, and malware spread through email. P.S. I have gone through and removed personal information, including email addresses that I did not wish to have visible (and accessible to spammers). |
I'm glad it worked for you, Thanks. Let me know if you come across any issue. |
Feature request: Add the ability to reply with the full, raw headers, including "Received:" headers with IP addresses. That's what I was looking for when I found the ReplyWithHeader plugin.
Replying with the full, raw headers is a necessary feature for people who report spammers, phishing attacks, criminal scams (Nigerian 419, craigslist vehicle pay-with-Western-Union, etc.), and malware payloads and links sent by email. These headers are needed by network abuse departments and law enforcement agencies for their investigations.
The text was updated successfully, but these errors were encountered: