Displaying 4 results from an estimated 4 matches for "delimiter_str".
2017 Aug 08
1
[master-2.2] 4118e86
...ress_parse? from incompatible pointer type [enabled
by default]
&detail);
^
In file included from quota-status.c:14:0:
../../../src/lib-mail/message-address.h:38:6: note: expected ?const
char **? but argument is of type ?char *?
void message_detail_address_parse(const char *delimiter_string,
^
quota-status.c:98:10: error: too many arguments to function
?message_detail_address_parse?
&detail);
^
In file included from quota-status.c:14:0:
../../../src/lib-mail/message-address.h:38:6: note: declared here
void message_detail_address_parse(const char *deli...
2017 Nov 01
2
Bug: lmtp proxy does not quote local parts with spaces
...var_expand(str, format, tab);
md5_get_digest(str_data(str), str_len(str), md5);
--- dovecot-2.2.33.2.original/src/lib-mail/message-address.c 2017-10-05 18:10:44.000000000 +0100
+++ dovecot-2.2.33.2/src/lib-mail/message-address.c 2017-10-31 10:12:50.185866755 +0000
@@ -540,7 +540,7 @@
if (*delimiter_string == '\0')
return;
- domain = strchr(address, '@');
+ domain = strrchr(address, '@');
p = strstr(address, delimiter_string);
if (p != NULL && (domain == NULL || p < domain)) {
/* user+detail at domain */
--- dovecot-2.2.33.2.original/src/lib-smtp/Make...
2017 Nov 03
1
Bug: lmtp proxy does not quote local parts with spaces
...expand(str, format, tab);
md5_get_digest(str_data(str), str_len(str), md5);
--- dovecot-2.2.33.2/src/lib-mail/message-address.c 2017-10-05 18:10:44.000000000 +0100
+++ dovecot-2.2.33.2.reverse-domaincut/src/lib-mail/message-address.c 2017-11-02 16:00:30.926866755 +0000
@@ -540,7 +540,7 @@
if (*delimiter_string == '\0')
return;
- domain = strchr(address, '@');
+ domain = strrchr(address, '@');
p = strstr(address, delimiter_string);
if (p != NULL && (domain == NULL || p < domain)) {
/* user+detail at domain */
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 18:38, Alexander Dalloz wrote:
> Am 26.10.2017 um 12:20 schrieb David Zambonini:
>>
>> There seems to be a bug with RFC822 processing in ltmp proxying that
>> doesn't
>> quote local parts that, for example, contain spaces.
>
> Newer related RFCs are RFC 5321 and 5322.
Typo, meant to say RFC2822, which they still supercede, not that the