This particular log was when I was testing idle timeout of 300 seconds
in Spamdyke, thus the longer delay.
Overall, the server is not that busy (avg 1-1.5), but will keep an eye
out for peak loads that may coincide with timeouts.
On 12/27/22 18:29, Eric Broch wrote:
It looks like the start
Hi,
It seems like suddenly my QMT installation started acting up and reject
mail (several days now). It does not deliver bounces but reports that
the sending server, e.g., Yahoo, etc, could not connect to send mail.
There is no MTA code in returned mail, at all. Initially, Gmail was
having an
You may want to share the headers of the incoming message for anyone to
have a better idea of what is there.
Mask/remove email and IP addresses and share the rest of the headers
before the message starts. Perhaps someone will spot anything there.
Otherwise, it is just a guessing game.
On 8/
On the 2nd thought, MIPSpace could be blocking everybody and there is no
way to remove yourself. In any case, you want to interact with whoever
is rejecting your mail based on MIPSpace list. In the worst case
scenarios, you can request that your VPS provider reaches out to the
receiving network
If you were assigned an IP address that was already on the list (range),
then not much. They may be blocking entire ranges.
Check similar IP addresses in their database to confirm. Ultimately, it
is the decision of the receiving side to use mipspace that is
responsible for your mail being bloc
You should try this:
https://github.com/fail2ban/fail2ban/blob/master/config/filter.d/qmail.conf
Ed
On 08/06/2014 06:09 PM, Dan McAllister wrote:
I am curious -- has anyone looked into a fail2ban implementation for QMT
One of my larger mail servers is being attacked (from China, currently,
b
The original patch is here
http://pyropus.ca/software/misc/qmail-1.03-domainbindings-1.2.patch
My modified one is attached.
I added
%patch9 -p1 -F 50
to spec file for the first two patches. Cheating, I know. :-)
I had to modify the patch file to remove the last two lines from the
last mat
I bound qmailtoaster services to run on a specific primary IP address
(confirmed to be a correct IP by netstat), yet when the email is sent,
the received email copy shows that SPF, X-Originating-IP and Received:
from lines display the secondary IP. This creates problems for me, since
messages ofte
