wildcard in incoming.conf

[Paul Theodoropoulos]

I've had a couple of requests over the last few weeks to an an entry in 
incoming.conf with * as the leading character, eg *.example.com. INN 
doesn't seem to like this. Is there any workaround? These are cases where 
the peer is making changes to host/server names, which aren't yet 
finalized. By using a wildcard it seems the hope is that they can continue 
feeding even as the hostname changes.
---------------------------------------------------------------------
Paul Theodoropoulos                        Advanced TelCom Group Inc.
Senior Unix Systems Administrator          Internet Services Division
paul at atgi.net                              Santa Rosa, California, US
Work: http://www.atgi.net             Play: http://www.anastrophe.com
"Reliability means never having to say you're sorry." -D.J. Bernstein