Recording all outgoing mail to stop spam

[madcat]

Make sure the permisions on the file /var/qmail/bin/qmail-remote are the same as the orrignial file (-r-xr-xr-x) and the permisions on the /var/log/qmail-remote.log file are world writable (-rw-rw--w-). Also make sure you have the "IPC::Open2" perl module installed by running:

perl -MCPAN -e "shell"
install IPC::Open2

Good luck.

 

[rperea]

Plesk 9.0 & Postfix?

Does anybody know how to record outgoing emails with the new Postfix MTA?

I am not too familiar with Postfix but I am learning. I couldn't find any easy solution to this. The closest thing I have come up with is using the Postfix content filtering as described here.

http://www.postfix.org/FILTER_README.html

But I am still not sure how all this works. If anybody has any suggestions or ideas, I would love to hear from you.

 

[rperea]

Well, the best way that I found to do this as easy as possible is to use the always_bcc = parameter in the /etc/postfix/main.cf file. So now all email is bcc'd to the email address that you specify and you can set a cron job to parse the contents of the mail directory using a quick mod of the script posted in this topic. Just modify the script to read the mail files and then delete them instead of reading STDIN and piping the output. If there is a better way or if I am dead wrong, let me know. Also, I know that this is the 8.3 forum and not the 9.0 forum, so maybe there should be a new topic there with a link to this topic. (I am not too familiar with forum etiquette.)

 

[dragnovich]

Hello madcat

I tried all you said and worked perfectly to trace the scripts used, any way I had a question about SpamDyke. do you know (can post) a little tutorial about how to install it the web site does not have any Plesk specific installation.

Or it will work as in the install.txt file? I dont want to play with the server !

Thanks!

 

[dragnovich]

Sorry I had make a very vague question ..

I follow the instructions in the install file:

Special note for Plesk users: starting relaylock before spamdyke can cause
some (harmless) errors to be logged. If spamdyke is started before relaylock,
you shouldn't see any errors:
--------------------------------------------------------------------------------
server_args = -Rt0 /usr/local/bin/spamdyke -FLAGS /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
--------------------------------------------------------------------------------
Plesk users can also use spamdyke for their SMTPS connections by adding it to
the /etc/xinetd.d/smtps_psa file. spamdyke's configuration in that file will
need to include the options "tls-level" (set to "smtps") and
"tls-certificate-file".

It seems to me that the -FLAGS is not right... the question I try to explain was if you can help me to se WHAT OPTIONS TO USE... also it talks about a "spamdyke's configuration" file, that can be created as /etc/spamdyke.conf to handle all configurations, but does not says how to call it.

What's you actual configuration OPTIONS ? or how do you solve this step?

Regards!!

 

[Paul Maine]

Postfix bcc_maps

Does anybody know how to record outgoing emails with the new Postfix MTA?

It's incredibly simple:

In older versions of Postfix:
http://www.postfix.org/postconf.5.html#always_bcc

Postfix 2.1 and later has more granular control over individual senders and recipients (the mapping can include regular expressions):
http://www.postfix.org/postconf.5.html#sender_bcc_maps
http://www.postfix.org/postconf.5.html#recipient_bcc_maps

A practical example of bcc_maps:
http://www.arschkrebs.de/postfix/postfix_archive.shtml

Hope this helps!