On 2025-03-18, Yves Goergen via Exim-users <exim-users@lists.exim.org> wrote: > Hello, > > I'm upgrading Exim from 4.93 to 4.97 soon and read an entry in the > upgrading documentation [1]. It says I cannot use $local_part in > transports anymore and should consider $local_part_data.
For some purposes you cannot use $local_part, what are you using it for? > Unfortunately, I'm not an Exim expert so I don't know what consequences > that will have. A web search hasn't brought up any information on this. > I'm using $local_part in transports, routers and ACLs, it's basically > everywhere. I mean, it's the most essential data to identify a mailbox. > > What should I do now? Can I simply replace that variable everywhere? You can use it as the key in a lookup and use the result to identify the mailbox file. $local_part_data is an exmple of that, but explicit lookups are allowed too. > It's also part of SQL queries in macros which are called from different > parts of the config file. If I need to use different variables in > different contexts now, I'd have to duplicate those SQL queries to use > different variables. Assuming it's being quoted properly the SQL queries can most likely remain as-is but if you're using "servers=" that part may need to be rearranged. -- Jasen. 🇺🇦 Слава Україні -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
