LeadMagnet/leadchat
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs(leadchat): document LeadMail delivery_method fix and LeadmailDelivery patch in customization index
Some checks failed
Lock Threads / action (push) Has been cancelled
Details

Browse Source 
Both LeadMail-related touchpoints now logged in section B (Direct edits
to OSS files). Notes the LeadChat-owned vs upstream distinction so
future merges know which need defense and which are ours to evolve.
This commit is contained in:
netlas
2026-04-27 19:57:16 +03:00
parent a00bcb204e
commit 0839fbec79
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
LEADCHAT.md
View File

@@ -28,7 +28,8 @@ LeadChat is a white-label Chatwoot fork maintained on the `leadchat` branch. Cus
| `app/models/channel/email.rb` (bottom) | One-line `include_mod_with` hook for the email_extension overlay | `# === LeadChat: microsoft_shared ===` |
| `app/mailers/conversation_reply_mailer_helper.rb` (bottom) | One-line `prepend_mod_with` hook for the helper extension overlay | `# === LeadChat: microsoft_shared ===` |
| `app/jobs/inboxes/fetch_imap_emails_job.rb` (bottom) | One-line `prepend_mod_with` hook for the fetch dispatcher overlay | `# === LeadChat: microsoft_shared ===` |
| `app/mailers/leadmail_delivery.rb` (`build_payload`) | Forward `In-Reply-To`, `References`, and `Message-ID` headers in the LeadMail API payload so conversation replies thread correctly when sent via the `imap_leadmail` transport | `# === LeadChat: microsoft_shared ===` |
| `app/mailers/leadmail_delivery.rb` (`build_payload`) | Forward `In-Reply-To`, `References`, and `Message-ID` headers in the LeadMail API payload so conversation replies thread correctly when sent via the `imap_leadmail` transport. (LeadmailDelivery is LeadChat-owned code — direct edit is acceptable; overlay would be over-engineering.) | `# === LeadChat: microsoft_shared ===` |
| `config/initializers/mailer.rb` (LeadMail and SMTP/sendmail branches) | Apply `delivery_method` and matching `*_settings` directly to `ActionMailer::Base`, not just `config.action_mailer.*`. Required because `devise.rb` runs alphabetically before `mailer.rb` and triggers ActionMailer's `on_load` hook with the default `:smtp` config — subsequent writes to `config.action_mailer.delivery_method` are silently ignored. Without this fix, all transactional email (Devise confirmation, password reset, invitations) silently fails with `Errno::ECONNREFUSED` to `localhost:25`. | `# === LeadChat: leadmail-delivery-fix ===` |
| `config/routes.rb` (3 separate blocks) | (1) `app_new_microsoft_shared_inbox` dashboard route; (2) account-namespaced `microsoft_shared/authorization` API endpoint; (3) `microsoft_shared/callback` OAuth callback | `# === LeadChat: microsoft_shared ===` |
| `app/javascript/dashboard/routes/dashboard/settings/inbox/channels/Email.vue` (3 separate blocks) | (1) import `MicrosoftShared.vue`; (2) `emailProviderList` entry for `microsoft_shared`; (3) router slot `<MicrosoftShared v-else-if="provider === 'microsoft_shared'"/>` | `<!-- === LeadChat: microsoft_shared === -->` and `// === LeadChat: microsoft_shared ===` |
| `app/javascript/dashboard/i18n/locale/en/inboxMgmt.json` | New keys: `INBOX_MGMT.ADD.MICROSOFT_SHARED.*` and `INBOX_MGMT.EMAIL_PROVIDERS.MICROSOFT_SHARED.*` | (no comment markers — JSON; flagged here in LEADCHAT.md instead) |