spammer | Простой | SMS library

After asking for help on this forum, I discovered that the email addresses were registering on many websites but not spamming (yet).

https://www.stopforumspam.com/forum/viewtopic.php?pid=51378

As Zoho Support Team said, the problem is with SPF alignment.

On analyzing the attached DMARC report, we see that email sent using the source IP "XXX.XXX.XXX.XXX" had passed the SPF & DKIM authentication. Please be informed that DMARC policy is evaluated based on "SPF authentication & SPF Alignment" or "DKIM authentication & DKIM Alignment". In the below attached report, we see the SPF Authentication is passed but SPF alignment fails as the From domain "client.com.ar" & Return Path domain "server.com" are different and that's the reason its mentioned as fail. To know more about DMARC policy, https://postmarkapp.com/guides/dmarc#how-does-dmarc-work

This is due to postfix aplying SRS, so reply-to is @forwarder-domain.com so breaks SPF alignment with the sender domain.

Seems unsolvable.

You have to remove the ctx parameter since it's not passed when on_message is called, and instead of ctx.author.send() use message.author.send(). If you really want to use ctx in on_message, because you need it for other parts of your code that you haven't shown here because it's irrelevant for the question, add ctx = await bot.get_context(message) at the top of on_message

References:

• on_message
• get_context

I generally don't recommend doing heavy stuff like this in an on_message event. I recommend using a cache, and add the user as usual.

But to answer your question:

The check would be very simple:

A static website means that their is no server-side code that can be executed. PHP is a language that has to be executed on the webserver, which is not supported as @hephalump points out with the reference to this question in the comments.

This means you can't use PHP to create a contact form for a static website in S3 as it requires server side interactions.

The error message you showed us comes from a different source though.

When you set up static website hosting in S3, it allows you to set a website index document and an error document. The index will be the default page if you access the domain and the error document will be displayed in case a user navigates to a key that doesn't exist or other errors.

You're seeing the error message, because error.html, which is the error document you configured, doesn't exist in the bucket. Presumably S3 notices you tried to do something it can't do and thus redirects you to the error document, which doesn't exist.

When using a command that takes a number as the input (like Sleep, you do not need to enclose your numeric variables in parenthesis like %var% (As opposed to a command like Send that takes a text input in which you would need to do so in order to disambiguate it)

As such, you can remove the parenthesis surrounding your Interval variable in Sleep, %Interval% * 1000, so you end up with Sleep, Interval * 1000

Final Code:

If a page refresh makes an API call, then that API call is accounted for quota usage.

Now, you say that your page refreshes at a rate of one Video.list API endpoint call per minute.

Therefore, during a full day (24 hours), you'll have 24 * 60 = 1440 calls to Videos.list.

According to the official specification of Videos.list, each call to this endpoint has a quota cost of 1 unit.

Consequently, if only accounting for 1440 calls to Videos.list, the quota cost of your page refreshing amounts to 1440 units. That's well below the allocated daily quota of 10000 units.

This implies also that the API will by no means consider you a spammer.

Here's how I'd do that.