Manage inbound messages
An inbound message is an email delivered to an BridgeERP database. Anyone can send an email to an email alias created in the database or reply to an email that was previously sent from the database based on the reply-to header.
Email aliases
Model specific aliases
Some applications have their specific aliases (sales teams, helpdesk teams, projects, etc.). These aliases are used to:
Create a record when an email is sent directly to the alias,
Receive replies to an email initially sent from a record.
Example
In the example displayed above, sending an email to info@company-name.www.mybridgeerp.com will create a new opportunity or a new lead automatically assigned to the corresponding sales team. If an email is sent from the chatter of an existing opportunity, the reply-to will be info@company-name.www.mybridgeerp.com. The reply will be posted in the right chatter, according to the message-id header.
Catchall
If an application does not have an alias, a generic fallback alias is used: the catchall. An email sent from a chatter has a reply address set to this catchall alias. A reply sent to the catchall is posted to the right chatter thanks to the message-id header.
By default, the local-part catchall will be used. Enable developer-mode and go to to access the configuration.
An email to the catchall always needs to be a reply to a previous email sent from the database. If an email is sent directly to the catchall, the sender will receive the following message:
Note
The email address info@company-name.com displayed in the screenshot above is the email address set on the company. Upon entering the developer mode on a company profile, additional configuration options (such as catchall and bounce) become readable. It can be modified by clicking on the internal link of the Email Domain. It is generally not recommended to modify these options unless specific needs dictate, as it will affect all replies to previously sent emails.
Example
An alias can be configured on a sales team in the CRM app. When a customer replies to an email coming from the CRM app, the reply-to is info@company-name.www.mybridgeerp.com.
When an email is sent from the Contact app, the reply address is catchall@company-name.www.mybridgeerp.com because there is no alias on the contact model.
Note
It is advised to keep the local-part of the catchall and the bounce unchanged. If this value is modified, previous emails sent from the database will still have the previous local-part values. This could lead to replies not being correctly received in the database.
Bounce
In the same way the catchall alias is used to build the reply address, the bounce alias is used to build the return-path of the email. The return-path is used when emails cannot be delivered to the recipient and an error is returned to the sender.
By default the name bounce will be used. Enable developer-mode and go to to access the configuration.
Note
On BridgeERP Online, when using the default outgoing email server, the return-path address is forced to the value bounce@company-name.www.mybridgeerp.com independently of the value set as bounce alias.
When an error occurs, a notification is received and displayed in a red envelope in the chatter. In some cases, the red envelope can just contain a no error message, meaning there is an error that could not be handled by BridgeERP.
A notification will also be displayed in the Discuss icon on the navigation bar.
Example
If the email address of the recipient is incorrect, by clicking on the red envelope in the chatter an error message containing the reason for the failure will be given.
Receive emails with BridgeERP’s default configuration
On BridgeERP Online and BridgeERP Cloud, the email alias, reply, and bounce addresses are pre-configured. These addresses use the alias domain automatically added to a standard database.
Example
Assuming the database URL is https://mydatabase.www.mybridgeerp.com, the alias domain mydatabase.www.mybridgeerp.com is automatically created. Catchall and bounce can be used and their address is respectively catchall@mydatabase.www.mybridgeerp.com, and bounce@mydatabase.www.mybridgeerp.com.
If the CRM app is installed, and a sales team with the alias info is created, the info@mydatabase.www.mybridgeerp.com address can be used immediately. The same goes for any other alias created in other applications.
The database domain is ready to be used to receive emails without any additional configuration.
Use multiple BridgeERP subdomains
On BridgeERP Online, the only BridgeERP subdomain is the one defined at the database creation.
On BridgeERP Cloud, it is possible to use several BridgeERP subdomains. In the settings of the branch, additional BridgeERP subdomains can be added as long as they are not used yet in another branch. These domains must then be added to the alias domains to be used by a company.
Use a custom domain for inbound messages
The alias domain must be selected in the general settings. If you have multiple companies, each one must be configured.
All the aliases will use this custom domain. Replies on models for which an alias is configured are done to [alias]@my-custom-domain.com. Replies to other models are sent to the catchall through catchall@my-custom-domain.com.
Important
If emails are sent using BridgeERP’s email servers while using a custom domain, follow the “Using a custom domain with BridgeERP’s email server” instructions.
Since this custom domain is used, all emails using an alias (replies, bounces and direct sends) are sent to an address of the domain. They are thus delivered to the email server linked to the domain (MX record). To display them in the chatter or to create new records, it is necessary to retrieve these incoming emails in the BridgeERP database.
Method |
Benefits |
Drawbacks |
|---|---|---|
Easy to set up, emails are directly sent to the database. |
Each alias of a database needs to be configured. |
|
Allows to keep a copy of the email in your mailbox (with IMAP). Allows to create records in the chosen model. |
Depends on a CRON, meaning emails are not retrieved immediately in the database. Each alias of a database needs to be configured. |
|
Only one record needs to be created to make all aliases work properly. |
Using a subdomain is required. Requires advanced technical knowledge. |
Important
For on-premise databases, the redirection and the MX record methods also require configuring the mail gateway script. Going through this script requires advanced technical and infrastructure knowledge.
Important
Refer to your provider’s documentation for more detailed information on how to handle the methods detailed below.
Redirections
If the database is hosted on BridgeERP Online or BridgeERP Cloud, using redirections is recommended. They allow messages to be received without delay in the database.
Warning
When configuring email redirections with Microsoft 365 (Exchange Online), be aware that certain technical limitations may affect your setup. Some users have reported that Microsoft 365 does not support true redirection and only allows forwarding, which may not behave as needed for BridgeERP’s email routing.
For more information on Microsoft Exchange configuration, visit Microsoft Learn.
It is mandatory to redirect the catchall and bounce address to the BridgeERP subdomain of the database. Every other alias used must be redirected as well.
Example
With one sales team, the following redirections are required:
catchall@company-name.com → catchall@company-name.www.mybridgeerp.com
bounce@company-name.com → bounce@company-name.www.mybridgeerp.com
info@company-name.com → info@company-name.www.mybridgeerp.com
Important
Some providers ask to validate the redirection by sending a link to the target email address. This procedure is an issue for catchall and bounce since they are not used to create records.
Modify the catchall value on the mail alias domain. developer-mode must be enabled to access this menu. For example, it can be changed from catchall to temp-catchall. This will allow to use catchall as the local-part of another alias.
Open an app that uses an alias. For example, CRM contains aliases for each sales team. Set catchall as the local-part of the alias of a sales team.
The validation email will create a record in the CRM app. The email sent will be visible in the chatter, allowing you to validate the redirection.
Do not forget to change back the alias of the sales team and the catchall value on the mail alias domain, just as they were before this procedure.
Note
An alternative to redirections is forwarding. With forwarding, the address forwarding the email will be identified as the sender, while with redirections, the original sender will always remain.
Incoming mail servers
As mentioned earlier, using redirections is the recommended method to receive emails in BridgeERP. However, it is also possible to set up incoming mail servers. Using this method means creating an incoming email server for each mailbox on your server, catchall, bounce, and every alias of the database, in order to fetch all incoming emails.
Warning
BridgeERP’s Incoming Mail Servers feature is designed for shared inboxes (e.g., sales@yourcompany.com or support@yourcompany.com) to route messages to team pipelines, tickets, or documents.
Using personal email addresses (e.g., mitchell.admin@yourcompany.com) as incoming mail servers is not recommended. Doing so can lead to increased security risks, unintended message routing, privacy issues, and difficulties syncing replies correctly.
Incoming mail servers are created by going to .
Important
We recommend using the IMAP protocol over the POP protocol, as IMAP fetches all unread emails, while POP fetches all the emails’ history and then tags them as deleted in your mailbox.
Tip
It is also possible to connect a mailbox through Gmail with Google OAuth or Outlook with Microsoft Azure OAuth.
Regardless of the protocol chosen, emails are fetched using the Mail: Fetchmail Service scheduled action.
Additionally, using an incoming mail server in BridgeERP gives the opportunity to create new records in a specified model. Each incoming mail server can create records in a different model.
Example
Emails received on task@company-name.com are fetched by the BridgeERP database. All fetched emails will create a new project task in the database.
MX record
A third option is to create a MX record in your DNS zone which specifies the mail server managing emails sent to your domain. Advanced technical knowledge is required.
Important
This configuration only works with a subdomain on the BridgeERP Online or BridgeERP Cloud infrastructure (e.g., @mail.mydomain.com). Point the MX record from the custom subdomain to the BridgeERP subdomain of your database, e.g., from mail.mydomain.com to dbname.www.mybridgeerp.com.
Below are presented some specifications depending on the hosting type:
BridgeERP Online
The custom subdomain must be added to your BridgeERP Portal.
BridgeERP Cloud
The custom subdomain must be added to the settings of the project:
Infinite email loops
In some cases, infinite mailing loops can be created. BridgeERP provides some protection against such loops, ensuring the same sender cannot send too many emails that would create records to an alias in a specific time span.
By default, an email address can send up to 20 emails in 120 minutes. If more emails are sent, they are blocked and the sender receives the following message:
To change the default behavior, enable developer-mode, then go to to add two parameters.
For the first parameter, enter mail.gateway.loop.minutes as the Key and choose a number of minutes as the Value (120 is the default behavior).
For the second parameter, enter mail.gateway.loop.threshold as the Key and choose a number of emails as the Value (20 is the default behavior).
Allow alias domain system parameter
Incoming aliases are set in the BridgeERP database to create records by receiving incoming emails. To view aliases set in the BridgeERP database, first activate the developer mode. Then, go to .
The following system parameter, mail.catchall.domain.allowed, set with allowed alias domain values, separated by commas, filters out correctly addressed emails to aliases. Setting the domains for which the alias can create a ticket, lead, opportunity, etc., eliminates false positives where email addresses with only the prefix alias, not the domain, are present.
In some instances, matches have been made in the BridgeERP database when an email is received with the same alias prefix and a different domain on the incoming email address. This is true in the sender, recipient, and CC email addresses of an incoming email.
Example
When BridgeERP receives emails with the commercial prefix alias in the sender, recipient, or CC email addresses (e.g. commercial@example.com), the database falsely treats the email as the full commercial alias, with a different domain, and therefore, creates a ticket/lead/opportunity/etc.
To add the mail.catchall.domain.allowed system parameter, first, activate the developer mode. Then, go to . Click New. Then, type in mail.catchall.domain.allowed for the Key field.
Next, for the Value field, add the domains separated by commas. Manually (Save), and the system parameter takes immediate effect.
Local-part based incoming detection
When creating a new alias, there is an option to enable Local-part based incoming detection. If enabled, BridgeERP only requires the local-part to match for routing an incoming email. If this feature is turned off, BridgeERP requires the whole email address to match for routing an incoming email.