on OS 11.1).
Sorry for spamming the list, but maybe this will help a future googler. :/
- Steve
> On Jan 30, 2021, at 2:53 PM, Eric Broch wrote:
>
> Try a different dns server
>
> On 1/30/21 12:25 PM, Steve Linberg wrote:
>> Greetings all. I’ve been running qmail on m
he speed of 1.1.1.1, but still can have the lookups.
>
>
>
> On Sat, January 30, 2021 11:53 am, Eric Broch wrote:
>> Try a different dns server
>>
>> On 1/30/21 12:25 PM, Steve Linberg wrote:
>>> Greetings all. I’ve been running qmail on my servers and vms fo
2021-01-30 15:46:02.080429500 tcpserver: end 2233 status 256
2021-01-30 15:46:02.080430500 tcpserver: status: 0/100
Any other ideas?
> On Jan 30, 2021, at 2:53 PM, Eric Broch wrote:
>
> Try a different dns server
>
> On 1/30/21 12:25 PM, Steve Linberg wrote:
>> Gre
Greetings all. I’ve been running qmail on my servers and vms for about 20 years
and it’s mostly worked great, but I’m having a thumper of a slowdown problem on
my current setup and I can’t get to the bottom of it… any help appreciated.
The environment is a very lightly-used private VM running ce
hat to do, but I really need to get this message out. Once
something hits a segfault, I’m pretty stuck. I’ve rebooted the server twice,
also, which I hate doing; didn’t help.
Any ideas for either a fix or a workaround so I can get this message out?
Thanks.
--
Steve Linberg, Chief Goblin
Sili
of the following form (where the QMAILQUEUE
> variable is set to simscan):
>
> QMAILQUEUE="/var/qmail/bin/simscan".
>
> then
>
> # cat /var/qmail/control/simcontrol
>
> and you should see the following lines which indicate that simscan calls
> clamav an
and
> spamassassin are invoked)
> 4) clamav & spamassassin
>
> 5) spamdyke
>
> 6) qmail-smtpd ...
>
>
> Dspam on the other hand is called later during delivery. I use it in
> .qmail-default.
>
>
>
>
>
> On 1/30/2017 9:09 AM, Steve Linberg
>
> 6) qmail-smtpd ...
>
>
> Dspam on the other hand is called later during delivery. I use it in
> .qmail-default.
>
>
>
>
>
> On 1/30/2017 9:09 AM, Steve Linberg wrote:
>> Thanks Eric. It’s very likely that I”m confused about this - I am using
>
> Eric
>
> On 1/30/2017 8:39 AM, Steve Linberg wrote:
>> Thanks for the suggestions, everyone. This is a small-scale system that’s
>> mostly for personal use, so unfortunately it doesn’t warrant the expense of
>> a standalone appliance for spam, so I’m pretty much lim
for about 15
years, and for the most part it’s worked reliably and well, but every once in a
while spammers change tactics and figure out a way through and there’s an
upsurge for a bit.
I’ll give sa-learn a shot and see if it improves anything.
Cheers,
Steve
--
Steve Linberg, Chief Goblin
these numbers high enough, or should I wait until I
have more? Or is it risky to do that at all?
Any advice for tuning this thing up? The spam problem seems to be getting worse
lately.
Thanks for any ideas.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be
arting location for most logs.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
but I haven’t
managed to get the various binaries working yet, and before I go bananas on it,
I just wanted to see if anyone else has already gotten it working. :)
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a
Happy to report no segfaults since I increased the softlimit in
/var/qmail/supervise/smtp/run from 64 megs to 128 megs. I also dropped the
softlimit in /var/qmail/supervise/submission/run back to 128 megs. So far so
good. Phew.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http
nks again.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
nfident now.
Thanks very much for the clues. Will report back after the weekend, but I’ve
got a good feeling now. :)
- Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
vchkpw in the above instance (they’re all like that, always in vchkpw).
I don’t know for sure if I’m softlimiting the right process in qmail
submission, or if it could be something else, or how to tell.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be k
y invoked by the qmail submission process chain?
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
the segfaults, but are there any other possible culprits that
might invoke vchkpw without enough RAM to do whatever it’s trying to do?
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
o now, but some
of the windows between segfaults have been longer than that, so I’m still
holding my breath.
- Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
k to 100 megs (which still feels like an awful lot)
and got immediate segfaults. I bumped it up to 200 megs about 30 minutes ago,
and no segfaults so far, but sometimes they’re a few hours apart. I don’t know
exactly what’s triggering them, so in part, it’s kind of a waiting game.
- Steve
--
e if it changes anything.
Thanks again to everyone for the help - hopefully we’ll get to the bottom of
this, and hopefully it’ll help some other people too.
- Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
port I'm using.
No, and it’s really just me authenticating at this point. There will be a few
more soon, but so far it’s very small-scale.
I’m going to do another round of incremental testing with qmailctl stop /
qmailctl start rather than qmailctl restart, and see if that makes any
h stop and start. This invalidates all of my testing, actually, so I’ll roll
it back to lower levels and do the stop/start process instead of restart, and
see how it goes. Thanks.
- Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
e changes to
/var/qmail/supervise/submission/run? That’s what I’ve been doing.
Anybody have any other ideas or theories? Again, this is a clean CentOS 7.2 VM
at DigitalOcean, with 2gb RAM. I’ve disabled ipv6 and selinux.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicon
there’s no spamc in the current toaster build, as far as I can see, and if
there is, I can’t find any config files, or any other component that controls
it. Something must, though, because messages over 500k are passing through
without being checked.
- Steve
--
Steve Linberg, Chief Goblin
the trick pretty well. Anyone know where it is?
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
so I can
increase the RAM if I have to, but it’ll of course increase the cost each time
I do, so I’m hoping I can squeak by with what I’ve got. I’ll report back
if/when I hit a number that stops the segfaults.
Cheers,
Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://s
y. 64 megabytes is the recommended setting from “Life
with Qmail” and “The Qmail Handbook”, so I thought I was safe raising it to
128k, or even 160k, but over a gig seems like an awful lot. Does it really need
to be that high?
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://si
nal setting was 6400, or 64,000,000, unless I misplaced something?
I thought going to 12800, and then 16000, was going roughly from 64megs
to 128 megs to 160 megs, and that that should be enough.
Sorry if I’m missing something stupidly obvious here…
- Steve
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
some distant way.
Maybe it’s even related to the /etc/resolv.conf issue. I’ll see how it goes
through the day.
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
in ipv6. I’m not actively using ipv6, and my first thought
was to just turn it off (in /etc/sysctl.conf), but even after a reboot, I was
still getting these messages, over and over in /var/log/maillog.
Does anybody have any ideas on either of these issues? Thanks in advance.
--
Steve Linberg
ctl restart
systemctl restart dovecot
And that’s it! Working for me.
Thanks again to all involved with this project, and again to Jamie Lerner to
taking the time to answer my questions, way above and beyond.
- Steve Linberg
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
h
33 matches
Mail list logo