Comments on: HoF Hates Base-64 https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/ Thoughts, rants, and even some code from the mind of Barney Boisvert. Thu, 11 Sep 2014 09:58:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Rob Brewer https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-262 Rob Brewer Thu, 02 Feb 2006 19:53:30 +0000 http://barneyb.com/barneyblog/?p=127#comment-262 I'm having similar problems with gmail and another mailing list. My messages to the list were silently discarded (perhaps by the moderator) and I now believe it was due to gmail base64 encoding my message for no reason. For now I turned off utf-8, but I filed a bug report with gmail. I'm having similar problems with gmail and
another mailing list. My messages
to the list were silently discarded (perhaps
by the moderator) and I now believe
it was due to gmail base64 encoding my
message for no reason. For now I turned
off utf-8, but I filed a bug report with
gmail.

]]> By: Barney https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-261 Barney Mon, 14 Nov 2005 17:37:00 +0000 http://barneyb.com/barneyblog/?p=127#comment-261 Alex, the problem wasn't with GMail not filtering base-64 message, but the mailing list software used by both House of Fusion and CFC-dev. Neither relayed base-64 encoded messages properly. The unknown was why GMail was _sending_ base-64 messages rather than quoted-printable. I have no idea about GMail's spam filters, other than that they do a good job filtering out the vast percentage of spam. Alex, the problem wasn't with GMail not filtering base-64 message, but the mailing list software used by both House of Fusion and CFC-dev. Neither relayed base-64 encoded messages properly. The unknown was why GMail was _sending_ base-64 messages rather than quoted-printable.

I have no idea about GMail's spam filters, other than that they do a good job filtering out the vast percentage of spam.

]]> By: Alex Spurling https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-260 Alex Spurling Mon, 14 Nov 2005 13:11:28 +0000 http://barneyb.com/barneyblog/?p=127#comment-260 GMail doesn't seem to block messages encoded in base64 for me. In fact almost all the spam that gets through the filter is encoded in this way. For some reason Google haven't figured out that all they need to do to filter this spam is decode the message, read the message, then throw it in the spam box. There's no reason that spam should be unfiltered or normal mail be blocked just because it is encoded in base64. Anyone know when Google are going to sort this out? GMail doesn't seem to block messages encoded in base64 for me. In fact almost all the spam that gets through the filter is encoded in this way. For some reason Google haven't figured out that all they need to do to filter this spam is decode the message, read the message, then throw it in the spam box. There's no reason that spam should be unfiltered or normal mail be blocked just because it is encoded in base64.

Anyone know when Google are going to sort this out?

]]> By: Michael Dinowitz https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-259 Michael Dinowitz Wed, 19 Oct 2005 21:53:13 +0000 http://barneyb.com/barneyblog/?p=127#comment-259 Sorry. There was a ton of base64 spam in the past (and present for that matter) and messages in that format are blocked. I'll look over the code to see if I should remove the restriction. Sorry. There was a ton of base64 spam in the past (and present for that matter) and messages in that format are blocked. I'll look over the code to see if I should remove the restriction.

]]> By: Barney https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-258 Barney Wed, 19 Oct 2005 16:26:13 +0000 http://barneyb.com/barneyblog/?p=127#comment-258 Bob, you're a genius. For whatever reason switching from UTF-8 back to 'default' also sets the content transfer encoding back to quoted-printable, rather than base-64. It certainly appears to be problem solved. Bob, you're a genius. For whatever reason switching from UTF-8 back to 'default' also sets the content transfer encoding back to quoted-printable, rather than base-64. It certainly appears to be problem solved.

]]> By: bob https://www.barneyb.com/barneyblog/2005/10/19/hof-hates-base-64/comment-page-1/#comment-257 bob Wed, 19 Oct 2005 16:21:53 +0000 http://barneyb.com/barneyblog/?p=127#comment-257 have you tried changing the default outgoing message encoding from "default" to UTF-8 to see if that helps? have you tried changing the default outgoing message encoding from "default" to UTF-8 to see if that helps?

]]>