Struct mailslurp::models::create_inbox_dto::CreateInboxDto [−][src]
pub struct CreateInboxDto { pub allow_team_access: Option<bool>, pub description: Option<String>, pub email_address: Option<String>, pub expires_at: Option<String>, pub expires_in: Option<i64>, pub favourite: Option<bool>, pub inbox_type: Option<InboxType>, pub name: Option<String>, pub tags: Option<Vec<String>>, pub use_domain_pool: Option<bool>, }
Expand description
CreateInboxDto : Options for creating an inbox. An inbox has a real email address that can send and receive emails. Inboxes can be permanent or expire at a given time. Inboxes are either SMTP
or HTTP
mailboxes. Use SMTP
for public facing mailboxes and HTTP
for test email accounts. SMTP
inboxes are processed by a mail server running at mx.mailslurp.com
while HTTP
inboxes are processed by AWS SES. Inboxes can use a custom email address (by verifying your own domain) or a randomly assigned email ending in either mailslurp.com
or (if useDomainPool
is enabled) ending in a similar domain such as mailslurp.xyz
(selected at random).
Fields
allow_team_access: Option<bool>
Grant team access to this inbox and the emails that belong to it for team members of your organization.
description: Option<String>
Optional description of the inbox for labelling purposes. Is shown in the dashboard and can be used with
email_address: Option<String>
A custom email address to use with the inbox. Defaults to null. When null MailSlurp will assign a random email address to the inbox such as 123@mailslurp.com
. If you use the useDomainPool
option when the email address is null it will generate an email address with a more varied domain ending such as 123@mailslurp.info
or 123@mailslurp.biz
. When a custom email address is provided the address is split into a domain and the domain is queried against your user. If you have created the domain in the MailSlurp dashboard and verified it you can use any email address that ends with the domain. Note domain types must match the inbox type - so SMTP
inboxes will only work with SMTP
type domains. Send an email to this address and the inbox will receive and store it for you. To retrieve the email use the Inbox and Email Controller endpoints with the inbox ID.
expires_at: Option<String>
Optional inbox expiration date. If null then this inbox is permanent and the emails in it won’t be deleted. If an expiration date is provided or is required by your plan the inbox will be closed when the expiration time is reached. Expired inboxes still contain their emails but can no longer send or receive emails. An ExpiredInboxRecord is created when an inbox and the email address and inbox ID are recorded. The expiresAt property is a timestamp string in ISO DateTime Format yyyy-MM-dd’T’HH:mm:ss.SSSXXX.
expires_in: Option<i64>
Number of milliseconds that inbox should exist for
favourite: Option<bool>
Is the inbox a favorite. Marking an inbox as a favorite is typically done in the dashboard for quick access or filtering
inbox_type: Option<InboxType>
HTTP (default) or SMTP inbox type. HTTP inboxes are best for testing while SMTP inboxes are more reliable for public inbound email consumption. When using custom domains the domain type must match the inbox type. HTTP inboxes are processed by AWS SES while SMTP inboxes use a custom mail server running at mx.mailslurp.com
.
name: Option<String>
Optional name of the inbox. Displayed in the dashboard for easier search and used as the sender name when sending emails.
Tags that inbox has been tagged with. Tags can be added to inboxes to group different inboxes within an account. You can also search for inboxes by tag in the dashboard UI.
use_domain_pool: Option<bool>
Use the MailSlurp domain name pool with this inbox when creating the email address. Defaults to null. If enabled the inbox will be an email address with a domain randomly chosen from a list of the MailSlurp domains. This is useful when the default @mailslurp.com
email addresses used with inboxes are blocked or considered spam by a provider or receiving service. When domain pool is enabled an email address will be generated ending in @mailslurp.{world,info,xyz,...}
. This means a TLD is randomly selecting from a list of .biz
, .info
, .xyz
etc to add variance to the generated email addresses. When null or false MailSlurp uses the default behavior of @mailslurp.com
or custom email address provided by the emailAddress field. Note this feature is only available for HTTP
inbox types.
Implementations
Options for creating an inbox. An inbox has a real email address that can send and receive emails. Inboxes can be permanent or expire at a given time. Inboxes are either SMTP
or HTTP
mailboxes. Use SMTP
for public facing mailboxes and HTTP
for test email accounts. SMTP
inboxes are processed by a mail server running at mx.mailslurp.com
while HTTP
inboxes are processed by AWS SES. Inboxes can use a custom email address (by verifying your own domain) or a randomly assigned email ending in either mailslurp.com
or (if useDomainPool
is enabled) ending in a similar domain such as mailslurp.xyz
(selected at random).
Trait Implementations
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
__D: Deserializer<'de>,
Deserialize this value from the given Serde deserializer. Read more
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for CreateInboxDto
impl Send for CreateInboxDto
impl Sync for CreateInboxDto
impl Unpin for CreateInboxDto
impl UnwindSafe for CreateInboxDto
Blanket Implementations
Mutably borrows from an owned value. Read more
Instruments this type with the provided Span
, returning an
Instrumented
wrapper. Read more