Re: Allowing alert messages from home server {Sender address rejected: Domain not found)

2014-07-24 Thread Nicolás
El 25/07/2014 3:45, Ian Evans escribió: I'm currently running postfix in two places. I have a fully functioning postfix email server for my site's domain and at home I have postfix installed to allow my home server to send alert messages. The home server is relaying through my home ISP's smtp

Re: Allowing alert messages from home server {Sender address rejected: Domain not found)

2014-07-24 Thread Edgar Pettijohn
http://www.postfix.org/cidr_table.5.html On 07/24/2014 09:45 PM, Ian Evans wrote: > I'm currently running postfix in two places. I have a fully > functioning postfix email server for my site's domain and at home I > have postfix installed to allow my home server to send alert messages. > > The ho

Re: access maps for smtpd_client_event_limit_exceptions

2014-07-24 Thread Will Yardley
On Mon, Jul 21, 2014 at 04:42:57PM -0500, Noel Jones wrote: > This isn't an access map, and doesn't have the network notation > searches built into access maps. See the docs on mynetworks for the > syntax supported here: > http://www.postfix.org/postconf.5.html#mynetworks > > It might be easiest t

Re: restriction classes

2014-07-24 Thread Will Yardley
On Wed, Jul 23, 2014 at 10:51:41AM -0500, Noel Jones wrote: > > and then have > > recommended = > > Yes, that should work as expected. This seemed to work as expected in my tests on 2.6.x. However, on 2.3.3, I get: postfix/smtpd[5673]: fatal: restriction class `recommended' needs a definition

Allowing alert messages from home server {Sender address rejected: Domain not found)

2014-07-24 Thread Ian Evans
I'm currently running postfix in two places. I have a fully functioning postfix email server for my site's domain and at home I have postfix installed to allow my home server to send alert messages. The home server is relaying through my home ISP's smtp server, but the messages get rejected by my

Perl script using sendmail to forward spam reports

2014-07-24 Thread Chris
This is a stand-alone system. I'm using postfix to forward to myself outputs of various cron-jobs and reporting spam to s...@uce.gov. I have postfix up and running on this new box as it was before the crash a couple of weeks ago and the cronjob reports are coming in correctly. This script is called

Re: restriction classes

2014-07-24 Thread Will Yardley
Thanks so much for the helpful response - just wanted to make sure I was heading in the right direction, and this was exactly what I needed. On Wed, Jul 23, 2014 at 10:51:41AM -0500, Noel Jones wrote: > > My thought was that maybe I should do something like this instead: > > > > reject_non

Re: but 1 DISCARD

2014-07-24 Thread Viktor Dukhovni
On Thu, Jul 24, 2014 at 09:57:58AM -0400, Robert Fitzpatrick wrote: > Can anyone help me understand what happened to a message to one user when it > was sent to three? Below is the log entries I find for this message, you can > see there were three recipients, all with the note of 'but 1 DISCARD'

Re: but 1 DISCARD

2014-07-24 Thread li...@rhsoft.net
Am 24.07.2014 15:57, schrieb Robert Fitzpatrick: > Can anyone help me understand what happened to a message to one user when it > was sent to three? Below is the log > entries I find for this message, you can see there were three recipients, all > with the note of 'but 1 DISCARD' that > I've ne

but 1 DISCARD

2014-07-24 Thread Robert Fitzpatrick
Can anyone help me understand what happened to a message to one user when it was sent to three? Below is the log entries I find for this message, you can see there were three recipients, all with the note of 'but 1 DISCARD' that I've never encountered before when handed off to Maia for filterin

Re: Postfix Performance on Mac OS X

2014-07-24 Thread DTNX Postmaster
On 24 Jul 2014, at 06:37, McKinnon Chris wrote: > I checked for “connect from unknown” errors coming from the client IPs in > mail.log and I’m not seeing any. The only warning I see for one client is: > > Jul 23 19:21:54 ravenviewhomes.com postfix/smtpd[61133]: warning: > fqdn_hidden[ip_hidde