Page 1 of 1

Disable mail sending

Posted: Fri Jul 06, 2012 12:09 pm
by rmizzi
Hello,

A bit of a strange question considering that the whole reason behind OpenEmm is that of mail sending ... but, I am using OpenEMM as a test bed for a research project I'm carrying out and do not really need to have the 'sendmail' functionality enabled. OpenEMM is running on a university workstation and it's not ideal to have mails being sent out everytime i run my tests ..

what would i need to do to disable the actual 'mail sending'? It's important for me to have the generation of the mails functional (I definitely need to have xmlback running) but I then want the process to stop there.

Would not running 'pickdist' solve the problem or would that mean that 'xmlback' then doesn't run?

any tips would be appreciated!

Thanks
Ruth

Re: Disable mail sending

Posted: Sun Jul 08, 2012 12:31 pm
by Anton
Maybe something like
http://serverfault.com/questions/239441 ... o-dev-null?
(the last post).

Re: Disable mail sending

Posted: Tue Jul 10, 2012 10:27 am
by rmizzi
Thanks for your reply Anton. I'm not entirely sure disabling sendmail will work though since, from what I've understood, when sendmail is not found an SMTP emulation provided by OpenEmm will kick in .. I'm not entirely sure I understood this well though.

I think i'll move this question to the Developer section of the forum maybe it's more 'code-related'. I'm curious to know what the repurcussions are of completely disabling the startup of 'pickdist.py' at startup. If it just means mails are not sent out then that is great for me.
The thing is that i'd be happy to stay commenting out lines and testing but my PC keeps getting blocked by IT administration as soon as it sends out emails and it's a hassle to get it unblocked every time ... :(

Thanks anyway!

Re: Disable mail sending

Posted: Tue Jul 10, 2012 10:35 pm
by Anton
I was suggesting the last comment :

The following sends everything to /dev/null:

LOCAL_RULE_0
R$* < @ $* > $* $#local $: bit-bucket
This assumes that in your /etc/aliases:

bit-bucket: /dev/null

Which should just accept the emails and send them to /dev/null. I really know nothing about sendmail, but I wouldn't be surprised if this was just considered normal delivery, and so it would even correctly write accounting files, etc. Maybe not, though I would say it's worth a try!