basicaly search for the offending
emil address which in you case contained " msimp "
Is that correct
Thanks
On 6/25/2013 12:00 PM, Jon Myers wrote:
When I had a customer that was compromised, and flooded outbound, I
first stopped mail processing, found who the sender was, then
&qu
When I had a customer that was compromised, and flooded outbound, I
first stopped mail processing, found who the sender was, then
"manually" deleted them out of the queue such as this...
WARNING, do NOT do these commands unless you fully understand them!!
/etc/init.d/qmail queue | grep msimp |
Two minor versions have been released since then, which
will also accounts for a pile of bugfix revisions between. Maybe
I'll just throw it on there and see what breaks. =) At least the
new versions tell me the limits in the error message.
At 10:44 AM 5/17/2013, Peter wrote:
Hi,
On Thu,
Since I have switched to dovecot, I'm reaching limits...
May 16 11:28:09 master: Warning: service(imap-login): process_limit
reached, client connections are being dropped
ps ax | grep dovecot | wc -l
200
(I was seeing a mix of imap and imap-login in the ps list)
doveconf reports default_client_l
At 01:57 PM 5/3/2013, you wrote:
On 05/03/2013 10:14 AM, Cecil Yother, Jr. wrote:
On 05/03/2013 10:11 AM, Eric Shubert wrote:
On 05/03/2013 07:58 AM, cj yother wrote:
On 05/02/2013 10:22 PM, Myers, Jon W wrote:
this is probably yet another thing for the vpopmail list, but I'm
not on that list
on port 25.
It let me connect with out authenticating. Should it have ? how can I stop
this .
-Original Message-
From: Jon Myers [mailto:myer...@alfredstate.edu]
Sent: Wednesday, March 27, 2013 1:12 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: RE: [qmailtoaster] Relaying
Did you
Did you really REMOVE sender_nocheck, or did you just set it to
0? I'm guessing you should have just set it to 0.
Also, by nature, users should be allowed to relay, as thats how they
send mail, but of course they need to authenticate first, unless they
are coming from the local network, in whic
If this is a new install, and you couldnt find the defaults in the
docs, they are admin & toaster.
If you cant remember the user/pass, you can use the standard htpasswd
mechanism:
htpasswd -c /usr/share/toaster/include/admin.htpasswd admin
At 09:00 AM 3/27/2013, Jim wrote:
HOw can i retriv
At 11:09 AM 1/29/2013, Eric Shubert wrote:
On 01/29/2013 08:55 AM, Jon Myers wrote:
Since I still have the data from the old server, its trivial to merge
the mrtg stuff. Not sure on the isoqlog stats, as I havnt played with
that before.
Me neither. I'm not sure where any of that data
After moving my QMT using qtp-backup and qtp-restore, I noticed that
the stats (mrtg and isoqlog) did not transfer over. Is this a
feature or a bug?
Since I still have the data from the old server, its trivial to merge
the mrtg stuff. Not sure on the isoqlog stats, as I havnt played
with that
At 01:24 PM 1/25/2013, Eric wrote:
On 01/24/2013 10:53 PM, Myers, Jon W wrote:
Silly me. I didnt bother checking the /var/log/qmail/send/current
file because I thought to myself "well, I can send just fine!"
but after poking around, and looking at that file; it greeted me with this:
@40005
At 02:17 PM 11/21/2008, Dan wrote:
Ok... since we're talking old *nix here, I thought I'd add my 2-cents worth...
Short & sweet: The password entries for your OLD system should import to
the new one without issue. The new system will already know how to use the
OLD password format, but when us
I've downloaded, installed qmail-intel-vm-1.4.1.zip, and have it running in
a VM on my AMD box (since the AMD version was 1.3.1).
Through various reading, there is conflicting stories about post
install. I see that binary packages are included now, so I'm guessing
theres no "final steps" to b
13 matches
Mail list logo
