[BUG] IMAP Bounce settings UI missing

[przemekscj]

🐛 Bug Description

The IMAP bounce monitoring settings are not visible in the Mailboxes settings UI, despite being documented as available since v2.0.5. Technical investigation shows that while the database migrations and backend logic (Controllers, Models, and Artisan commands) are fully implemented, the Vue components are missing the necessary input fields.

Steps to Reproduce:

1. Go to Settings -> Mailboxes.
2. Edit an existing mailbox or try to create a new one.
3. Observe that there is no section for "IMAP Bounce Monitoring" as described in the documentation.

Expected Behavior:
A section for IMAP configuration (Host, Port, Encryption, Email, Password) should be visible in the mailbox settings.

Actual Behavior:
The fields are missing from the UI. A grep on the frontend source code (resources/js/Pages/Settings/Mailboxes/Index.vue) confirms that the keyword "bounce" is entirely absent from the component.

📸 Screenshots / Logs:

• Artisan command exists: php artisan list | grep bounce -> bounce:process-mailboxes (Found)
• Database columns exist: DESCRIBE mailboxes; -> bounce_imap_host (Found)
• Frontend check: grep -ri "bounce" resources/js/Pages/Settings/Mailboxes -> (Result: Empty)

Environment:

• NetSendo version: v2.0.10
• OS: Linux (TrueNAS SCALE)
• Docker version: v2.32.3
• Build type: Docker image ghcr.io/netsendo/netsendo:latest

Additional Context:
It appears the frontend assets were not updated or compiled with the new UI components in the latest Docker builds.

[GregECAT]

Response to [BUG] IMAP Bounce settings UI missing #14

✅ Fixed

Root Cause

The IMAP Bounce Monitoring feature was introduced in v2.0.5 with complete backend support:

• ✅ Database migration (bounce_enabled, bounce_imap_host, bounce_imap_port, bounce_imap_encryption, bounce_imap_credentials, bounce_imap_folder, bounce_last_scanned_at, bounce_last_scan_count)
• ✅ Model (Mailbox) — all bounce fields in $fillable, credential encryption/decryption
• ✅ Controller (MailboxController) — update() processes bounce fields, testBounce() endpoint
• ✅ Service (BounceMailboxService) — IMAP connection, DSN parsing, bounce processing
• ✅ Artisan command (bounce:process-mailboxes) — CRON-integrated every 5 minutes
• ✅ Routes — POST /settings/mailboxes/{mailbox}/test-bounce
• ✅ Translations — all 4 locales (EN, PL, DE, ES) with complete mailboxes.bounce.* keys

However, the Vue component (resources/js/Pages/Settings/Mailboxes/Index.vue) was never updated to include the UI form fields for configuring bounce monitoring. The modal was missing the entire "IMAP Bounce Monitoring" section.

Fix Applied

File: src/resources/js/Pages/Settings/Mailboxes/Index.vue

1. Form Object Extended

Added 7 new fields to the Inertia useForm() definition:

bounce_enabled: false,
bounce_imap_host: "",
bounce_imap_port: 993,
bounce_imap_encryption: "ssl",
bounce_imap_username: "",
bounce_imap_password: "",
bounce_imap_folder: "INBOX",

2. Edit Mode Data Population

When editing an existing mailbox, bounce fields are now populated from the mailbox object:

form.bounce_enabled = mailbox.bounce_enabled || false;
form.bounce_imap_host = mailbox.bounce_imap_host || "";
form.bounce_imap_port = mailbox.bounce_imap_port || 993;
form.bounce_imap_encryption = mailbox.bounce_imap_encryption || "ssl";
form.bounce_imap_username = "";  // left blank for security (leave empty to keep existing)
form.bounce_imap_password = "";  // left blank for security (leave empty to keep existing)
form.bounce_imap_folder = mailbox.bounce_imap_folder || "INBOX";

3. UI Section Added

A complete "Bounce Mailbox Monitoring" section was added to the configuration modal, positioned between the "Daily Limit" field and the "Test Result" area. Features:

