From: not handled correctly
Brought to you by:
chrissamuel
Menu
▾
▴
#10 From: not handled correctly
as requested: I try to enter a report in the bug section,
but for me it's addon for who doesn't respect RFC.
Hi,
I use vacation 1.2.7.0 beta4 on SuSE 10.1 with dovecot 1.0.beta3-13.9 (same problem with: postfix 2.2.9-10 )
Some address use From: field with about 80 characters + mail address,
structure are visible with less command like that:
From: "12345678901234567890123456789012345678901234567890123456789012345678901234567890" <= around 80 characters, but not fixed, can be 76 !
<email@address.com>
vacation only see "xxxx-around-eighty-characters-xxx", and thus: reply finish with an "unknown user" with local domain name
Same problem with vacation 1.2.6.3
Another point is (in 1.2.6.3):
vacation -l user
give "Segmentation Fault" and other "*** glibc detected *** vacation: free(): invalid pointer: 0x080b5ec8 ***"
In vacation 1.2.7.0 beta4: vaclook (which replace vacation -l user) doesn't have this SegFault problem
Using hexedit I see: 1234567890"..<email@address.com> , the 2 dot file in between are in hex: 0A 09
Looking at RFC 2822, From: field should respect:
"From:" mailbox-list CRLF
Thus it's not a bug in vacation, just as always: "not RFC respect" :(
Someone can adapt vacation to take care of some stupid to put CarrierReturn in From: field ?
Any idea are welcome,
Laurent.
Logged In: YES
user_id=1581966
Originator: NO
Yup, these are known bugs and I'm working in trunk to try and fix this (not committed yet).
Will be fixed in 1.3 as it's a fairly major piece of work.
Logged In: YES
user_id=1743914
Originator: YES
Hi Chissamuel,
Can you point me the line and the variable used to sent autoreply ?
My problem concern less than 20 mails address,
I can hardcoded something like:
switch (variable) {
case bad_address_1:
replace_bad_adress_1_with_good_address_1;
break;
case bad_address_2:
replace_bad_adress_2_with_good_address_2;
break;
}
It's not elegant but for me it's a solution.
Thank you for your help,
Laurent.
Logged In: YES
user_id=1581966
Originator: NO
You'll be wanting to look at the readheaders() function, best of luck!
A workaround for this problem is prepending `formail -c` to the vacation invocation:
"| /usr/bin/formail -c | vacation <user>"
Could you check for me with 1.2.8.0 beta 1 please?
There was code introduced to deal with wrapped headers but I'm not sure if it'll fix your issue.
Thanks!
Hello,
I will not able to help cause this server finish his life
and I never face this problem with a different mail system.
Good day.