email-processing

Why isn't Gmail using quoted-printable encoding?

99封情书 提交于 2019-11-30 20:04:32
Why the web-version of Gmail line-wrap its mail content without marking the breaking place with a = , which make email processing very difficult: See the original mail content sent by gmail: and this mail sent by Mac OS X Mail: Edited: As Brandon Invergo said, they are using different encoding method. I am sorry that I said GMail is not decent. Edited 2: Their original content are: They are wrapped in Gmail, I guess it is according to word-wrap algorithm . John McManigle So, there are two separate issues here, and GMail is doing one of them "a different way" and one of them "the wrong way."

Is it possible to programmatically 'clean' emails?

混江龙づ霸主 提交于 2019-11-30 18:02:18
问题 Does anyone have any suggestions as to how I can clean the body of incoming emails? I want to strip out disclaimers, images and maybe any previous email text that may be also be present so that I am left with just the body text content. My guess is it isn't going to be possible in any reliable way, but has anyone tried it? Are there any libraries geared towards this sort of thing? 回答1: In email, there is couple of agreed markings that mean something you wish to strip. You can look for these

Why isn't Gmail using quoted-printable encoding?

杀马特。学长 韩版系。学妹 提交于 2019-11-30 04:50:47
问题 Why the web-version of Gmail line-wrap its mail content without marking the breaking place with a = , which make email processing very difficult: See the original mail content sent by gmail: and this mail sent by Mac OS X Mail: Edited: As Brandon Invergo said, they are using different encoding method. I am sorry that I said GMail is not decent. Edited 2: Their original content are: They are wrapped in Gmail, I guess it is according to word-wrap algorithm. 回答1: So, there are two separate