MikeNolan is experiencing issues with AOL emails. Occasionally, emails from AOL users come from @aim.com instead of the usual @aol.com, causing them to be rejected due to non-matching email addresses. MikeNolan is looking for a way to force a secondary email address into a user record without the user having to confirm the email address.
Further investigation revealed differences in email headers between @aol.com and @aim.com emails, including the X-Mailer header. MikeNolan suspects that the user may be unknowingly generating the @aim.com domain.
Additionally, MikeNolan is experiencing issues with email replies being rejected with an Email::Receiver::ReplyUserNotMatchingError despite the email matching the primary email in the user profile.
AOL has come up with another odd email behavior that is causing problems for my users.
Most of the time, a post or response via email comes from AOL comes from XXX@aol.com. But I have seen occasions when it comes from XXX@aim.com. Of course these are rejected as non-matching email addresses.
The users, as far as I know, don’t have the ability to access email sent to XXX@aim.com, so there’s no easy way to set that up as a secondary email address by having them confirm that email address.
Is there a easy way to force a secondary email address into a user record without the user having to confirm the email address?
If I had a dollar for every strange email issue from AOL, I could have a nice steak dinner at least once a month.
Another common problem is posts via email that reject with this explanation:
Email::Receiver::ReplyUserNotMatchingError
It appears that the email matches the primary email for this user in his user profile, so it’s not clear to me why the reply via email was rejected.
This only happens a small percentage of the time, most of the time the replies from my users go through without any problems. Not sure what trips the reject.