Re: send all local mail to single email address

Thanks Pascal- I tried using luser_relay, and it worked fine for non-existent users on the system, but for system users like 'root' I couldn't get it working. Should there be some way to make that work for all users, whether they exist (which will likely be the most common case) or not? This sys

Re: send all local mail to single email address

Pascal Volk: > On 01/16/2014 08:26 PM Michael Barrett wrote: > > Hi, I was wondering if anyone had any luck with configuring postfix to > > send all local mail, no matter to what user, to an external email address? > > ? > > Is luser_relay you >

Re: send all local mail to single email address

On 01/16/2014 08:26 PM Michael Barrett wrote: > Hi, I was wondering if anyone had any luck with configuring postfix to > send all local mail, no matter to what user, to an external email address? > … Is luser_relay you are looking for? Regards

Re: Postfix 2.11.0 stable release available

Am 16.01.2014 22:59, schrieb Viktor Dukhovni> On Thu, Jan 16, 2014 at 10:35:12PM +0100, li...@rhsoft.net wrote: > >>> There is no code in Postfix 2.11 that adds smtpd_relay_restrictions >>> to main.cf >> >> it's the same code which added the safety-net in 2.10 >> "postfix upgrade-configuration

Re: Postfix 2.11.0 stable release available

On Thu, Jan 16, 2014 at 10:35:12PM +0100, li...@rhsoft.net wrote: > > There is no code in Postfix 2.11 that adds smtpd_relay_restrictions > > to main.cf > > it's the same code which added the safety-net in 2.10 > "postfix upgrade-configuration" That "same code" is commented out in the Postfix 2.

Re: Postfix 2.11.0 stable release available

Am 16.01.2014 22:51, schrieb Wietse Venema: > li...@rhsoft.net: >>> There is no code in Postfix 2.11 that adds smtpd_relay_restrictions >>> to main.cf >> >> it's the same code which added the safety-net in 2.10 >> "postfix upgrade-configuration" > > That safety net is commented out in Postfix 2.11

Re: Postfix 2.11.0 stable release available

li...@rhsoft.net: > > There is no code in Postfix 2.11 that adds smtpd_relay_restrictions > > to main.cf > > it's the same code which added the safety-net in 2.10 > "postfix upgrade-configuration" That safety net is commented out in Postfix 2.11, as I already mentioned. It now looks like this: #

Re: insight to virtual mailbox config...i think...

On 1/16/2014 3:30 PM, rolf wrote: > On 1/16/2014 2:35 PM, Noel Jones wrote: >> On 1/16/2014 12:47 PM, rolf wrote: >>> Hi folks, >>> >>> I'm stuck...any help is appreciated. I am by no means a postfix >>> expert but I have it working fine for local accounts, trying now to >>> add an account for a d

Re: Postfix 2.11.0 stable release available

Am 16.01.2014 22:27, schrieb Wietse Venema: > li...@rhsoft.net: postfix *must not* add the second line at the end of "main.cf" if the first one already exists >>> >>> The only difference is that this Postfix version REPORTS >>> duplicate lines. It was added before Postfix 2.11.0 >> >> *

Re: insight to virtual mailbox config...i think...

On 1/16/2014 2:35 PM, Noel Jones wrote: On 1/16/2014 12:47 PM, rolf wrote: Hi folks, I'm stuck...any help is appreciated. I am by no means a postfix expert but I have it working fine for local accounts, trying now to add an account for a different domain. Apologies in advance for what will be

Re: Postfix 2.11.0 stable release available

li...@rhsoft.net: > >> postfix *must not* add the second line at the end of "main.cf" if > >> the first one already exists > > > > The only difference is that this Postfix version REPORTS > > duplicate lines. It was added before Postfix 2.11.0 > > * i see this only on one machine > * the first li

Re: Postfix 2.11.0 stable release available

Am 16.01.2014 22:04, schrieb Wietse Venema: > li...@rhsoft.net: >> well, i found a clear bug >> >> sendmail: warning: /etc/postfix/main.cf, line 160: overriding earlier entry: >> smtpd_relay_restrictions=permit_mynetworks, permit_sasl_authenticated, >> reject_unauth_destination >> __

