Taking a look at the RFC, my explanation is incorrect. Separators
lines are defined as two dashes followed by the separator. Looking
closer at the message, it appears that the message separates lines by
/n instead of the required /r/n characters. I know that the mail gem
has a bit of code to rec
The answer I'm about to give is not likely to be very enlightening.
That particular message, when parsed by the Ruby mail gem, has no attachments.
https://whimsy.apache.org/secretary/workbench/201811/f19c4032c4/
If you look at the raw version of the message, you will see
boundary="=_NextPart
A mail received by secretary@ this morning at 3:28 AM Pacific was not delivered
to the workbench. It was forwarded to my apache.clr address.
Any ideas what went wrong? Here are the headers:
大步流星 <835576...@qq.com>
yizhenqiang-dubbo ICLA
To: Secretary
Dkim-Signature: v=1; a=rsa-sha256; c=rela
Can we please take another look at this issue? I'm afraid it might start to
affect account creation since no email with the vote result is being sent to
root.
Thanks,
Craig
> On Oct 30, 2018, at 8:00 PM, Sam Ruby wrote:
>
> On Tue, Oct 30, 2018 at 10:43 PM Sam Ruby wrote:
>>
>> It would be
