Bug 3124 - Redirect UI action MUST violate best practices of mailexchange
Summary: Redirect UI action MUST violate best practices of mailexchange
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: SMTP (show other bugs)
Version: 3.9.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2014-03-26 16:02 UTC by bes
Modified: 2014-03-27 09:45 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description bes 2014-03-26 16:02:33 UTC 
When I shoose Redirect action for message (where body mail from is <incoming@domain.tld>) mail send as below:

[17:43:39] SMTP< 220 xxxxx, ESMTP EXIM
[17:43:39] ESMTP> EHLO support
[17:43:39] ESMTP< 250-xxx Hello support [192.168.99.128]
[17:43:39] ESMTP< 250-SIZE 268435456
[17:43:39] ESMTP< 250-8BITMIME
[17:43:39] ESMTP< 250-PIPELINING
[17:43:39] ESMTP< 250-AUTH PLAIN LOGIN CRAM-MD5
[17:43:39] ESMTP< 250 HELP
[17:43:39] ESMTP> AUTH CRAM-MD5
[17:43:39] ESMTP< 334 zzzz
[17:43:39] ESMTP> yyyyyy
[17:43:39] ESMTP< 235 Authentication succeeded
[17:43:39] ESMTP> MAIL FROM:<incoming@domain.tld> SIZE=9162

But must use my account address for this. I have no right to create a letter on behalf of another server. 

Сorrect action for Redirect
1. get body of selected message (STMP context, all data with headers) and wrap it in my envelope
2. that means use in SMTP MAIL FROM my account email
Comment 1 Paul 2014-03-26 16:23:26 UTC 
Please consult RFC 2822 for 'Resent fields'.
Comment 2 bes 2014-03-26 19:54:50 UTC 
No. Forget what I said about the text messages. Problem in SMTP MAIL FROM. It can not belong to an old envelope. Need to use the address that sent a new letter(forward). Address of account. 
Unfortunately I was not able to quickly find the section in RFC about this.
Comment 3 bes 2014-03-26 21:46:12 UTC 
I found RFC says about it. Please see RFC 5598 at section 5.2 "ReSender" (http://tools.ietf.org/html/rfc5598). Pay attention to RFC5321.MailFrom

Please explain why you are closing this bug as invalid?
Comment 4 Paul 2014-03-27 09:45:33 UTC 
(In reply to comment #3)
> I found RFC says about it. Please see RFC 5598 at section 5.2 "ReSender"
> (http://tools.ietf.org/html/rfc5598). Pay attention to RFC5321.MailFrom
> 
> Please explain why you are closing this bug as invalid?

RFC 5598 is an "Informational" RFC.
RFC 2822 is a "PROPOSED STANDARD" RFC.
RFC 5321 is a "DRAFT STANDARD" RFC.

Please see RFC 2026 for the meaning of these labels and then ask yourself why I keep marking this as INVALID.
Note You need to log in before you can comment on or make changes to this bug.