Change in How "Reply-To" Works (Yahoo Only?)
Posted: Thu Aug 29, 2019 9:59 am
One nice feature of Pop Peeper is how the "Reply-To" feature has worked for outgoing messages. I could put anything I want in that field and if a recipient clicked the "Reply" option to an email I sent, that address would be the address used for the reply. Of course if I wanted to actually receive the reply, the address would have to be legit, which it was, since I own the domain used. For example, let's say I own the domain mydomain.com: I would have the email address of electricity@mydomain.com for my electric bill, amazon@mydomain.com for my amazon account, etc. Even if these addresses weren't set up with my Yahoo email account as valid outgoing email addresses, I would still receive emails sent to those addresses, since I had a 'catch-all' option set up for all incoming emails to that domain. This was useful because I could automatically categorize incoming emails based upon the Reply-To address.
However, yesterday I tried creating a new "Reply-To" address within an outgoing email (from Pop Peeper) using my AT&T/Yahoo account, and for some reason, that address is now being checked by Yahoo to see if it's a valid outgoing (what Yahoo calls a "send-only") address. And because I haven't set up that address, sending that email fails with this error message:
I don't know if this new behavior is because of something different within Pop Peeper, a change to how Yahoo looks at the Reply-To field, or both, but I'm wondering if there is a way for Pop Peeper to reinstate the 'anything goes' functionality of the Reply-To field?
I would add the new address to my list of send-only addresses within Yahoo, but there are two problems with that approach:
NOTE: I'm running Pop Peeper Pro v4.5.2 with Webmail v4.5.11.0 and SSL v1.0.2.16. All other modules show the same version for both "Current" and "Latest".
However, yesterday I tried creating a new "Reply-To" address within an outgoing email (from Pop Peeper) using my AT&T/Yahoo account, and for some reason, that address is now being checked by Yahoo to see if it's a valid outgoing (what Yahoo calls a "send-only") address. And because I haven't set up that address, sending that email fails with this error message:
I don't know if this new behavior is because of something different within Pop Peeper, a change to how Yahoo looks at the Reply-To field, or both, but I'm wondering if there is a way for Pop Peeper to reinstate the 'anything goes' functionality of the Reply-To field?
I would add the new address to my list of send-only addresses within Yahoo, but there are two problems with that approach:
- Yahoo only allows a maximum of 10 send-only addresses.
- Currently, I'm not able to add any additional send-only addresses to my Yahoo account (there is a failure with Yahoo sending the verification email), even though I have less than 10 (this problem may be related to the error I'm receiving when trying to use a 'temporary' Reply-To address).
NOTE: I'm running Pop Peeper Pro v4.5.2 with Webmail v4.5.11.0 and SSL v1.0.2.16. All other modules show the same version for both "Current" and "Latest".