Bug #15551, was updated on 2009-Apr-23 14:30
Here is a current snapshot of the bug.
Project: Community Fetchmail
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: arunvasan
Assigned to : none
Summary: Fetmail envelope option - Reg
Details: Hi and Hello to all,
I have one clsrification in the Fetchmail.
My Fetchmail version is 6.3.6
My .fetchmailrc file is as follows
set logfile '/var/log/fetchmail.log'
set invisible
set bouncemail
set showdots
poll mail.mydomain.com
protocol pop3
no dns
envelope Delivered-To
qvirtual 'mailindx-mydomain:com-'
localdomains mydomain.com
user test
password test
is * here
smtphost intranet.mydomain.com
no rewrite
flush
fetchall
All our mail users mail will be received at mail.mydomain.com with in a comman user id having their original email id in Delivered-To header. (Mutidrop)
This is Delivered-To header will be as a second header to my email.
In the fetchmail man pages I came to know that
-E <line> | --envelope <line>
(Keyword: envelope; Multidrop only)
In the configuration file, an enhanced syntax is used:
envelope [<count>] <line>
This option changes the header fetchmail assumes will carry a copy of the mail's envelope address. Normally this is 'X-Envelope-To', but as this
header is not standard, practice varies. See the discussion of multidrop address handling below. As a special case, 'envelope "Received"' enables
parsing of sendmail-style Received lines. This is the default, and it should not be necessary unless you have globally disabled Received parsing
with 'no envelope' in the .fetchmailrc file.
The optional count argument (only available in the configuration file) determines how many header lines of this kind are skipped. A count of 1
means: skip the first, take the second. A count of 2 means: skip the first and second, take the third, and so on.
But if I give the option in the .fetchmailrc as follows
envelope [1] Deivered-To
it throws an error as follows,
fetchmail:/root/.fetchmailrc:9: syntax error at Delivered-To
Can any one Help me to rectify this error ?
Thanks in advance.
Regards,
Arun
For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=15551&group_id=1824
|
