Contrib.social

Don't throw SkipMailException when successfully adding it to the queue

Open on Drupal.org →
Created on 28 July 2025, 5 days ago

Problem/Motivation

When sending mails via the admin account - or any other account that has the privilege to see the exceptions - and the module adds the mail to the queue, it throws a SkipByMail Exception, that shows as an error message.

This confuses users and administrators, as the exception and the error-message suggest, that something went wrong - when in fact, the module acted as expected.

Steps to reproduce

* Install symfony_mailer_queue
* Trigger sending of any symfony mailer mail as admin
* See the "The email was queued for sending" Error-Message

Proposed resolution

Remove the message or make it optional - from my point of view it is not needed.

Remaining tasks

Review patch where the exception trigger gets removed - or provide another solution.

User interface changes

The "The email was queued for sending" Error-Message after a mail was added to the queue should be gone.

API changes

None.

Data model changes

None.

🐛 Bug report
Status

Active

Version

1.2

Component

User interface

Created by

🇩🇪Germany fisherman90 Dortmund

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @fisherman90
  • Comment 5 days ago →
    🇩🇪Germany fisherman90 Dortmund

    Issue fork with proposed resolution (removal of exception) added.

  • Merge request !9#3538386 - removed unneeded exception → (Open) created by fisherman90
  • Pipeline finished with Failed
    5 days ago
    Total: 150s
    #558801
  • Comment 4 days ago →
    🇩🇪Germany simonbaese Berlin

    @fisherman90 This exception is necessary to interrupt the sending during the initial email processing. As you can see in the failing tests, the emails are not processed correctly anymore when queued. I am open to changing the exception handling or catching the message if you provide a merge request that passes the tests.

    I am changing the issue type as this works as intended and is not a bug.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024