[INN] #124: Configuration parsing and documentation of innfeed.conf
INN
rra at stanford.edu
Sat Jan 17 09:09:11 UTC 2009
#124: Configuration parsing and documentation of innfeed.conf
---------------------+------------------------------------------------------
Reporter: iulius | Owner: eagle
Type: defect | Status: new
Priority: low | Milestone: 2.6.0
Component: innfeed | Version:
Severity: normal | Keywords:
---------------------+------------------------------------------------------
We should proof-read all the variables parsed in innfeed.conf, fix
possible errors and update the man page (converting it into POD).
In an [https://lists.isc.org/pipermail/inn-bugs/2005-March/004558.html
inn-bugs posting], Jeffrey T. Eaton reports that imapfeed has a bug in its
configuration parsing:
If I configure my feed as
{{{
group cyrus {
deliver-rcpt-to: bb+%s
peer cyrus.andrew.cmu.edu {
ip-name: cyrus.andrew.cmu.edu
}
}
}}}
or as:
{{{
group cyrus {
peer cyrus.andrew.cmu.edu {
deliver-rcpt-to: bb+%s
ip-name: cyrus.andrew.cmu.edu
}
}
}}}
then the deliver-rcpt-to setting is ignored. If I move it outside of
the group block, then it is honored. IE, this works:
{{{
deliver-rcpt-to: bb+%s
group cyrus {
peer cyrus.andrew.cmu.edu {
ip-name: cyrus.andrew.cmu.edu
}
}
}}}
--
Ticket URL: <http://inn.eyrie.org/trac/ticket/124>
INN <http://www.eyrie.org/~eagle/software/inn/>
InterNetNews
More information about the inn-bugs
mailing list