Yes, we had that problem too,  a few weeks ago.

The problem could finally not be solved, so we went back to a groupwise server-backup that was fortunately taken a few hours before.

Reason not clear, but a user created a blog entry in a blog which was configurated for announcement and he additionally checks the send email button. Normally the the post then comes twice, but this post was repeated endless. We had to stop the MTA for the corresponding domain to stop the mailflood and to prevent the postoffices  from running out of space. All attempts to fix this with groupwise backend tools failed. When we started the MTA for testing, immediatelyat the mailflood begun again.

One issue is perhaps interesting: the announcement in the blog was configured for a group of 6 Users,
but only 2 of them were affected by the mailflood.

Hello, all.

We also have been having similar issues. We have Vibe 4.0.6 (Build 5467, 3/15/19). In our GroupWise mgt console, in GWIA -> Access Control tab -> SMTP Relay Settings, we have Vibe server as an exception.

So, every 3 months on a consistant bases, we have been getting SPAMMED by Vibe to GroupWise. Thousands of the same message. An example of the issue is when a user would upload a PDF to a folder, and users who also subscribe to that folder, will get those same spam messages. This cripples GWIA and no new email messages are delivered.

Our temporary fix is to 1) Shut down & reboot Vibe 2) Shut down GWIA & MTA 3) Go to our SMTPQ folder and delete those messages (all with the same byte size), 4) Restart GWIA, and then our email would be back to normal (incoming & outgoing).

Interestingly, in the GW console settings -> SMTP/MIME tab -> Security Settings -> Mailbomb Security -> We have it to check 10 messages every 5 seconds. And, these Vibe emails are still getting through.

Does anyone have a solution to address them, on a permanent basis? Or, perhaps, there is a log to check what is happening here.

Hi,

I recommend you open a Service Request and reference Bug# 1138208

Cheers,

Hi Jlee_eye,

has your problem been solved rsp. did you find a permanent solution?

Yesterday we had the problem twice, in the morning and in the afternoon.

The vibe mail report showed al lot of  retries of the same notification driven mail , again and again.

Different error texts were shown like "Couldn't connect to host, port: <our groupwise Server IP>, 25; timeout 15000; nested exception is: java.net.ConnectException: Connection refused (Connection refused)"

or

"Could not parse mail; nested exception is com.sun.mail.smtp.SMTPSendFailedException: 554 connection rejected."

Something goes wrong with the comunication between the vibe smt-Server and the Groupwise smtp.

In your last post, you mentioned deleting messages from the smtpQ. Can this be done over the gwia Console or directly in the file system. In the latter case, could you please post the file location of this Queue Folder (our vibe 4.0.6  is installed on a virtualized SLES Server)

Thx in advance !

Hi,

I recommend you open a Service Request and reference Bug# 1138208 so that you can get the patch.

Cheers,

Hi Jlee_eye,

you wrote:

Our temporary fix is to 1) Shut down & reboot Vibe 2) Shut down GWIA & MTA 3) Go to our SMTPQ folder and delete those messages (all with the same byte size), 4) Restart GWIA, and then our email would be back to normal (incoming & outgoing).

I can't find the SMTPQ folder you are mentioning. Could you give me a quick hint where to look for.

Thanks in advance
Ben

Hi Laura,

about 8 weeks ago, we opened a Service Request with reference Bug# 1138208, then got and applied the corresponding patch.

Lat week, on february, the 28th 2020 , the mail storm happened again, after setting a date in a vibe calendar that was configured for notification to a large group of users. The GW mailboxes of all thes users where spammed in a few minutes with about 13000 of the same notification. We had to stop vibe and GW Server and restored GW Server to a point before the incident.

Maybe a kind of  interprocess communication hazard or something, because its not reliably reproducible.

This is not a "normal" bug. This is a very serious bug, affecting central components of our internal (and also at least external) communication.

We hope now, that an upgrade to vibe 4.0.7 has addressed this bug and hope that this version will be released soon downloadable in the customer center.

Cheers,
Gerard