Re: Postfix 2.11.0 stable release available

li...@rhsoft.net: > well, i found a clear bug > > sendmail: warning: /etc/postfix/main.cf, line 160: overriding earlier entry: > smtpd_relay_restrictions=permit_mynetworks, permit_sasl_authenticated, > reject_unauth_destination > __ > > cat main.cf | grep smtpd_re

Re: Postfix 2.11.0 stable release available

well, i found a clear bug sendmail: warning: /etc/postfix/main.cf, line 160: overriding earlier entry: smtpd_relay_restrictions=permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination __ cat main.cf | grep smtpd_relay_restrictions smtpd_relay_restr

Re: Possibly OT? Re: Postfix 2.11.0 stable release available

On Thu, Jan 16, 2014 at 06:40:49AM -0700, LuKreme wrote: > On 15 Jan 2014, at 22:52 , Viktor Dukhovni wrote: > > > IMPORTANT DISCLAIMER: If you want to try DANE security in the > > Postfix SMTP client, you MUST ensure that /etc/resolv.conf contains > > only "127.0.0.1" and/or "::1" as nameserver

send all local mail to single email address

Hi, I was wondering if anyone had any luck with configuring postfix to send all local mail, no matter to what user, to an external email address? Basically I'm trying to make it so that crontab error emails all go to a mailing list from a set of hosts. I know I could edit /etc/aliases for all the

Re: "Mail loops back to itself" error: figured it out

Am 16.01.2014 21:00, schrieb Security Admin (NetSec): > Brain fart. Forgot to modify the “/etc/postfix/transport” file with the new > domain please do *not* post HTML messages to mailing-lists and avoid them in general - for people like me as example which had some medical operations on both e

RE: "Mail loops back to itself" error: figured it out

Brain fart. Forgot to modify the "/etc/postfix/transport" file with the new domain. From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Security Admin (NetSec) Sent: Thursday, January 16, 2014 11:25 AM To: postfix-users@postfix.org Subject: "Mail loops ba

PATCH (was: disable tls for legacy versions)

Wietse Venema: > Matthew McGehrin: > > Is there a make flag to disable tls for legacy releases? I'm getting a > > compile error for 2.10.3 when trying to compile on FreeBSD 7.x 64bit. > > Postfix builds without TLS by default. > > On my system the command line looks like this: > > gcc -Wmissing

Re: disable tls for legacy versions

I renamed /usr/local/include/tls.h and it compiled fine. No errors. Thank You. Wietse Venema wrote: Postfix builds without TLS by default. I see. The "-I. -I../../include" should be before "-I/usr/local/include". Meanwhile, can you temporarily rename /usr/local/include/tls.h? Wie

Re: insight to virtual mailbox config...i think...

On 1/16/2014 12:47 PM, rolf wrote: > Hi folks, > > I'm stuck...any help is appreciated. I am by no means a postfix > expert but I have it working fine for local accounts, trying now to > add an account for a different domain. Apologies in advance for > what will be a lengthy email, I am trying t

Re: disable tls for legacy versions

Matthew McGehrin: > Is there a make flag to disable tls for legacy releases? I'm getting a > compile error for 2.10.3 when trying to compile on FreeBSD 7.x 64bit. Postfix builds without TLS by default. On my system the command line looks like this: gcc -Wmissing-prototypes -Wformat -Wno-comment

Re: "Mail loops back to itself" error

On 1/16/2014 1:24 PM, Security Admin (NetSec) wrote: > I recently added a new domain to my postfix mail gateway. I use the > “relay_domains = newdomain, domain2, …” in “main.cf” to add accepted > domains. > > > > I also updated my “relay_recipients” file with the following line: > > > >

"Mail loops back to itself" error

I recently added a new domain to my postfix mail gateway. I use the "relay_domains = newdomain, domain2, ..." in "main.cf" to add accepted domains. I also updated my "relay_recipients" file with the following line: "@newdomain.com x OK" All of my other domains s

disable tls for legacy versions

Is there a make flag to disable tls for legacy releases? I'm getting a compile error for 2.10.3 when trying to compile on FreeBSD 7.x 64bit. In file included from tls_level.c:52: /usr/local/include/tls.h:23:53: error: tcl.h: No such file or directory In file included from tls_level.c:52: /usr/lo

