2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier 20020921
FromSent OnAttachments
Sam VarshavchikSep 21, 2002 11:57 pm 
Huang YuzhenSep 23, 2002 12:42 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Courier 20020921Actions...
From:Huang Yuzhen (huan@bj.tom.com)
Date:Sep 23, 2002 12:42:40 am
List:net.sourceforge.lists.courier-users

Sam: I guess you make something wrong,if use your code,normal pop3 user could NOT
login again. I track with authmysql, it show SELECT id, crypt, "", uid, gid, home, "", quota, "" FROM passwd WHERE id = "abc
@qq.com.cn" , between "abc" and "@" there is a 'space', so I change "p=strtok(0,"\n")" to
"p=strtok(0,"\r\n")" . would you check it?

diff -rc src/courier-0.39.3.20020921/imap/pop3login.c
courier-20020921-hyz/imap/pop3login.c *** src/courier-0.39.3.20020921/imap/pop3login.c Sun Sep 15 08:28:06 2002 --- courier-20020921-hyz/imap/pop3login.c Mon Sep 23 14:15:20 2002 *************** *** 190,196 **** continue; }

! p=strtok(0, "\n"); if (p) { if (user) free(user); --- 190,196 ---- continue; }

! p=strtok(0, "\r\n"); if (p) { if (user) free(user); *************** *** 257,263 **** } } else if (strcmp(p, "PASS") == 0) { ! p=strtok(0, "\n");

if (!user || p == 0) { --- 257,263 ---- } } else if (strcmp(p, "PASS") == 0) { ! p=strtok(0, "\r\n");

if (!user || p == 0) {

Huang Yuzhen. 2002.09.23 Beijing,China

----- Original Message ----- From: "Sam Varshavchik" <mrs@courier-mta.com> To: <cour@lists.sourceforge.net>;
<cour@lists.sourceforge.net> Sent: Sunday, September 22, 2002 2:57 PM Subject: [courier-users] Courier 20020921

Download: http://www.courier-mta.org/download.php

This is an update that adds support for RFC 2231-based encoding of MIME attributes to the webmail server. This primarily modifies encoding of attachment filenames to include native filename character set and language. It's a relatively recent standard. Up until now sqwebmail used encoding based on RFC 2047, which is the encoding used for character sets in the subject, and addressing headers. But, it looks like that someone decided that it would be a good idea to use a completely different encoding mechanism for MIME attributes, such as attachment filenames, so there you go.

And, just to make things more interesting, the whole mess is not backwards-compatible. Meaning that -- for now -- mail clients that are not RFC 2231-aware will not be able to see the default attachment filenames from sqwebmail. I'll try to think of something to mitigate that to some degree; 20020921 is a trial baloon to evaluate how big of a mess this is going to be.

-- Sam

_______________________________________________ courier-users mailing list cour@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users