Topic: Saving a copy of all outgoing e-mail

[Kelvin]

If you had a look at the qmail web site, it clearly mentions that if you wish to distribute modified binaries, you could ask permission from Dan, the author. As the change we are after is clearly outlined in qmail's own FAQ, I don't see why Dan would not allow it. So, we could ask permission, although it would sound a lot better coming from Mitel. Of course, if Mitel does not deem this important enough, then they won't bother.

Kelvin

[Charlie Brady]

Kelvin wrote:

> As the change we are
> after is clearly outlined in qmail's own FAQ, I don't see why
> Dan would not allow it.

You obviously know very little about Dan Bernstein. Google will tell you more.

> So, we could ask permission...

You would be wasting your time. You are almost certain to get no reply.

Charlie

[Kelvin]

Charlie Wrote :

>You obviously know very little about Dan Bernstein. Google will tell you more.

Granted. Then again, I know very little about just about everyone at Mitel, Microsoft, Symantec, etc. yet I still choose to put faith in their products, support (if any), etc.

Anyway, from what I can tell by reading Dan's licensing as well as other discussions on the net, patching is not disalllowed and therefore if anyone out there with enough knowledge to do so should be free to distribute a patch file / program to accomplish what we want as long as the patch is applied to the original binary distribution.

Obviously, patching a patched version is asking for trouble, but as clearly implied, the qmail program distributed with SME has to be the original unmodified version. So anyone producing a patch for the qmail in the SME server should not have an issue with this (unless they have already applied some other patch !).


> You would be wasting your time. You are almost certain to get no reply.

Won't know till you try. It might take a 5 minute e-mail and if he does reply positively, this would save days, even weeks of working around the problem. Like the problem with bind in 5.1.2 I brought up a while back. If there is a simple enough way to fix the issue in an existing 5.1.2 server (in this case upgrade bind), why would you force the client to upgrade their server to a newer version (free software or otherwise, there are issues with inconvenience, downtime, etc.). Plus a risk that the new version might not work correctly on their existing hardware, etc. (been there, done that!).

Kelvin

[Luk Vermeylen]

About monitoring incoming and outgoing e-mail:
I did this yesterday and it seems to work. It even war relatively
simple.
I installed a few development packages (make, gcc,...)downloaded qmail
tarball extracted this one ,stopped the qmail service, changed the file
according qmail faq, did a make setup check, made a
/var/qmail/alias/.qmail-log file with in that one a line ./msg-log
afterwards created 2 e-mail aliasses for the user who had to receive the
monitored e-mail: log@... and alias-localdelivery-log@...

everything seems to work. The only thing I would like to change is that
the subject line in the monitored e-mails (send to log@ and
alias-localdelivery-log@ schould be modified with monitor outgoing or
incoming acoording the mail is incoming or outgoing, but found until now
no solution for this

Luk

[Arby Edi]

Luk,

What version of SME did you do this on?  I'm about to attempt this on 5.1.2 but I really don't know too much.  Anything you can do to help (step byu step instructions?) would be greatly appreciated.

[Luk Vermeylen]

Did this on a 5.5

I did it like mentionned in the faq of qmail

created 1 user acccounts (copy)
created 2 pseudonyms for 'copy' alias-localdelivery-log and log (if you
don't create them, you get undelivered mail- seems that the change in qmail
delivers the mails to them)

for qmail: http://cr.yp.to/qmail/faq/admin.html#copies

I downloaded qmail tarball, untarred it, changed the extra.h file as
mentionned, did a ./config (mentionned in the install.ctl file)
put the line ./msg-log in the /var/qmail/alias/.qmail-log file

restarted the server and it worked
I don't know if this is the exact way, but it works for me

If my guidelines are not totally correct, let me know, and i'll try to make
a howto

don't try this on a working box, do this first on a test box or a box not
yet running as production server

Luk

[Drew]

Kelvin/Luk/Nathan,

I am sending you guys an email on this topic off phorum in order to come to some form of conclusion on this whole outbound mail logging issue.

Thanks,
Drew

[ChanChong]

Sorry to write in.

But is there any conclusion upon this issue? Seems like this is the thread that is really working on this issue.

There isn't any other threads that gives this issue so much coverage. If there is, can someone also help to point me to the right direction.

Thanks.

[Kelvin]

Hi ChanChong,

Try :-

http://www.quasarsoft.com.au/howtos/html/mailcapture_howto.html

Not perfect, but see how far this gets you.

Kelvin

[Michiel]

From a posting in dev-info by Gordon Rowell:

- Install Charlie Brady's mailfront-0.86-1es2 (see his contrib area on any of the mirror servers)
- Create a mail log user (e.g. maillog)
- echo maillog > /var/service/smtpfront-qmail/env/LOG_RECIPIENT

That's all. All your incoming & outgoing mail will be copied to user maillog. With some procmail coding you can then sort the mail to different folders or exclude certain mails from being archived. A bit limited, but it works quite well.

Michiel

[Luk Vermeylen]

how to let it work in 5.6 or 6.0?
mailfront rpm is for 5.5, will it work also on 5.6 and/or 6.0?

Thanks

Luk