when an expected email is missing, requesting it again is an easy first reaction. first, check that the address can receive and that you’re looking in the right place. it can save you from collecting several old verification codes at once.

this checklist covers receiving. if you can read mail but can’t send, begin with plus status and your smtp settings.

check the full destination.

your main vael address ends in @vael.email. aliases end in @vael.pw. vaelmail.com is the website, rather than the domain for your main email address.

compare the full address in the sender’s account settings or confirmation page with the address shown in vael. look for a typo, an old alias, or the wrong domain. a similar-looking address is still a different destination.

for password resets, keep using the address currently saved with that outside service until you have completed its email-change process. changing your mind about which alias to use does not update their records.

look beyond the inbox.

check spam, trash, archive and any folders or filters you’ve set up. search for the sender or service name as well as the subject you expect. a filter may have moved a message after it arrived.

if you use a mail app, check webmail too. that helps separate a receiving problem from a synchronization or folder-view problem in the app. imap actions can also move or delete mail across devices.

make sure the address is enabled.

open aliases if the message is going to an alias. receiving must still be enabled. a paused alias does not accept password resets or security notices either.

if you removed the alias, don’t assume it can be recreated or still belongs to you. our alias guide explains why you should update important outside accounts before releasing an address.

check storage and plan changes.

a full mailbox can prevent new mail from being accepted. check storage and remove mail you no longer need, or choose the allowance that fits what you keep. export anything important before deleting it.

if plus recently ended, check your paid-through date and the grace period. free limits eventually apply again. an oversized mailbox must be reduced or renewed before additional mail can be accepted.

if you use your own domain.

check domains. the domain needs valid verification and mx records, plus the exact recipient address you want to use. vael domains have no catch-all, so an unlisted address is rejected.

dns changes can take time to appear through cached resolvers. the custom-domain guide shows which records to check and why the verification record should stay in place.

ask for the useful details.

if the sender received a delivery error, ask for its error text and approximate sending time. don’t ask them to send you their password or a live verification code. delivery errors can distinguish a wrong address, a full mailbox and a temporary failure.

after fixing the destination, request a fresh verification message and follow that service’s rules about which code remains valid. if the problem continues, contact support with the destination, approximate time and error details you’re comfortable sharing. never include your account number, app password or recovery codes.