Originally submitted by John Griffin on: Thu Jan 19 19:36:01 -0500 2012
stmp-send-message failed to connect on one gmail account while working fine for two others. The problem is around line 100 of smtp.rkt where a base64-encode does a line break at 72 characters on the one account which happens to be long enough to expose a symptom (authentication failure). The two functioning email accounts happen to be shorter strings. Whether using a regex-replace* is better than using (base64-encode-stream in out #"") seemed a toss up. My fix is below for someone to review.
Originally submitted by John Griffin on: Thu Jan 19 19:36:01 -0500 2012
stmp-send-message failed to connect on one gmail account while working fine for two others. The problem is around line 100 of smtp.rkt where a base64-encode does a line break at 72 characters on the one account which happens to be long enough to expose a symptom (authentication failure). The two functioning email accounts happen to be shorter strings. Whether using a regex-replace* is better than using (base64-encode-stream in out #"") seemed a toss up. My fix is below for someone to review.
(when auth-user (log "auth\n") (fprintf w "AUTH PLAIN ~a\r\n" ;; Encoding adds CRLF
(regexp-replace*
rx"\r\n"
Steps to Reproduce:
Release:
Environment:
This bug was converted from Gnats bug 12501.
[anon-submit; griffinish at gmail dot com]