insight to virtual mailbox config...i think...

Hi folks, I'm stuck...any help is appreciated. I am by no means a postfix expert but I have it working fine for local accounts, trying now to add an account for a different domain. Apologies in advance for what will be a lengthy email, I am trying to include sufficient debugging information.

Re: unknown_address_reject_code = 550 working random?

2014/1/16 Wietse Venema > > A lookup error means that there is no reply - the requestor does > not know whether the requested domain exists. This is not to > be confused with a reply that says the domain does not exist. > > Wietse > Ok... I get my error: postfix replies with "Domain not

Re: Rejecting via header_checks

Hello, >> postfix/cleanup[15798]: AE60A602E4: reject: header From: "American >> Express" from unknown[83.217.119.xx]; >> from= to= proto=ESMTP >> helo=<[83.217.119.xx]>: 5.7.1 aexp is a spamdomain. > >> Shouldn't the 5.7.1 be prefixed by a 550? Or, does postfix do this and >> it is not logged? >

Re: unknown_address_reject_code = 550 working random?

Andrea: > 2014/1/16 Wietse Venema > > > Andrea: > > > Anyone knows why this happens? > > > How can I force to have always 550 for inexistent domain on sender > > address? > > > > Postfix will ALWAYS reply 450 after TEMPORARY lookup error. > > Doing otherwise would be a mistake. A lookup error me

Re: unknown_address_reject_code = 550 working random?

2014/1/16 Wietse Venema > Andrea: > > Anyone knows why this happens? > > How can I force to have always 550 for inexistent domain on sender > address? > > Postfix will ALWAYS reply 450 after TEMPORARY lookup error. > Doing otherwise would be a mistake. > > Wietse > You mean that after I

Re: Rejecting via header_checks

Mark: > Hello everyone, > > Using postfix 2.10.2, I have the following entry in headers_check: > > /From:.*aexp\.com/ REJECT aexp.com domain denied due to frequent spam > > I see that it works, but I am unsure about what I see in my logs: > > postfix/cleanup[15798]: AE60A602E4: reject: header

Re: unknown_address_reject_code = 550 working random?

Andrea: > Anyone knows why this happens? > How can I force to have always 550 for inexistent domain on sender address? Postfix will ALWAYS reply 450 after TEMPORARY lookup error. Doing otherwise would be a mistake. Wietse

Re: unknown_address_reject_code = 550 working random?

On 1/16/2014 10:36 AM, Andrea wrote: > Hello, > here I have a strange behaviour from postfix. > > I had many mails "rejected" with a 450 code for "Sender address > rejected: Domain not found", and wanted to change them to a 550 code > to avoid queue on the previous mta. > > So I added the row: >

unknown_address_reject_code = 550 working random?

Hello, here I have a strange behaviour from postfix. I had many mails "rejected" with a 450 code for "Sender address rejected: Domain not found", and wanted to change them to a 550 code to avoid queue on the previous mta. So I added the row: unknown_address_reject_code = 550 on main.cf and restar

Rejecting via header_checks

Hello everyone, Using postfix 2.10.2, I have the following entry in headers_check: /From:.*aexp\.com/ REJECT aexp.com domain denied due to frequent spam I see that it works, but I am unsure about what I see in my logs: postfix/cleanup[15798]: AE60A602E4: reject: header From: "American Express

Re: Current Postfix under Debian

On 01/16/2014 09:42 AM, Sebastian Wiesinger wrote: > * Robert Schetterer [2014-01-16 12:42]: >> Am 16.01.2014 12:13, schrieb Sebastian Wiesinger: >>> Hello, >>> >>> currently I'm running the distributed postfix version under Debian >>> Stable (currently 2.9.6-2). I would like to switch to the curr

Postfix legacy releases 2.10.3, 2.9.9, 2.8.17, and 2.7.16

[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-2.10.3.html] Postfix legacy releases 2.10.3, 2.9.9, 2.8.17, and 2.7.16 are available. They contain fixes and workarounds that are also part of Postfix 2.11. This is the final update for Postf

