I don't see anything "wrong". The default for .pcre is case independence.
I use "REJECT Spam not allowed." instead of DISCARD.
You're not escaping your period (\.com).
You can combine some of these into a single rule:
/mediablueinc\.(cf|com|ga)$/REJECT Spam not allowed (1).
/\.(top|ninja|d
I have a check_sender_access to weed out spam from spam domains.
The check_sender_access is a pcre: list.
And the pcre list is:
/mediablueinc.cf$/i DISCARD
/mediablueinc.com$/i DISCARD
/mediablueinc.ga$/i DISCARD
/abstreeltg.eu$/i DISCARD
/\.top$/i DISCARD
(Yeah, the .top domain
Dirk Stöcker wrote on 12/12/2015 13:26:
And SMTP has the big advantage, that you can define the name of the host in MX,
so the name of the mail server can be independent from the domain of the email
address.
I use this method.
Just one cert to manage/renew and no exotic configuration. KISS pr
On Sat, Dec 12, 2015 at 06:42:03AM -0800, Alice Wonder wrote:
> I do not want SNI to die but IMHO SNI is not for mail servers.
On Sat, Dec 12, 2015 at 01:26:06PM +0100, Dirk Stöcker wrote:
> And SMTP has the big advantage, that you can define the name of the host in
> MX, so the name of the mail
On 12/12/2015 04:26 AM, Dirk Stöcker wrote:
On Fri, 11 Dec 2015, Viktor Dukhovni wrote:
Over the years there have from time to time been requests for
server-side SNI support in Postfix, but most users have found
workable alternatives, such as above.
A key reason that SNI support is not there
On Fri, 11 Dec 2015, Viktor Dukhovni wrote:
Over the years there have from time to time been requests for
server-side SNI support in Postfix, but most users have found
workable alternatives, such as above.
A key reason that SNI support is not there yet, is that we like to
do things right(TM) in
