[BlueOnyx:08889] Re: forward email to /dev/null?

[Roy Urick]

/Thats the problem. We use a Barracuda and it throws away emails from 
non-existent mailboxes.

I also considered lumping them all under a d0_not_reply address, but 
alas: our copiers email us to say we need to feed them (order more 
toner) and when somebody screws up we need to know where it came from.

I look forward to Michael's tweak to add a check box to the GUI to black 
hole email. (although some days I might be tempted to use it on my own 
mailbox)



/On 10/20/2011 1:18 PM, Hans Draaisma - Netvictory B.V. wrote:
> Another approach but maybe not what you are looking for...
>
> The copier or printer only has to sent-out mail and mail going to it's "from" address needs to be discarded right?
>
> Why then just not give the printer or other device an e-mailadress that is not there (configured in the BO interface) in the first place. (printer01 at domainname.com or whatever)
> If your BO server also is the SMTP server for the device than this is somewhat tricky because it will check originating e-mailadress under a domain that it's running locally.
>
>
> regards,
>
> Hans Draaisma
> Netvictory B.V.
>
> On 20 okt 2011, at 18:50, Dan Porter wrote:
>
>> Would it be possible to use the GUI and just forward all mail for the user to "nobody"  rather than going into the virtusertable?
>>
>>
>> ---------- Original Message -----------
>> From: Michael Stauber<mstauber at blueonyx.it>
>> To: BlueOnyx General Mailing List<blueonyx at mail.blueonyx.it>
>> Sent: Thu, 20 Oct 2011 17:51:59 +0200
>> Subject: [BlueOnyx:08875] Re: forward email to /dev/null?
>>
>>> Hi Roy,
>>>
>>>> How can we setup those mailboxes to dump any inbound email so we aren’t
>>>> cleaning out the mailbox periodically due to rejections, etc.?
>>> Edit /etc/mail/virtusertable and find all aliasses related to that mailbox.
>>>
>>> An example could look like this:
>>>
>>> mstauber at 5107rmail.smd.net      mstauber
>>>
>>> You could handle the situation in two possible ways by changing the username
>>> part:
>>>
>>> Method a):
>>> mstauber at 5107rmail.smd.net      nobody
>>>
>>> Method b):
>>> mstauber at 5107rmail.smd.net      error:nouser No such user here
>>>
>>> Changing the username to "nobody" will accept the emails to the email address
>>> in question. But in /etc/mail/aliasses "nobody" is mapped to /dev/null. So the
>>> email will then be silently discarded.
>>>
>>> Changing the username to "error:nouser No such user here"  will instead refuse
>>> to accept the email and the sender gets an error message, telling him "No such
>>> user here". You could change the "No such user here" to something else, but it
>>> should be a really, really brief description without much in the way of using
>>> any non-alphabetical characters.
>>>
>>> Once you have edited /etc/mail/virtusertable run these two commands:
>>>
>>> makemap hash /etc/mail/virtusertable.db<  /etc/mail/virtusertable
>>> /etc/init.d/sendmail restart
>>>
>>> But be prepared that these changes are not permanent. If you use the GUI to
>>> update these VSites email settings, or if you use the GUI to edit this users
>>> email details, then these changes will get reverted back to what they were
>>> before.
>>>
>>> -- 
>>> With best regards
>>>
>>> Michael Stauber
>>>
>>> _______________________________________________
>>> Blueonyx mailing list
>>> Blueonyx at mail.blueonyx.it
>>> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>> ------- End of Original Message -------
>> _______________________________________________
>> Blueonyx mailing list
>> Blueonyx at mail.blueonyx.it
>> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20111020/965bd88a/attachment.html>