[Question] Mdaemon không thể nhận Mail BCC |
20/03/2007 00:17:44 (+0700) | #1 | 47839 |
lama
Member
|
0 |
|
|
Joined: 14/06/2004 20:27:02
Messages: 40
Offline
|
|
Hi,
Mình sử dụng Mdaemon v8.0.3. Đang gặp vấn đề là user không nhận được mail nếu họ trong danh sách BCC list.
Mình tìm được thông tin sau trên MDaemon
BCC Headers in MDaemon
KBA-01291
Summary
--------------------------------------------------------------------------------
BCC by definition is blind. The header should never be created by a mail client because the message should not display that it was sent to anyone in the BCC field. Here's what the headers look like when composing a message with a BCC:
Received: from robin ([127.0.0.1]) by test.mail ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.0.5.R); Tue, 20 Aug 2002 10:09:15 -0400
Reply-To: 'Robin' <test@company.mail>
From: 'Robin' <test@company.mail>
To: <yep@company.mail>
Subject: test
There is no BCC info in the message even before it goes out to the Internet for delivery. (I BCCed robin@isp.com.)
The way that BCC mail is routed is via the SMTP envelope information. Mail servers pass the message along via SMTP and the delivery information is kept in tact.
When you download the message via DomainPOP, MDaemon does not have the SMTP delivery information any longer. It has to make the best guess as to where the message should go.
Some ISPs stamp a header so that the SMTP delivery information is available for parsing, but it's not required. These headers may be “Envelope-To” or “Delivered-To” or something similar. Your ISP may be able to do something along these lines. Alternatively you could ask them if you could receive mail via ATRN instead of POP because then the SMTP envelope is still there.
Như vậy, để nhận được mail, mình phải nhờ bên Hosting Mail Server chèn thông tin vô Header ? ATRN thì mình không rành.
Trường hợp này theo mình cũng thường gặp lắm, bạn nào giải quyết rồi xin chia sẻ.
Cám ơn nhiều. |
|
|
|
|
|
|
|
Users currently in here |
1 Anonymous
|
|
Powered by JForum - Extended by HVAOnline
hvaonline.net | hvaforum.net | hvazone.net | hvanews.net | vnhacker.org
1999 - 2013 ©
v2012|0504|218|
|
|