Just for the record, to close this off - the problem was solved when I
finally configured Django to send email via my *ISP*. Apparently
Django was doing some unnecessary formatting, whether the output went
to file, console, or even *smtp*, going to a local smtp server: python
-m smtpd -n -c
> Actually, it doesn't. It only has utf-8. The first nine lines of your pasted
output are the actual email headers.
Okay, that makes more sense. That particular experiment I was using a
MIMEObject's to_string() function. Although I had passed in plain text
to the object, clearly it put its own
> What are you *actually* doing to send this email?
This is the basic version - the one with two headers, I was
experimenting with a MIMEText object:
from django.core.mail import send_mail
def page_worked(request):
the_text = u'this is a test of a really long line that has more
words that
On Tue, May 17, 2011 at 1:02 PM, John Crawford wrote:
> Actually, upon looking more at the output, it has *both* "utf-8" and
> "us-ascii" as the charset.
Actually, it doesn't. It only has utf-8. The first nine lines of your pasted
output are the actual email headers.
Actually, upon looking more at the output, it has *both* "utf-8" and
"us-ascii" as the charset. I'm not sure if this is the result of code
changes I've made, or I just missed it the first time around - but my
Django email output now looks like this:
-- MESSAGE FOLLOWS --
> The only encoding that isn;t going to wrap is charset="us-ascii"
Actually, looking at the resulting file, it *does* say it's
charset="us-ascii".
> An email client would read "=\r\n" as a soft line break, and remove it
> when displaying the message.
I tried cutting/pasting the text, and
On Fri, May 6, 2011 at 5:33 AM, Jason Culverhouse wrote:
>
>
> The answer is no, it it the underlying python email.MIMEText object that is
> performing the encoding
> The only encoding that isn;t going to wrap is charset="us-ascii"
>
>
On May 5, 2011, at 5:50 PM, John Crawford wrote:
> I'm using the filebased email backend for testing (although the console
> version had the same problem). When I send email, either via function or
> template, lines that are too long, are broken, with an '=' sign at the end.
> For instance:
>
I'm using the filebased email backend for testing (although the
console version had the same problem). When I send email, either via
function or template, lines that are too long, are broken, with an
'=' sign at the end. For instance:
this is a test of a really long line that has more words
9 matches
Mail list logo