[qmailtoaster] UNable to send

2013-06-25 Thread System Admin
Hi all, Currently our mail mail server can only receive but not send any email. What logs can I check, and what might the problem be. Thanks - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For

Re: [qmailtoaster] UNable to send

2013-06-25 Thread System Admin
Emai server spamming I have over 200 thousand in the out queue Box must be compromised Any thing We can do to block outgoing . madmac On 6/25/2013 12:09 PM, System Admin wrote: Hi all, Currently our mail mail server can only receive but not send any email. What logs can I check, and what

Re: [qmailtoaster] UNable to send

2013-06-25 Thread Cecil Yother, Jr.
Closing the port using your IPtables would be the quickest or at the firewall level. On 06/25/2013 12:36 PM, System Admin wrote: Emai server spamming I have over 200 thousand in the out queue Box must be compromised Any thing We can do to block outgoing . madmac On 6/25/2013 12:09 PM,

Re: [qmailtoaster] UNable to send

2013-06-25 Thread System Admin
Hi Cecil, I am very familiar with IP tables, but what port to close for outgoing ? Surely can close 25, ? used qmHandle -s, to see the ammount then qmHandle -D, to remove all from Q, yes did warn all users. Thanks madmac On 6/25/2013 11:41 AM, Cecil Yother, Jr. wrote: Closing the port using

Re: [qmailtoaster] UNable to send

2013-06-25 Thread Cecil Yother, Jr.
Yes, port 25. That should still allow incoming traffic and outgoing on port 587 if secure connection is used, but block the spammer. On 06/25/2013 12:51 PM, System Admin wrote: Hi Cecil, I am very familiar with IP tables, but what

Re: [qmailtoaster] UNable to send

2013-06-25 Thread Jon Myers
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 |

Re: [qmailtoaster] UNable to send

2013-06-25 Thread System Admin
okay, I always set port 587 on the clients email setting, Thanks again madmac On 6/25/2013 12:01 PM, Cecil Yother, Jr. wrote: Yes, port 25. That should still allow incoming traffic and outgoing on port

Re: [qmailtoaster] UNable to send

2013-06-25 Thread System Admin
Hi Jon, so what I read here is you 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

[qmailtoaster] More

2013-06-25 Thread System Admin
Yet another weird error , came up on the consle ( putty login ) I was checking the queue for messages again qmHandle -s Messages in local queue: 0 Messages in remote queue: 0 [root@mail2 ~]# qmHandle -s Messages in local queue: 0 Messages in remote queue: 2 *and this showed up after the mail

Re: [qmailtoaster] UNable to send

2013-06-25 Thread Jon Myers
Yes, I search for that, then using cut a few times, I extract the message number, and that list gets put in the spam.txt file I update the locate database via updatedb. Then, I cat the spam.txt and feed it's output to xargs which in turn uses each line as an argument for the locate command.

Re: [qmailtoaster] UNable to send

2013-06-25 Thread System Admin
Thanks Jon, I will try this on an old unused box madmac On 6/25/2013 1:14 PM, Jon Myers wrote: Yes, I search for that, then using cut a few times, I extract the message number, and that list gets put in the spam.txt file I update the locate database via updatedb. Then, I cat the spam.txt