The setup is warning you that it can't find a connector that is setup for a wildcard SMTP address. Looking at your current Exchange 2003 setup, do you have an SMTP connector? If so, what address-space is assigned to it? A stock SMTP connector would have an address space of "*" assigned.
It may be that you're running w/o an SMTP connector and just using the stock behaviour of the "Default SMTP Virtual Server" to deliver mail to the Internet. If you're just a single-server Exchange 2003 environment that may be the case. If it is, I'd continue with the Exchange 2007 installation and immediately create an SMTP send connector after the install completes. See: http://technet.microsoft.com/en-us/library/aa997285.aspx
If the above applies (re: single Exchange 2003 server w/ no SMTP connector), be aware that you will have to "undo" any smart host settings that you might've applied directly to the Defualt SMTP Virtual Server. It's best if you try and return these settings to stock and place such settings on the new E2K7 SMTP send connector. (In a pure E2K3 environment, it's preferrable to create an SMTP connector and apply such settings there, but I've seen a lot of E2K3 single-server environments where settings were set directly on the Default SMTP Virtual Server. It normally comes back to bite people when they add a 2nd Exchange Server computer or when they upgrade to E2K7.)
By creating an SMTP Send Connector on the E2K7 side after the install completes, email bound to the Internet from the E2K3 server will deliver to the E2K7 server first, then be relayed to the Internet. Email sourcing on the E2K7 side bound for the Internet will deliver directly there. Be sure your firewall will let the E2K7 machine source connections to the Internet, TCP ort 25. (Your firewall should be configured to drop outgoing TCP connections to port 25 EXCEPT from authorized mail servers.)
As you move mailboxes off of the E2K3 machine and retire it, Internet mail flow will continue. It doesn't matter, initially, if your inbound mail continues to come to the E2K3 machine, but you'll want to change that over to the E2K7 machine as you get closer to retirement of the E2K3 machine.
Be sure to work thru the retirement procedures from Microsoft, and you'll have no problems. There's some work in replicating off the public folder hierarchy and getting all of the E2K3 infrastructure cleaned up, but it's quite feasible to end up with a clean and properly functional infrastructure when all is said and done. (I've done several mid-sized E2K3 to E2K7 migrations, and they go fine so long as you move methodically and with care.)