Re: Sender address rejected, but I didn't ask it to be checked.

2019-01-30 Thread paiNgoo4
You were right. There were overrides in the master.cf and I forgot to check that. And to make matters funny, the same filename was used for sender_login_maps and virtual_alias_maps. Fixed the file names and now it works. Thank you for your help -- Sent from: http://postfix.1071664.n5.nabble.com/

disable logging of header_checks FILTER action

2019-01-30 Thread Stefan Bauer
hi, smtp_header_checks = pcre:/etc/postfix/header_chk /^Subject: .*test.*/ FILTER test: Postfix then logs: Jan 30 12:44:16 mx2 postfix/cleanup[19243]: 096B95EAE2: filter: header Subject: some text test from mail-cloud-01.asdfasdf.tld[1.2.3.4];(...) How to disable logging of this events? I simp

Re: disable logging of header_checks FILTER action

2019-01-30 Thread Wietse Venema
Stefan Bauer: > hi, > > smtp_header_checks = pcre:/etc/postfix/header_chk > > /^Subject: .*test.*/ FILTER test: > > Postfix then logs: > > Jan 30 12:44:16 mx2 postfix/cleanup[19243]: 096B95EAE2: filter: header > Subject: some text test from mail-cloud-01.asdfasdf.tld[1.2.3.4];(...) > > How to

Re: disable logging of header_checks FILTER action

2019-01-30 Thread Wietse Venema
Wietse Venema: > Stefan Bauer: > > hi, > > > > smtp_header_checks = pcre:/etc/postfix/header_chk > > > > /^Subject: .*test.*/ FILTER test: > > > > Postfix then logs: > > > > Jan 30 12:44:16 mx2 postfix/cleanup[19243]: 096B95EAE2: filter: header > > Subject: some text test from mail-cloud-01.asd

Blocked by yahoo.com

2019-01-30 Thread Robert Mann
Even though this is not a postfix specific issue I was hoping someone in the community could help with this issue. We recently changed IP addresses as we purchased a /24 to use as we plan to move Internet service provides in the near future. Once we did this we now get the following from yahoo.

Re: Blocked by yahoo.com

2019-01-30 Thread Luciano Mannucci
On Wed, 30 Jan 2019 09:55:49 -0800 "Robert Mann" wrote: > Does anyone have any ideas or suggestions or even know of a service that can > help with these types of issues? You may try to check your IP address reputation. For that I usually use https://mxtoolbox.com/ which is just one of the many ar

Re: Blocked by yahoo.com

2019-01-30 Thread Paul C
mxtoolbox is a great tool to see almost all blacklists on your ips, as Luciano mentioned, but yahoo doesn't report their own blacklists so that tool can only tell you if the ips have been blacklisted in other places. TSS09 is the same as yahoo's old TS03 which is a permanent block as the message te

Re: Blocked by yahoo.com

2019-01-30 Thread Mauricio Tavares
On Wed, Jan 30, 2019 at 2:51 PM Paul C wrote: > > mxtoolbox is a great tool to see almost all blacklists on your ips, as > Luciano mentioned, but yahoo doesn't report their own blacklists so > that tool can only tell you if the ips have been blacklisted in other > places. TSS09 is the same as yaho

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Andrey Repin
Greetings, Wietse Venema! > I'm reconsidering the once-per-year schedule for stable releases. > Basically, a Postfix stable release freezes development at a point > in time, forever. Primarily, this is good for stability. > * In this day and age it seems archaic to have to wait for up to a > ye

RE: Blocked by yahoo.com

2019-01-30 Thread John Anderson
Not disputing the below information, but was curious as we have been researching DMARC is it possible (perhaps a different destination not yahoo), that it has something to do with the DMARC report showing one thing and now it shows something else. I am just getting spun up on DMARC and learning

Re: Blocked by yahoo.com

2019-01-30 Thread Phil Stracchino
On 1/30/19 3:17 PM, Mauricio Tavares wrote: > I find amusing [Yahoo] are taking this heavy handled approach with > a "we are not let the likes of you make out garden insecure, scum!" > and yet how many times they got hacked? Ah, but that's DIFFERENT... -- Phil Stracchino Babylon Commu

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Yuval Levy
Mainly, I don't want to race to get code ready for the once-per-year release, and I don't want to wait for an entire year if the code is not ready before the deadline. Release any time a sufficiently important feature is ready and do not let any schedule pressure force you to compromise on qual

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Wietse Venema
I do not care much what other projects do. Postfix has a good record for quality, stability and compatibility, and it supports four stable releases, each release receiving updates for four years. I do observe that 1) several major features were ready about 6 months after the 3.3 stable release tha

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Wietse Venema
One problem with LTS releases is that down-stream distros can end up running very old code (for example with 4-year LTS up-stream, a down-stream distro with 4-year LTS can end up running 8-year old code, which is really a pain to support on a mailing list like this one). SMTP may be an old protocol

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Patrick Ben Koetter
* Wietse Venema : > I do not care much what other projects do. Postfix has a good record > for quality, stability and compatibility, and it supports four > stable releases, each release receiving updates for four years. > > I do observe that 1) several major features were ready about 6 > months af

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Viktor Dukhovni
> On Jan 30, 2019, at 4:39 PM, Patrick Ben Koetter wrote: > > Why wait for a group of features before a release? Why not release per > feature? Because people want a reasonable period of support for released code. And we can only support a small handful of releases. So increasing the release ca

Re: Blocked by yahoo.com

2019-01-30 Thread Philip
Hi there, I had this exact issue when I first started warming up the IP I was sending my company email from.  Any email going to a Yahoo server you need to throttle heavily as if you try and send to much too quickly you will get your IP blocked.  When yahoo blocks you - because of this it tak

Re: Blocked by yahoo.com

2019-01-30 Thread @lbutlr
On 30 Jan 2019, at 16:26, Philip wrote: > had this exact issue when I first started warming up the IP I was sending my > company email from. Any email going to a Yahoo server you need to throttle > heavily as if you try and send to much too quickly you will get your IP > blocked. I "solved"

Support of "\"-like aliases feature?

2019-01-30 Thread Jeremiah Rothschild
Recently I rolled out a transition from sendmail to postfix. I've been very happy with the changes except for one feature, which was supported by sendmail but I'm not sure what to do about it in postfix. This is the use of a backslash before a username in the aliases file. A backslash inhibits fur

Re: Support of "\"-like aliases feature?

2019-01-30 Thread Wietse Venema
Jeremiah Rothschild: > Recently I rolled out a transition from sendmail to postfix. I've been very > happy with the changes except for one feature, which was supported by > sendmail but I'm not sure what to do about it in postfix. > > This is the use of a backslash before a username in the aliases

Re: Support of "\"-like aliases feature?

2019-01-30 Thread Viktor Dukhovni
On Wed, Jan 30, 2019 at 05:18:19PM -0800, Jeremiah Rothschild wrote: > Recently I rolled out a transition from sendmail to postfix. I've been very > happy with the changes except for one feature, which was supported by > sendmail but I'm not sure what to do about it in postfix. > > This is the us

Re: Rethinking the Postfix release schedule

2019-01-30 Thread Richard Damon
On 1/30/19 4:45 PM, Viktor Dukhovni wrote: >> On Jan 30, 2019, at 4:39 PM, Patrick Ben Koetter wrote: >> >> Why wait for a group of features before a release? Why not release per >> feature? > Because people want a reasonable period of support for released code. > And we can only support a small h