Feature	Description
Enable toggle	Animated switch to enable/disable bounce monitoring
IMAP Host	Text input with imap.example.com placeholder
IMAP Port	Number input (1-65535), default: 993
Encryption	Dropdown: SSL / TLS / None
IMAP Folder	Text input, default: INBOX
Username	Email input with "leave empty to keep" hint
Password	Password input with visibility toggle (eye icon)
Last Scan Info	Displays timestamp and bounce count from last scan
Test Connection	Button that calls POST /settings/mailboxes/{id}/test-bounce
Test Result	Success/error indicator with message

4. Visibility Rules

• Section is only visible in edit mode (not when creating a new mailbox — bounce config requires a saved mailbox first for the test endpoint)
• Section is hidden for Gmail provider (Gmail handles bounces via webhook, not IMAP)
• IMAP configuration fields are animated in/out based on the toggle state using Vue <Transition>

How to Verify

1. Go to Settings → Mailboxes
2. Click Edit (⚙️) on any existing non-Gmail mailbox
3. Scroll down past "Daily Limit" — the "Bounce Mailbox Monitoring" section should now be visible
4. Toggle the switch to enable bounce monitoring
5. Fill in the IMAP credentials
6. Click Save — the bounce settings will be persisted
7. Re-open the mailbox — the toggle and non-sensitive fields (host, port, encryption, folder) should be populated; username/password fields will be blank (leave empty to keep existing values)

Files Changed

File	Change
src/resources/js/Pages/Settings/Mailboxes/Index.vue	Added bounce form fields, edit population, toggle UI, IMAP configuration section, test connection button
CHANGELOG.md	Added entry under [Unreleased] → Fixed

Note: No backend changes were required — the controller, model, service, and translations were already complete since v2.0.5.

[przemekscj]

Widzę jeszcze drobny błąd:
Ustawienia listy - Zaawansowane nie przyjmuje zmiany z wartości domyślnych, pomimo komunikatu o zapisaniu ustawień: stale jest Per lista oraz 3.

[GregECAT]

✅ Fixed

Thanks for the follow-up @przemekscj — you're right, this was a real bug, and it turned out to be purely server-side.

Root Cause

The Zakres odbić (Per lista / Globalny) and Próg miękkich odbić fields were being sent by the frontend correctly, but the backend was throwing them away.

All the settings controllers validated only the toggle:

'settings.advanced.bounce_analysis' => 'boolean',

…with no rules for bounce_scope or soft_bounce_threshold. In Laravel, $request->validate() returns only the keys that have rules, and that validated array is exactly what gets persisted ($mailingList->update($validated) / $user->settings = $validated['settings']). So both fields were silently stripped on every save — which is why you got the "settings saved" confirmation while the values snapped straight back to the defaults Per lista and 3.

(The Analiza Odbić toggle saved fine because it did have a rule — matching exactly what you saw.)

Fix Applied

Added the missing validation rules everywhere these settings are persisted:

'settings.advanced.bounce_scope' => 'nullable|in:list,global',
'settings.advanced.soft_bounce_threshold' => 'nullable|integer|min:1|max:10',

File	Method(s)	Scope
app/Http/Controllers/MailingListController.php	store(), update()	Per-list bounce settings (the reported case)
app/Http/Controllers/DefaultSettingsController.php	store()	Global default bounce settings (same section, same bug)

How to Verify

1. Go to Ustawienia listy → Zaawansowane.
2. Change Zakres odbić to Globalny and set Próg miękkich odbić to e.g. 5.
3. Save, then re-open the list — Globalny and 5 now persist instead of reverting to Per lista / 3.

The values are consumed by BounceProcessingService (bounce_scope, soft_bounce_threshold), so bounce handling now honours the per-list configuration as intended.

Note: The frontend (MailingList/Edit.vue / Create.vue) was already correct — no Vue changes were needed. This was purely a server-side validation-whitelist gap.