I’m assuming that Barracuda is extracting the identifier pattern from the email source and matching it to sutieCRM and then building the proper opt-out URL atomically at the time the email is received. We removed the default opt-out URL and added our own that redirects to an unsubscribe page on our Website. The opt-out URL sent by Barracuda doesn’t exist anywhere in the source of the emails sent.
Were is the opt-out processed? We want to add an additional parameter to be passed that only we know so we can avoid this in the future. Or if anyone has any better ideas to combat this crap. Thanks
The Source IP Addresses below are owned by Barracuda:
209.222.82.161 - - [25/Apr/2019:07:00:08 -0400] “GET /index.php?entryPoint=removeme&identifier=f2ff90f6-e75e-9642-98f7-5cc19343ef52 HTTP/1.0” 200 49 “-” “Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)”
209.222.82.137 - - [25/Apr/2019:07:00:12 -0400] “GET /index.php?entryPoint=removeme&identifier=9dc88d0f-e4ce-995c-7109-5cc1935cf9b4 HTTP/1.0” 200 49 “-” “Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)”
209.222.82.149 - - [25/Apr/2019:07:00:21 -0400] “GET /index.php?entryPoint=removeme&identifier=28a36e11-966b-5829-6157-5cc193f54aff HTTP/1.0” 200 49 “-” “Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)”
209.222.82.143 - - [25/Apr/2019:07:00:28 -0400] “GET /index.php?entryPoint=removeme&identifier=6bc3b349-0846-239c-7066-5cc1936e775b HTTP/1.0” 200 49 “-” “Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)”