On 7/30/24 8:33 AM, Gellner, Oliver via mailop wrote:
On 30.07.2024 at 16:45 David Landers via mailop wrote:
I am attempting to submit a removal request via BarracudaCentral
(https://www.barracudacentral.org/rbl/removal-request) and it appears to be timing out or
otherwise failing, as I am r
On 2/23/22 5:27 AM, Mary via mailop wrote:
> [...]
> I use them with Linode's smallest offering ($5 for a 1GB server) as a hosting
> platform. But can't run ClamAV anti-virus because it requires at least 4GB of
> ram to load its default data set.
For what it's worth, in my experience ClamAV/clam
On 10/11/21 10:19 PM, John via mailop wrote:
Hello Matt,
The answer is yes, it's not good practice to block messages containing long
lines in emails. That will likely cause problems at either the sender or
recipient. Senders may receive non-delivery notifications, recipients may miss
mails.
I've sent a reply off list.
Thanks,
Erwin
On 10/4/21 1:15 PM, Michael Sofka via mailop wrote:
Most of our SMTP servers started being rejected by systems using
barracuda. The rejection included a link that provided no additional
information. I was able to find Barracuda's reputation page, and
On 4/5/21 9:35 AM, L. Mark Stone wrote:
And...
The barracudacentral.org website certificate expired yesterday as well.
Indeed. The relevant group is aware and working to fix that.
--Erwin
===
Get the 13 Email Threat Types eBook
https:/
On 4/3/21 8:59 AM, Jim Popovitch via mailop wrote:
Paging someone from Barracuda or EmailReg. EmailReg.org has been
offline for a while now.
https://www.barracudacentral.org/about/emailreg
As I understand it that should be deprecated/removed, I've nudged
someone about it.
--Erwin
===
On 10/23/20 11:04 AM, Erwin Harte wrote:
Hello,
We appear to be hitting a capacity ceiling from one of our ranges
(15.222.16.128/25) in delivering to their servers at 184.150.200.82
(smtpvipmtrlin.bell.net/mxmta.owm.bell.net) and 184.150.200.210
(smtpviptorin.bell.net/mxmta.owm.bell.net).
I
Hello,
We appear to be hitting a capacity ceiling from one of our ranges
(15.222.16.128/25) in delivering to their servers at 184.150.200.82
(smtpvipmtrlin.bell.net/mxmta.owm.bell.net) and 184.150.200.210
(smtpviptorin.bell.net/mxmta.owm.bell.net).
I reached out to postmas...@bell.ca (postma
On 2/6/20 1:43 PM, Kevin A. McGrail via mailop wrote:
Have IPs showing clean from BRBL with tickets open from recipients aka
Barracuda customers. Traceroutes show it gets fair enough that it's
unclear if it is an AWS or barracuda issue but we can't get to port 25.
Looking for any guidance to fi
