Re: Split domain configuration

2015-03-26 Thread Wietse Venema
Jonathan Vaughn: > Google Apps handles our mail, and relays any non-existant accounts to our > Postfix server. This works fine, and we can then use virtual accounts on > our Postfix server to do whatever we wish. > > However, we have a problem with relaying mail from inside our LAN through > our P

Add all BCC-recipients to a header for archiving

2015-03-26 Thread André Peters
Hello, For a mail archiving solution I need to write all BCC'ed recipients to a X-header. I am looking for a better way to hide this X-header from users than ignoring it at delivery and only keep it for recipient "arch...@archive.domain.tld". So far I am doing this: /etc/postfix/main.cf

Re: Add all BCC-recipients to a header for archiving

2015-03-26 Thread Viktor Dukhovni
On Thu, Mar 26, 2015 at 05:54:21PM +0100, Andr? Peters wrote: > For a mail archiving solution I need to write all BCC'ed recipients to a > X-header. I am looking for a better way to hide this X-header from users > than ignoring it at delivery and only keep it for recipient > "arch...@archive.domai

Re: Split domain configuration

2015-03-26 Thread Jonathan Vaughn
We receive mail directly from the internet, but not for this particular domain. This postfix also handles virtual mail for domains that aren't on Google apps, this is the only time it's listed as the MX. The only time it receives mail from outside our networks on this domain is if Google Apps is r

Re: Goodbye IBM, Hello Google

2015-03-26 Thread @lbutlr
On 25 Mar 2015, at 09:49 , Jim Reid wrote: > Can y'all please stop posting messages of goodwill to the list? Just send > your best wishes direct to Wietse. There's no reason for the list to see > these. Of all the things to complain about, seriously? Ohnoes! I have a single thread of 20-ish me

Tracing why there's a NDN

2015-03-26 Thread @lbutlr
given the following logs: Mar 26 02:53:51 mail postfix/smtpd[7489]: 3lCKqM0QcJzJMnf: client=unknown[186.60.69.23] Mar 26 02:53:53 mail postfix/cleanup[7524]: 3lCKqM0QcJzJMnf: message-id= Mar 26 02:54:23 mail spamd[87999]: spamd: processing message for *localuser*.com:58 Mar 26 02:54:30 mail s

Re: Tracing why there's a NDN

2015-03-26 Thread Wolfgang Zeikat
Hi, your logs show: - On 26 Mar, 2015, at 23:44, @lbutlr krem...@kreme.com wrote: > Mar 26 02:55:38 mail postfix/smtp[7534]: 3lCKqM0QcJzJMnf: > to=<*gmailuser*@gmail.com>, orig_to=<*localuser*.com>, > relay=gmail-smtp-in.l.google.com[74.125.193.26]:25, delay=115, > delays=46/0.02/38/31, dsn=

Re: Split domain configuration

2015-03-26 Thread Wietse Venema
Jonathan Vaughn: > We receive mail directly from the internet, but not for this particular > domain. > > This postfix also handles virtual mail for domains that aren't on Google > apps, this is the only time it's listed as the MX. The only time it > receives mail from outside our networks on this

Re: Split domain configuration

2015-03-26 Thread Jonathan Vaughn
MX only points to Google on this domain that we want to set up this split domain handling. The other domains' we have configured in Postfix, their MX only point to Postfix. In all cases, MX only goes to one or the other. Google DOES accept mail for invalid recipients, and then relays them to Postf

Re: Split domain configuration

2015-03-26 Thread Jonathan Vaughn
To be clear, having the nonexistant in both systems users just disappear is fine with me. "Fixing" that is not a priority, but making the split domain setup be less of a pain to manage (having to add Google accounts in both places, with Postfix transport map set to force them to Google via MX if it

Re: Tracing why there's a NDN

2015-03-26 Thread @lbutlr
> On 26 Mar 2015, at 16:59 , Wolfgang Zeikat wrote: > > Hi, > > your logs show: > > - On 26 Mar, 2015, at 23:44, @lbutlr krem...@kreme.com wrote: > >> Mar 26 02:55:38 mail postfix/smtp[7534]: 3lCKqM0QcJzJMnf: >> to=<*gmailuser*@gmail.com>, orig_to=<*localuser*.com>, >> relay=gmail-smtp-in