I don’t understand why not more people are raising these concerns.
How did you pick who you are sending to? You could have had them send you ADA first.
I feel compelled to respond to the idea about 1 ADA being used to fight token spam. That is what the transaction fee is for, and last time I checked, it’s not zero. This locked ADA stuff some committee invented is just an amateur’s solution to a perceived problem, whatever problem they perceived. I can understand it growing with size, but this is some ridiculous Austrian economics or something.
I’m bumping this thread. I need to send my token to 10,000 addresses. How can I reduce costs?
Usual solution is to not just spam a token to 10 000 accounts, but either use DripDropz or TosiDrop or build a similar solution yourself, where people send the minimum ADA (or a little more) upfront and receive it back together with the token.
You can also build a small dApp, where they do not even have to trust you, but the dApp can take a UTxO from their account and immediately send it back with the token (minus the transaction fee maybe) in the very same transaction.
I’m not a spammer. I have my token (Token GND - Cardanoscan) and community.
I want to distribute tokens to all members of my community. My community members don’t have cryptocurrency wallets and ADA, so they can’t send ADA to me.
But thanks I’ll check out DripDropz and TosiDrop.
If they don’t have Cardano wallets and ADA, it will be impossible to send them a token that (only) exists on the Cardano chain. Makes little sense.
DripDropz, TosiDrop, a self-made solution with or without dApp, … all require to have a Cardano wallet.
Even without those and without the minimum UTxO costs: To what addresses would you want to send if they are not on Cardano?
It’s not like that. I am a Java developer and created a script generating 10,000 addresses in the Cardano blockchain. Ultimately, I want to distribute addresses with a native token but the fees are too expensive for me.
What do you mean by “generating 10,000 addresses”?
An address is the hash of a public key. In order for your users to be able to do something with it, you’d have to give them the private key for it.
And since no (more or less) user-friendly wallet app can deal with plain key pairs, you will probably want to generate seed phrase wallets for them.
But in both cases, you (or your script or your distribution system) will know the private key or the seed phrase. So, it would not be recommended for them to use that, anyway.
And you just can’t gift addresses or wallets without minimal ADA in them. So, your plan basically is not possible on Cardano.
So Cardano native tokens is not for me and it is not for many content creators who are building a community with their own tokens. Thank you. 
If your use case is a token to be used exclusively inside your community: Just manage it in your user system without any blockchain technology at all. Each user account gets a number of tokens and you track transactions between user accounts and new balances. Without blockchain, that’s almost trivial.
If you want to use a public blockchain for respectability or to allow your users to trade and transfer outside of your system (if that makes even sense), then they will inevitably need to have wallets and wallet apps for the blockchain you choose. Just sending tokens to randomly generated addresses is a bad idea on all blockchains. They can never be moved away from them again.
On another blockchain, there will perhaps not be the minimal ADA requirements of Cardano native tokens, but for example on Ethereum you and your users will have to pay quite high gas fees to move the tokens around. Cf. for example: https://ethereum.stackexchange.com/q/119829
What you could do as a middle ground is managing the tokens in your usual user system, but give the option to withdraw them to and deposit from a public blockchain.
In both cases – completely on-chain or hybrid – I would first do a survey among your users, which chains they maybe already use, already have wallet apps for, want to use for this, if they even want to use a blockchain for this at all.
I agree with @HeptaSean going with an internal solution and allow the user to withdraw to a blockchain wallet. You could support multiple blockchains with converters etc (in case it’s worth the req. work).
Having the token sit in a wallet that you created and have given access to to the user would be eventually the same as managing the token centrally and allowing for withdrawal, as the user cannot trust your wallet and will have to move the token anyway… and it’s more expensive to do.