[squid-users] acl "clientside_mark" problem

[Amos Jeffries]

On 16/10/18 11:13 PM, Antony Stone wrote:
> On Tuesday 16 October 2018 at 11:38:53, morteza omidian wrote:
> 
>> Hi
>> why anybody don't answer me?
> 
> Maybe we don't have experience with precisely what you're trying to do.
> 
> Maybe we're busy with our day jobs.
> 
> Maybe we're confused by the multiple messages you send about approximately the 
> same topic but with different information in them.
> 
> Maybe because we're waiting for your answer to responses sent back to you (eg: 
> http://lists.squid-cache.org/pipermail/squid-users/2018-October/019432.html )
> 

[ leaving that in because it was so well-said.]


>> Please help!
> 
> Please remember this is free, open source software and you are writing to a 
> mailing list and asking for help from volunteers who choose to spend some of 
> their own time answering questions they feel able to help with.
> 
> This is not a commercial support service.
> 
>> I compiled Squid 4.3 with this options in linux
>> server:                    ./configure   --enable-linux-netfilter 
>> --enable-zph-qos when i change my squid configuration file and add this
>> line "acl MY_CLIENTs clientside_mark 0x1" I got  error messages like this:
>> root at linux:~# /usr/local/squid/sbin/squid -k restart
>> 2018/10/16 09:33:42| FATAL: Invalid ACL type 'clientside_mark'2018/10/16
>> 09:33:42| FATAL: Bungled /usr/local/squid/etc/squid.conf line 5: acl
>> CLIENT clientside_mark 12018/10/16 09:33:42| Squid Cache (Version 4.3):
>> Terminated abnormally.CPU Usage: 0.025 seconds = 0.017 user + 0.008
>> sysMaximum Resident Size: 38592 KBPage faults with physical i/o: 0 What is
>> wrong with my configuration??What should  i do?
>> Tanx
> 
> Also, formatting your messages more clearly might help people to understand 
> the question better.
> 
> Oh, yes, and Please Do Not set Reply-to on list messages.
> 


I was intending to keep this between the admin already working on the
issues. But maybe I should explain a few details that I uncovered in the
last few days.


There is something about the way you (morteza) are posting messages to
the mailing list which is causing a bunch of spam to be delivered along
with each of your emails - often this spam arrives first by 1-2 seconds.

These spam are clearly forging the same message-ID your emails use to
*uniquely* identify themselves. As a result it takes longer for your
real message to reach the list. The system has to detect and erase the
spam messages before your message is accepted as having a unique ID from
the leftover emails Yahoo is trying to deliver.

Another side-effect is that our servers rejecting the burst of spam
causes the Yahoo system to become extra suspicious of our servers for a
while. During that time Yahoo is either delaying or rejecting emails
which we are trying to deliver to you and other Yahoo users. That
includes your own request going back out.

So if the person who might have answered your question immediately
happened to be one of those Yahoo users - they are not going to receive
your message for many hours, maybe a whole day. Or sometimes never at all.

If one of us non-Yahoo users do receive it happen to reply quickly
during that slowdown period our message may take hours/days to reach
you, or be rejected entirely by Yahoo and you never see it.
Unfortunately the length of this time is not easily known, and also gets
restarted each time this situation happens.


I hope this clarifies what is going on here. I know the problem is
probably not your fault, but there are some things you can do to help
everyone have a better time communicating. Like, tweak your mailer
settings. Not use the web UI at all if you can. Patience, etc.

Is it probably a good idea also to get your computing device checked for
virus etc infections. I'm not sure how the spam gets your message-ID
value, but the timing of it is a bit suspicious to me.

Amos