search for: relay_recipient

I have csvde dump from active directory I process on my postfix mta. It takes output like this: "CN=Curtis xxx,OU=Domain Users,OU=xxx xxx,DC=xxx-xxx,DC=local",X400:c=US\;a= \;p=xxx xxx xxx\;o=Exchange\;s=xxx\;g=xxx\;;SMTP:Cxxx at xxx-xxx.com and should return a relay_recipient map in the form of: Cxxx at xxx-xxx.com OK The command I am using is: cat $1 | tr -d \" | tr , \\n| tr \; \\n | awk -F\: '/(SMTP|smtp):/ {printf("%s\tOK\n",$2)}' Everything up to the awk is working, it drops the smtp: but its putting OK's all over the darn place. An...

...sn't know legitimate addresses of primary MX? > > I know about postfix. And all my servers are based on postfix. And even in > the most trivial configuration of secondary MX based on postfix secondary > MX _does_ have to have all legitimate addressed of primary MX. These are > in relay_recipients table. Any address that is not in that table, will not > be accepted by secondary MX. Postfix even in the most trivial > configuration is sane and does not "accept everything". > > So, what is the secondary MX server that you are describing that "accepts > everything&...

Les Mikesell wrote: > On Fri, Feb 13, 2015 at 11:39 AM, Valeri Galtsev > <galtsev at kicp.uchicago.edu> wrote: >>> Otherwise it accept junk that your primary rejects >> Not exactly. If greylisting on primary is set, but on backup MX is not, >> still what is killed by greylisting by primary MX, almost never will come >> through backup MX. This is due to the

...primary MX? >> >> I know about postfix. And all my servers are based on postfix. And even >> in >> the most trivial configuration of secondary MX based on postfix >> secondary >> MX _does_ have to have all legitimate addressed of primary MX. These are >> in relay_recipients table. Any address that is not in that table, will >> not >> be accepted by secondary MX. Postfix even in the most trivial >> configuration is sane and does not "accept everything". >> >> So, what is the secondary MX server that you are describing that >&...

...you say secondary MX doesn't know legitimate addresses of primary MX? I know about postfix. And all my servers are based on postfix. And even in the most trivial configuration of secondary MX based on postfix secondary MX _does_ have to have all legitimate addressed of primary MX. These are in relay_recipients table. Any address that is not in that table, will not be accepted by secondary MX. Postfix even in the most trivial configuration is sane and does not "accept everything". So, what is the secondary MX server that you are describing that "accepts everything" is based on? Vale...

Hi All, I'm just wanting to check that my understanding of the settings is correct as my web searches are finding a lot of dated information. If I want a Centos 6 sendmail system act as the secondary MX for domain bbbbb.co.uk do I just add a Connect:bbbbb.co.uk RELAY statement into /etc/mail/access and restart sendmail Obviously I have the DNS MX records for the domain are

...ul behavior to accept something which later you discover you can not deliver. I would call it bad MX setup, as you are making yourself potential source of backscatter (which though is not as much exploited yet as open relays, but still is bad setup). If you set backup MX based on postfix, there is relay_recipients you have to specify, which lists all e-mail addresses that are legitimate on primary MX. Nothing else is being accepted by default, thus secondary MX does not become a source of backscatter. <rant> I've seen at least at some point that google mail accepts everything. Then, (after they p...