Masked Addresses (Postscale Shield)

Postscale Shield lets you create unique masked email addresses for your users. These aliases forward to real email addresses while keeping user identities private.

Use Cases

• Marketplace platforms: Let buyers and sellers communicate without exposing emails
• Dating apps: Enable messaging before users share personal details
• Support systems: Create per-ticket email addresses
• Newsletter signups: Give users disposable addresses for each service

Creating an Alias

const alias = await postscale.shield.aliases.create({
  forward_to: ['user@example.com'],
  description: 'acme-newsletter'
});

// Returns: { alias: { address: 'xk7m9p', domain: 'shield.postscale.io', ... } }

Managing Aliases

List User Aliases

const aliases = await postscale.shield.aliases.list();

Disable an Alias

await postscale.shield.aliases.update('alias_id', {
  active: false
});

Delete an Alias

await postscale.shield.aliases.delete('alias_id');

Reply Handling

When an email is forwarded through a Shield alias, the Reply-To header is rewritten to a unique reply address (r-{token}@shield.postscale.io). When you reply:

1. The reply is received at the r-{token} address
2. The token is looked up to find the original sender and alias
3. The reply is sent from the masked alias address, DKIM-signed
4. The original sender receives the reply without seeing your real email

Reply tokens expire after 90 days.