Re: How enable notification for incoming mail bounce on zimbra (postfix) server

On 1/16/2014 7:28 AM, Premjith R wrote: > Hello Postfix User List, > > MX record for our domain points to dyndns.com, where upto 50 MB > messages are received. From dyndns setup is to push mails to a > zimbra (postfix) server inside the corporate firewall, where in > message limit is set to 5MB. >

Possibly OT? Re: Postfix 2.11.0 stable release available

On 15 Jan 2014, at 22:52 , Viktor Dukhovni wrote: > IMPORTANT DISCLAIMER: If you want to try DANE security in the > Postfix SMTP client, you MUST ensure that /etc/resolv.conf contains > only "127.0.0.1" and/or "::1" as nameserver entries. Is this normal? I was told, back in the previous millenni

Re: How enable notification for incoming mail bounce on zimbra (postfix) server

Am 16.01.2014 14:28, schrieb Premjith R: > Hello Postfix User List, > > MX record for our domain points to dyndns.com, where upto 50 MB messages are > received. From dyndns setup is to push > mails to a zimbra (postfix) server inside the corporate firewall, where in > message limit is set to 5

How enable notification for incoming mail bounce on zimbra (postfix) server

Hello Postfix User List, MX record for our domain points to dyndns.com, where upto 50 MB messages are received. From dyndns setup is to push mails to a zimbra (postfix) server inside the corporate firewall, where in message limit is set to 5MB. When incoming messages are more than 5MB, we are

Re: Current Postfix under Debian

* Robert Schetterer [2014-01-16 12:42]: > Am 16.01.2014 12:13, schrieb Sebastian Wiesinger: > > Hello, > > > > currently I'm running the distributed postfix version under Debian > > Stable (currently 2.9.6-2). I would like to switch to the current 2.11 > > version to try out DANE and other new fe

RE: Message Bounced for Domain with no A record

> -Original Message- > From: owner-postfix-us...@postfix.org [mailto:owner-postfix- > us...@postfix.org] On Behalf Of martijn.list > Sent: 16 January 2014 12:17 > To: postfix-users@postfix.org > Subject: Re: Message Bounced for Domain with no A record > > On 01/16/2014 12:52 PM, James Day

Re: Message Bounced for Domain with no A record

On 01/16/2014 12:52 PM, James Day wrote: > Hello Postfix User List, > > I have a mail server that I use to provide a smart host service for my > customers. I have a problem sending a message onto a recipient in the domain > cbhc.uk.com. The failure message is below. > > I'm struggling to work o

Re: Message Bounced for Domain with no A record

Am 16.01.2014 13:13, schrieb k...@jromiak.com.ar: > El 16/01/2014 08:52 a.m., James Day escribió: >> Hello Postfix User List, >> >> I'm struggling to work out why postfix is unable to forward >> this message when there is a valid MX record. > > It is *not* Postfix problem, but solely DNS problem.

Re: Message Bounced for Domain with no A record

El 16/01/2014 08:52 a.m., James Day escribió: Hello Postfix User List, I'm struggling to work out why postfix is unable to forward > this message when there is a valid MX record. It is *not* Postfix problem, but solely DNS problem. cbhc.uk.com uses 2 DNS servers: NS1.NSNOC.COM and NS2.NSNOC.C

Message Bounced for Domain with no A record

Hello Postfix User List, I have a mail server that I use to provide a smart host service for my customers. I have a problem sending a message onto a recipient in the domain cbhc.uk.com. The failure message is below. I'm struggling to work out why postfix is unable to forward this message when

Re: Current Postfix under Debian

Am 16.01.2014 12:13, schrieb Sebastian Wiesinger: > Hello, > > currently I'm running the distributed postfix version under Debian > Stable (currently 2.9.6-2). I would like to switch to the current 2.11 > version to try out DANE and other new features. > > Has anyone got the current version packa

Current Postfix under Debian

Hello, currently I'm running the distributed postfix version under Debian Stable (currently 2.9.6-2). I would like to switch to the current 2.11 version to try out DANE and other new features. Has anyone got the current version packaged for Debian Stable (I was unable to find one online) or does