[nflug] Email

Pete Cummings pete at linuxcowboy.com
Thu Aug 16 08:31:19 EDT 2007


Why not put sendmail in front of the whole mess ? I know it takes some 
extra elbow grease to set up and get familiar with it, but I've never 
been at a loss for features.
Pete

eric wrote:
> Starting new sub-thread..
> Darin, can I ask, what are all the mail packages you use postfix, etc..
>
> I'd love an outline or rough draft?
>
>
>
> Darin Perusich wrote:
>> Will this machine be an MX server or will it be behind your MX and 
>> relaying from there? I'm also not understanding your SPAM tagging 
>> point. Are you concerned about your relay marking mail from the 
>> domains it's relaying for marking them as SPAM? This is easily 
>> remedied by setting the following spamassassin rule and included ALL 
>> of the relaying domains:
>>
>> header LOCAL_RCVD Received =~ /.*\(\S+\.cognigencorp\.com\s+\[.*\]\)/
>> describe LOCAL_RCVD Received from local machine
>> score LOCAL_RCVD -50
>>
>> The only way outgoing mail will be sent from a different IP is using 
>> some type of virtualization, and why doesn't this even matter? It 
>> sounds like over complicating the setup.
>>
>> You mentioned using Postfix for the MTA, a wise move IMHO ;-). Are 
>> you planning on using amavisd-new to filter, tag spam, and virus 
>> check? This is a very typical and efficient setup for relaying for 
>> multiple domains not to mention straightforward. Your setup is a 
>> little more complication then what I have setup here but it's pretty 
>> much the same. If you want more details let me know.
>>
>> Robert Meyer wrote:
>>> OK, before we get into this, remember that this is NOT my design.  
>>> I'm trying to make the best of what I have here...  Having said that...
>>>
>>> We currently have several clients, all using an Imail server 
>>> (remember, not my design) to handle Email.  We are also routing a 
>>> few Exchange servers through it.  In essence, all mail coming in for 
>>> these clients hits a single server that separates the domain names 
>>> and routes the mail to the backend servers.  We also have some 
>>> clients that are actually storing their mail on the Imail server.  
>>> These two functions are going to be separated so that the relay 
>>> server and the POP/IMAP functions are on different boxes.  The mail 
>>> servers that I relay for also relay back through the Imail server.  
>>> The problem is that if one client gets infected with a spam virus or 
>>> otherwise gets the server tagged as a spam host, it breaks all of 
>>> the clients that route through that server.  We (actually, they) 
>>> want to keep the single relay host, because it's good for 
>>> troubleshooting.  (remember, not my design)
>>>
>>> What I need to know is:  Is there any way that I can set up a system 
>>> that will relay mail from internal mail servers but have the IP 
>>> address leaving the server be different for each domain.  
>>> Essentially, I want it to look like each domain is coming from a 
>>> different server.  We are switching the relay server to CentOS (RHEL 
>>> clone) and are going to use Postfix for the relay functions.
>>>
>>> The only idea that comes to mind is to create multiple virtual 
>>> servers with VMWare and route each client through a different 
>>> virtual machine.  I know I can create multiple IP aliases on the 
>>> machine.  Can I leverage that somehow to get different source 
>>> addresses for different domains?
>>>
>>> Thanks...
>>>
>>> Cheers!
>>>
>>> Bob
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>> Moody friends. Drama queens. Your life? Nope! - their life, your story.
>>> Play Sims Stories at Yahoo! Games. 
>>> <http://us.rd.yahoo.com/evt=48224/*http://sims.yahoo.com/>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> nflug mailing list
>>> nflug at nflug.org
>>> http://www.nflug.org/mailman/listinfo/nflug
>>
>
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>



More information about the nflug mailing list