The Pickup & Delivery app allows merchants to enter a custom sender email address, such as: hello@examplebrand.com However, notification emails are still sent through Appstle’s mail servers. Email providers may then display the message as: hello@examplebrand.com via app.pickup-delivery.appstle.com and warn recipients that the sender cannot be verified. This can reduce customer trust and may cause important pickup and delivery notifications to be filtered into spam. Requested enhancement Please add support for authenticating merchant domains used for Pickup & Delivery notification emails. Possible options could include: * Custom sending-domain verification * DKIM authentication * SPF authorization * DNS verification records * A verified sender-domain configuration Current behavior From: hello@examplebrand.com via: app.pickup-delivery.appstle.com mailed-by: app.pickup-delivery.appstle.com signed-by: app.pickup-delivery.appstle.com Desired behavior From: hello@examplebrand.com mailed-by: examplebrand.com signed-by: examplebrand.com Alternatively, any standards-compliant configuration that allows Appstle to send authenticated messages on behalf of the merchant’s domain without triggering sender-verification warnings. Why this matters Custom-domain authentication would: * Improve transactional email deliverability * Reduce spam placement * Remove sender-verification warnings * Increase customer confidence * Help merchants reliably deliver time-sensitive pickup and delivery updates Is custom sending-domain authentication currently unsupported, or is there an existing SPF/DKIM setup process that is not yet documented in the app?
