Emails from Airbnb don't have proper reply to capability.

[Bob-And-Meg0]

We recently changed our Email address in our Airbnb account and we are now [only] receiving email reservation requests sent from Airbnb to this address and our text phone number. Our problem is we can't reply to accept reservations anymore through our email requests. When we hit the reply button, it goes to "express@airbnb" which doesn't accept emails. We can reply through our phone. We somehow lost our ability to reply through email as it does not have the guest's Airbnb temporary email address which is "their name, a long string of letters and numbers, followed by @reply.airbnb.com". This used to automatically happen when we hit "reply" to an email reservation request.

[Steve143]

Hello @Bob-And-Meg0,

I'm not sure how it used to be as I started being a host just last October.

When you get email notifications of a booking request there's now a "Confirm/Deny" button in the text of the email. You should click on that rather than using the email "Reply to" button.

As you rightly note, doing that will just send the reply to express@airbnb.com

Steve.

[Ian131]

Having the same problem.  I want to send a .pdf document to a guest with information about the apartment - I can't do this through the site but in the past was able to do this via email.  Now "reply to" just results in an error.  Doesn't create a great impression to guests when initial communications comprise little more than "just sent you an email with a doc", "hasn't arrived", "I've tried again", "no still nothing", "now", "no"..........

[Ian131]

@Bob-And-Meg0 - this has driven me mad this morning.  I tried replying to a guest using email (on Windows 10 device) and I kept getting the same error as you.  My email account is with gmail - so I have just tried logging onto Gmail through my web browser and that seemed to work fine.  The message was sent (and now appears in the conversation history on the AirBNB site) and hopefully my guest will also have received the file that was attached.  I don't know whether that will help in your specific scenario - but maybe it is an issue with compatability with your email package?  I can only suggest trying a few different options like I did and see if that helps get around the problem.