imapfeed bug with deliver-rcpt-to

[Russ Allbery]

Jeffrey T Eaton <jeaton at cmu.edu> writes:

> 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
>  }
> }

While this is not perhaps what's desired, it's not actually a bug.  See
the innconf man page:

GLOBAL PEER DEFAULTS
       All the key/value pairs mentioned in this section must be specified  at
       global scope. They may also be specified inside a group or peer defini-
       tion. Note that when peers are added  dynamically  (i.e.  when  innfeed
       receives an article for an unspecified peer), it will add the peer site
       using the parameters specified at global scope.

[...]

              deliver-rcpt-to
                     A printf-style format string for  creating  the  envelope
                     recipient  address.   The  pattern  MUST include a single
                     string specifier which will be replaced with the newgroup
                     (e.g "bb+%s").  The default is "+%s".

Does this cause problems for you?  Do you need to be able to configure
this differently depending on which host you're feeding?  If so, I can add
that to the to-do list, although I can't make any guarantees as to when
I'll be able to fix it.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>