- Original Message -
From: "Ernie Regaspi"
To:
Sent: Friday, May 15, 2009 2:03 AM
Subject: [qmailtoaster] Deleted email accounts.
Hi,
Is there a logs in qmail where I can trace deleted email accounts?
Thanks
--
Ernie P. Regaspi
System Engineer
Technical Support Center
MICROGENES
Hi,
Is there a logs in qmail where I can trace deleted email accounts?
Thanks
--
Ernie P. Regaspi
System Engineer
Technical Support Center
MICROGENESIS BUSINESS SYSTEMS
2nd Floor Alegria Bldg., Annex
2229 Chino Roces Ave., Makati City
Tel. : +632.8930584 Ext. 204
Fax : +632.892.6710
Cel : +632.
There are new versions of the Qmailtoaster packages on the main site.
Here are the release notes:
Updated all the QMT packages to add Fedora 9 x86_64 and Fedora 10 x86_64
support
Updated simscan to version 1.4.0, thanks to Steve Huff for the testing
and the modified spec file
Qmailadmin was
I think you are going to have to put a firewall/logger infront of your local
network or infront of your mail server and capture packets. Qmail Tap does
not handle bcc. It just provides a copy of the message as you would see it
if you opened it and looked at the headers. BCC is protected and n
If you can't get an answer here's a solution, not exactly the answer you were
looking for tho. Check /var/log/qmail/send and match the outgoing email
addresses against those already logged. If you find some that are included in
the log but not the outgoing messages, there's your possible leak.
Great!! thanks Nigel and Eric
-Original Message-
From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert
Sent: miƩrcoles, 13 de mayo de 2009 10:32 a.m.
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] sorry, can't find a valid MX for rcpt domain
I should have re
I have a requirement to tap all out going messages for domain and I have
qmail tap setup and working for a few email ids.
But it does not show the bcc email address for messages which are being
archived.
There is a serious info leak thru emails and I was trying to find the user
who sends it an
I should have read this before replying. :(
Nice explaination, Nigel.
Nigel Reed wrote:
Comment out 200.12.224.5 and see if that works. It doesn't look like it's
forwarding the request to get the MX.
The first look up through that server just says no answer and tells you where
to find an auth
First, it's a good idea to run caching-nameserver on a QMT host. It will
reduce network traffic somewhat, and eliminate your dependency on your
ISP's DNS resolver for name resolution. That's not a requirement though.
The nameserver at 200.12.224.5 is not providing recursion:
shu...@edwin:~$ dig