Re: Deliver to non-local users from domain.

On Fri, Oct 8, 2010 at 5:06 AM, Nikolai K. Bochev wrote: > Hello list, > > I have one domain , with several users in it. Most of them , will be > migrated to a exchange server, which will later be the mx record for that > domain. The exchange server will redirect emails for users not in his > data

Re: Problems getting Gmail to use my SMTP server rather than theirs

On Wed, Feb 10, 2010 at 5:54 PM, Rob Tanner wrote: > >> TLS is enabled on port 25 of our server and it has a regular Thawte > >> certificate behind it. Tests with Thunderbird using PLAIN > >> authentication (SASL method) work perfectly. From our point of view, > >> all we really want to protect

Re: connections from ipv4 localhost logged as unknown[127.0.0.1]

On Wed, Jan 13, 2010 at 3:20 PM, Tom Hendrikx wrote: > Hi, > > After setting up postfix up on a ipv4/ipv6 dualstack machine I'm seeing > the following issue: connections on 127.0.0.1 (where my content_filter > re-injects mail) are logged as: > > 010-01-13T22:51:07+01:00 meredith-vmail postfix/smt

Re: Don't filter the users\

On Tue, Nov 24, 2009 at 1:25 PM, Sahil Tandon wrote: > On Nov 24, 2009, at 3:07 PM, LuKreme wrote: > > >> On 24-Nov-2009, at 10:39, Jordi Espasa Clofent wrote: >> >> That is easy. Have your users connect to the submission port >>> >>> Yes Wietse, I've considered this simple and clean

Re: Postfix DKIM

On Wed, Sep 9, 2009 at 8:08 PM, KLaM Postmaster wrote: > I found the easiest way by far, was to use the DKIM feature of amavisd-new > simple to setup > and work like a charm. > > JLA > I couldn't tell from the docs: http://www.ijs.si/so

Re: Test e-mailservice

On Wed, Nov 11, 2009 at 1:54 AM, Martijn de Munnik wrote: > Hi, > > Of course I don't want this to happen again in the future. How do people > test their mail server periodically? So far we use webmin which tries to > connect to port 25, 110 and 143 and checks if the greeting is correct. If > one

Settings for restrictive mail server

I need some ideas for implementing this uber-restrictive mailserver at my company. Some background: CEO doesn't want to buy Exchange. We have basically 3 user groups: agents, their team leads, and corporate (execs, etc). The goal is: Execs don't want agents to e-mail each other or anyone outside