logging username

2017-01-20 Thread Kiss Gabor (Bitman)
My logs are fullfilled with this: Jan 20 20:05:26 linzer postfix/smtpd[22308]: warning: hostname c942452695-cloudp ro-214859053.cloudatcost.com does not resolve to address 167.88.40.162: Name or service not known Jan 20 20:05:26 linzer postfix/smtpd[22308]: connect from unknown[167.88.40.162] Jan

Re: Prevent Backscatter

2017-01-20 Thread Postfix User
My test procedure follows telnet domain.com 25 ehlo me mail from: rcpt to: At this point I get "Ok" message, and I can continue writing the body of the e-mail. Because account doesn't exist, Postfix sends bounce notification back to sender address. This is the output of postconf

Re: Prevent Backscatter

2017-01-20 Thread Bastian Blank
On Fri, Jan 20, 2017 at 02:01:27PM -0700, Postfix User wrote: > check_sender_access $virtual_alias_maps, You are creating an open relay, don't do that. > #smtpd_tls_auth_only = yes This is _not_ the postconf -n output we where asking for. Bastian -- Those who hate and fight must stop

Re: Prevent Backscatter

2017-01-20 Thread Noel Jones
On 1/20/2017 3:01 PM, Postfix User wrote: > Thanks for the reply, > > Just made the changes you suggested. I set relay_domains to empty, because > all domains are served by the same server. Again I sent a message to non > existing account, and I am still getting "250 2.1.5 Ok" instead of a reject

Re: Prevent Backscatter

2017-01-20 Thread Postfix User
Thanks for the reply, Just made the changes you suggested. I set relay_domains to empty, because all domains are served by the same server. Again I sent a message to non existing account, and I am still getting "250 2.1.5 Ok" instead of a reject message. This is my current main.cf smtpd_banner =

Re: Postfix instance not listening

2017-01-20 Thread Larry Stone
Mostly directed at the OP: I'm mostly a lurker here but I've learned a lot here. The tone of this list is mostly "teach a man to fish", not "give a man a fish" (from the old saying "give a man a fish and you feed him for a day; teach a man to fish and you feed him for life". To that end, answe

Re: Postfix instance not listening

2017-01-20 Thread Viktor Dukhovni
> On Jan 20, 2017, at 3:18 PM, Wietse Venema wrote: > >> Obviously, given your level of godly perfection, you've never suffered >> from "config file blindness" you know after starting a whole bunch of >> them for a while suddenly the obvious gets hidden. > > I can't speak for Viktor, but I sur

Re: Postfix instance not listening

2017-01-20 Thread Wietse Venema
Tim Smith: > Viktor, > > I'm sorry I'm obviously not as perfect as you. Sorry, I appreciate that tone matters, but we're not really hostile here. > Obviously, given your level of godly perfection, you've never suffered > from "config file blindness" you know after starting a whole bunch of > th

Re: Postfix instance not listening

2017-01-20 Thread Tim Smith
Viktor, I'm sorry I'm obviously not as perfect as you. Obviously, given your level of godly perfection, you've never suffered from "config file blindness" you know after starting a whole bunch of them for a while suddenly the obvious gets hidden. Thanks a bunch

Re: Getting smtpd restrictions right....

2017-01-20 Thread Noel Jones
You didn't answer the all-important question about what IP postfix sees for mail arriving from the Xeams server, nor did you provide the requested logging. I'll assume postfix sees the Xeams IP. That's bad; it prevents postfix from making any decisions about the source of the mail. The solution

Re: Getting smtpd restrictions right....

2017-01-20 Thread SH Development
Postfix I assumed got it’s valid users from the same place Dovecot is getting it, the mySQL database. In the postconf -n I posted, it may not have shown the mynetworks as I have gone from trying different things to leaving it at default. It was probably at default when I generated it. I have

Re: Postfix instance not listening

2017-01-20 Thread Viktor Dukhovni
> On Jan 20, 2017, at 6:29 AM, Tim Smith > wrote: > > Hi, > > I need a second pair of eyes on this. > > My postmulti instance as configured below is not listening and I can't > figure out why ! > > I've uploaded to main.cf to pastebin : > http://pastebin.com/iVJCbU6T Even a cursory look at

Re: Getting smtpd restrictions right....

2017-01-20 Thread Noel Jones
On 1/19/2017 11:49 PM, SH Development wrote: > I have a server running Xeams for spam filtering, and another server running > Postfix 2.6.6. Both servers are on the same network behind a firewall. > Haven’t had any problems until recently when Xeams tech support pointed out > that my Xeams ser

Re: Prevent Backscatter

2017-01-20 Thread Wietse Venema
Is your server MX host for domains that are delivered to a different mail server? If not: Set relay_domains to empty. If yes: DO Specify ONLY THOSE DOMAINS in relay_domains DO specify ONLY THOSE recipients in relay_recipient_maps DO NOT specify virtual (alias or mailbox) stuff in relay

Prevent Backscatter

2017-01-20 Thread Postfix User
Hello, I am trying to reject instead of sending bounce message back when email arrives to non existing account at domains hosted by my server. This is my main.cf smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc

Postfix instance not listening

2017-01-20 Thread Tim Smith
Hi, I need a second pair of eyes on this. My postmulti instance as configured below is not listening and I can't figure out why ! As you can see below, "postfix-authrelay" is active : $ sudo postmulti -l - - y /etc/postfix postfix-authrelay mta y