Dan,
> Thanks for the reply. No, luser skywalker doesn't need to see any
> mail messages. I don't want to violate any RFC's, but all I need to do
> is send incoming mail to the bit bucket. I don't need to bounce
anything
> back to a user. Since I am hosting these domains, I am assuming that I
can
> as you say, accept then trash it so that I am not flagged.
> What makes this complicated is that I have a user outside of my local
> workgroup who is wanting to send out emails with marketing software
> hosted elsewhere. This software will generate gazillions of replies
back to
> email@hidden, etc etc. I want to take EVERYTHING for the ENTIRE
> DOMAIN out of the equation, and send it to hell. No one cares
> about the content of these mails. It is preferable in this case, to our
> organization, to forward everything to /dev/null than it is to let
> some of them 'bounce'. We do not want to manage bouncing, as well as
support
> calls and emails regarding this which will come in through other ways.
> This is not my ideal scenario but one I have to live with at this
> point.
>
> And yes, I am indeed RTFM in /etc/aliases, but I am still wondering a
> little bit about how to accomplish this. Is alias also a daemon which I
need to kick off?
> I don't quite know enough about how mail traffic is routed on the
internet to fully understand some of
> this. I believe since we host the domain (site.com), the traffic
> will hit our server first (basically any-mail-address @site.com).
>
> And yes, before you tell me, I realize that this is probably not an
> ideal setup - ideal would be to run this software HERE where the mails
> are sent. All of this is just so that the software won't do any weird
> looping or have other miscellaneous problems, when he sends out 100,000
emails at a time, for example.
>
> Also I have put in a request for us to get a full fledged mail
> server and not just do forwarding, since if we had a dedicated mail
server I
> could just create those accounts and forward them to whereever. These
> addresses are not actual user accounts; at this point we are just
strictly
> forwarding; hence wanting to just forward everything from a particular
domain
> to the trash heap.
>
>
>
>
>
>
>
> Thanks,
>
> Marc
Dan Shoop <email@hidden>
10/01/07 11:41 AM
To: Marc L Maxwell <email@hidden>, Macos X-Server
<email@hidden>
cc:
Subject: Re: email forwarding
On Oct 1, 2007, at 9:24 AM, Marc L Maxwell wrote:
>
> Alex, thanks for the response. I am hosting a number of sites
> here. I
> want to take everything such as for example, site1.com and site2.com.
> Every email that gets sent to them for any reason
> (email@hidden,
> email@hidden - whatever) needs to go to the proverbial trash
> compactor
> with no one but Luke Skywalker to ever see it again.
This is confusing. Does luser skywalker need to see this or not?
> This applies to anything and everything incoming, based on the domain
> extension @site1.com so to speak.
This violates RFCs and will get site1.com blacklisted on many lists
as being RFC ignorant.
You must accept postmaster [and abuse]. Technically you're accepting
and just trashing it, but...
> I don't want to fill up a spot on the system with files. It looks
> like I
> was on the right path, /dev/null appears to be where I would send
> it to.
Then Luke will not be able to see these again.
> So how do I do this? Just vi /etc/aliases and put in an entry such as
>
>
>
> @site1.com /dev/null
> @site2.com /dev/null
>
> ???
RTFM the /etc/aliases file where it discusses the alias file format.
...and run newaliases
However if you don't want any mail for a zone/domain/host why are you
bothering accepting it in the first place??? The more proper thing to
do would be to just not accept it and bounce it. Accepting the mail
infers delivery for many people. Not to mention if you scan for
viruses or spam you'll be wasting a lot of cycles. So why not just
remove these from 'mydestination' in main.cf or in ServerAdmin???
-dhan
------------------------------------------------------------------------
Dan Shoop <email@hidden>
Tactical Operations Center: 1.866.901.8787 (24x7)
Ph: 714.363.1174
AIM: iWiring
Dan,
> Thanks for the reply. No, luser skywalker doesn't need to see
any
> mail messages. I don't want to violate any RFC's, but all I need
to do
> is send incoming mail to the bit bucket. I don't need to bounce
anything
> back to a user. Since I am hosting these domains, I am assuming
that I can
> as you say, accept then trash it so that I am not flagged.
> What makes this complicated is that I have a user outside of my
local
> workgroup who is wanting to send out emails with marketing
software
> hosted elsewhere. This software will generate gazillions of
replies back to
> email@hidden, etc etc. I want to take EVERYTHING for the
ENTIRE
> DOMAIN out of the equation, and send it to hell. No one cares
> about the content of these mails. It is preferable in this case,
to our
> organization, to forward everything to /dev/null than it is to
let
> some of them 'bounce'. We do not want to manage bouncing, as
well as support
> calls and emails regarding this which will come in through other
ways.
> This is not my ideal scenario but one I have to live with at this
> point.
>
> And yes, I am indeed RTFM in /etc/aliases, but I am still
wondering
> little bit about how to accomplish this. Is alias also a daemon
which I need to kick off?
> I don't quite know enough about how mail traffic is routed on the
internet to fully understand some of
> this. I believe since we host the domain (site.com), the traffic
> will hit our server first (basically any-mail-address @site.com).
>
> And yes, before you tell me, I realize that this is probably not
an
> ideal setup - ideal would be to run this software HERE where the
mails
> are sent. All of this is just so that the software won't do any
weird
> looping or have other miscellaneous problems, when he sends out
100,000 emails at a time, for example.
>
> Also I have put in a request for us to get a full fledged mail
> server and not just do forwarding, since if we had a dedicated
mail server I
> could just create those accounts and forward them to whereever.
These
> addresses are not actual user accounts; at this point we are just
strictly
> forwarding; hence wanting to just forward everything from a
particular domain
> to the trash heap.
>
>
>
>
>
>
>
> Thanks,
>
> Marc
|+--------------------+--------------------------------------------------|
|| Dan Shoop | |
|| <email@hidden| To: Marc L Maxwell |
|| t> | <email@hidden>, Macos X-Server |
|| | <email@hidden> |
|| 10/01/07 11:41 AM| cc: |
|| | Subject: Re: email forwarding |
|+--------------------+--------------------------------------------------|
On Oct 1, 2007, at 9:24 AM, Marc L Maxwell wrote:
>
> Alex, thanks for the response. I am hosting a number of sites
> here. I
> want to take everything such as for example, site1.com and
site2.com.
> Every email that gets sent to them for any reason
> (email@hidden,
> email@hidden - whatever) needs to go to the proverbial trash
> compactor
> with no one but Luke Skywalker to ever see it again.
This is confusing. Does luser skywalker need to see this or not?
> This applies to anything and everything incoming, based on the
domain
> extension @site1.com so to speak.
This violates RFCs and will get site1.com blacklisted on many lists
as being RFC ignorant.
You must accept postmaster [and abuse]. Technically you're
accepting
and just trashing it, but...
> I don't want to fill up a spot on the system with files. It
looks
> like I
> was on the right path, /dev/null appears to be where I would send
> it to.
Then Luke will not be able to see these again.
> So how do I do this? Just vi /etc/aliases and put in an entry
such as
>
>
>
> @site1.com /dev/null
> @site2.com /dev/null
>
> ???
RTFM the /etc/aliases file where it discusses the alias file
format.
...and run newaliases
However if you don't want any mail for a zone/domain/host why are
you
bothering accepting it in the first place??? The more proper thing
to
do would be to just not accept it and bounce it. Accepting the mail
infers delivery for many people. Not to mention if you scan for
viruses or spam you'll be wasting a lot of cycles. So why not just
remove these from 'mydestination' in main.cf or in ServerAdmin???
-dhan
------------------------------------------------------------------------
Dan Shoop <email@hidden>
Tactical Operations Center: 1.866.901.8787 (24x7)
Ph: 714.363.1174
AIM: iWiring
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
