Configurare l'email in arrivo per creare nuovi argomenti o raggruppare i messaggi

[Discourse]

This guide explains how to set up incoming emails to create new topics or group messages in Discourse, including configuration of site settings and category or group-specific settings.

Required user level: Administrator

This guide covers:

• Enabling and configuring incoming emails
• Choosing between category and group for incoming emails
• Setting up incoming emails for a group
• Setting up incoming emails for a category
• Deciding how forwarded emails are handled

If you have already set up reply via email, or you are on a hosting plan that pre-configures your incoming email, you’re now ready to set up Starting a New Topic via Email.

Configuring site settings

To enable incoming emails, you need to configure three main site settings:

1. email_in: This setting must be enabled for incoming emails to work.
2. email in allowed groups: Users must belong to this group to send an email to Discourse.
3. enable_staged_users: This setting allows the creation of staged users for unknown email addresses.

For Discourse hosted sites, the enable_staged_users setting is disabled and hidden during the trial to prevent abuse. Once a subscription is started, the setting is unhidden. To ask for it to be enabled during your trial, contact team@discourse.org.

To configure these settings:

1. Go to your site’s Admin panel
2. Navigate to Settings
3. Search for each setting and configure as needed

Staged users are special user accounts in Discourse created to support incoming emails from anyone. They have limited functionality:

• Can’t be mentioned or searched for
• Don’t receive digests
• Can only be notified of and reply to topics they started or were invited to
• Will be promoted to a normal user if they create an account using the same email address

Choosing between categories and groups

Decide whether you want incoming emails to create topics in a category or messages in a group.

Using a group

Benefits of using a group:

• Useful for setting up a support-like workflow
• Creates a message sent to all group members
• Messages appear in /my/messages
• Anyone can send an email to the group
• Any group member can read, reply, delete, or archive the message
• Each group member has their own read tracking state

Using a category

Benefits of using a category:

• Simulates a mailing list
• Creates a topic in the specified category
• Anyone with access to the category can read and reply via web interface or email
• Respects category security settings
• Respects the email in allowed groups site setting
• Allows disabling staged users on a per-category basis

Setting up incoming emails for a group

To configure incoming emails for a group:

1. Go to the Groups page from the main menu

2. Click on the group name (or create a new group)
   

   

3. For a new group, find the “Custom incoming email address” field at the bottom of the form
   

   

4. For an existing group, go to the Manage tab, then click Interaction in the left side menu
   

   

5. Enter the email address(es) you want to associate with the group (separate multiple addresses with |)

6. Click Save to apply the changes

For Discourse hosted sites, check the “Accept incoming emails sent to:” box and forward your custom email(s) to this address for proper functionality.

Setting up incoming emails for a category

To configure incoming emails for a category:

1. Go to the category page (e.g., /c/<category_slug>)

2. Click the Edit button
   

3. In the Edit category modal, click the Settings tab
   

   

4. Look for “Accept emails from anonymous users with no accounts” and “Custom incoming email address” fields
   

   

5. Enable “Accept emails from anonymous users with no accounts” if you want to create staged users for unknown email addresses

6. Enter the email address(es) you want to associate with the category

7. Click Save Category to apply the changes

For Discourse hosted sites, check the “Accept incoming emails sent to:” box and forward your custom email(s) to this address for proper functionality.

Forwarded emails behavior

You can decide how forwarded emails appear in Discourse using the forwarded emails behaviour site setting, which has the following options:

• hide - a new new topic or PM will be created with the forwarded text included as hidden text that can be expanded to view
• quote - a new topic or PM will be created with the forwarded text included as quoted text.
• create replies - a new topic or PM will be created authored by the original sender. Replies will be created authored by participants in the email. If the user accounts do not already exist matching the sender email addresses, they will be created as staged user accounts.

Additional resources

• Troubleshoot reply by email

[Ivan_Rapekas]

Qualche pensiero sull’opzione in arrivo per le email reindirizzate (poiché l’indirizzo del destinatario originale viene salvato invece di cambiare in quello reindirizzato).

Caso: Ho un account Atlassian Confluence con un indirizzo email personale collegato lee@dot.com. Volevo ricevere email su qualsiasi modifica allo spazio e raccoglierle in un unico posto su un forum. Quindi ho creato un abbonamento all’intero spazio. Tali email generate automaticamente contengono la frase “Smetti di guardare”, che avevo pianificato di utilizzare come modello per il filtro.

Nelle impostazioni della casella di posta, ho abilitato una regola di reindirizzamento per le email che includono questo modello, come mostrato nell’immagine sottostante. L’email dovrebbe essere reindirizzata a bob@ex.com. Questa email corrisponde a una specifica categoria del forum. Dopo l’elaborazione, questa email viene automaticamente eliminata dalla mia casella di posta lee@dot.com, in modo da non dover gestire il flusso di email.

Come si è scoperto, le email direttamente indirizzate a bob@ex.com sono state assegnate correttamente alla categoria del forum. Ma le email reindirizzate per qualche motivo sconosciuto sono finite nella sezione non categorizzata.

Forse qualcuno cercherà una soluzione allo stesso problema mio. Quindi descriverò qual era il problema.

Quando ho esaminato attentamente la sezione dei log in /admin/email/received, ho scoperto che il campo TO delle email reindirizzate contiene non l’indirizzo che ho impostato nella proprietà della categoria, ma la mia email personale. Ed è quello che dovrei inserire nella categoria come indirizzo email in arrivo.

Spiegazione:

• №1 (email diretta) va alla categoria corretta
• №2 e №3 (email reindirizzate) vanno a non categorizzate

Pertanto, il suggerimento popup mi ha aiutato a capire quale indirizzo viene utilizzato nel campo TO. Forse è corretto qui, o forse verrà corretto in futuro, ma al momento funziona così.