FWIW, I keep an xyz tld for test purposes. Point dot com to production and dot
xyz for test. Yes I know there are ways to do this with a subdomain, but dot
xyz is really cheap.
I never investigated if there production users of xyz.
Original Message
From: Viktor Dukhovni
Sent: Monday, Novem
On Mon, Nov 16, 2015 at 11:31:23PM -0600, Chris Boylan wrote:
> So if I build a one line /etc/postfix/access with
> .xyz REJECT
http://www.postfix.org/postconf.5.html#parent_domain_matches_subdomains
If smtpd_acces_maps is included, then the key is "xyz" not ".xyz".
You can always list both
Am 17. November 2015 06:31:23 MEZ, schrieb Chris Boylan
:
>So if I build a one line /etc/postfix/access with
>.xyz REJECT
>
>and use smtpd_sender_restrictions=check_sender_access
>
You have to add the path to the access map, e.g. you postmap the
/etc/postfix/access file and add hash:/etc/po
So if I build a one line /etc/postfix/access with
.xyzREJECT
and use smtpd_sender_restrictions=check_sender_access
That seems from the documentation like it would reject all email from .XYZ.
Is this a reasonable approach?
-Original Message-
From: owner-postfix-us...@postfix.org
> On Nov 16, 2015, at 02.53, Vicki Brown wrote:
>
> [...] discards email to non-existent recipient addresses [...]
on a side note, don't accept mail and then discard it. instead, reject it.
-ben
On Mon, Nov 16, 2015 at 10:38:07PM -0600, Chris Boylan wrote:
> I think I'd like to key off the from information and block anything, for
> example, that self-identifies as being from a sender in .xyz domain.
The ".xyz" domain is a real TLD, for a generic example use ".example"
or "example.com", .
We'd like to reject all email from some specific domains regardless of ip
address.
I think I'd like to key off the from information and block anything, for
example, that self-identifies as being from a sender in .xyz domain.
Would appreciate being pointed in the right direction as I'm just drawin
In instances like this, I often find virtual machines a big help
Sent from my iPhone
On Nov 16, 2015, at 8:37 PM, Vicki Brown wrote:
>>> To test a configuration before going live, use a test machine, or
>>
>> configure a secondary Postfix instance if your Postfix distribution
>> has not broke
On Mon, Nov 16, 2015 at 06:45:05PM -0800, Vicki Brown wrote:
> > configure a secondary Postfix instance if your Postfix distribution
> > has not broken http://www.postfix.org/MULTI_INSTANCE_README.html
>
> We're a house, not a company. We don't have "test machines"
Most laptops can run VirtualBo
>> To test a configuration before going live, use a test machine, or
>
> configure a secondary Postfix instance if your Postfix distribution
> has not broken http://www.postfix.org/MULTI_INSTANCE_README.html
We're a house, not a company. We don;t have "test machines"
>> As documented, Postfix co
On 09/11/15 16:43, L.P.H. van Belle wrote:
>
>> -Oorspronkelijk bericht-
>> Van: njo...@megan.vbhcs.org [mailto:owner-postfix-us...@postfix.org]
>> Namens Noel Jones
>> Verzonden: maandag 9 november 2015 16:05
>> Aan: postfix-users@postfix.org
>> Onderwerp: Re: Disable spooling
>>
>> On
Christian Rohmann:
> Hey postfix-users,
>
> I am afraid I have a hopefully simple configuration style question:
>
> I set up a restriction class. Every connection/sending attempt that goes
> into this somewhat trapping class via an access-map, naturally.
>
> Now I would love to log a warn or inf
Hey postfix-users,
I am afraid I have a hopefully simple configuration style question:
I set up a restriction class. Every connection/sending attempt that goes
into this somewhat trapping class via an access-map, naturally.
Now I would love to log a warn or info message to the log file whenever
Vicki Brown:
> Can I insert a content filter before a relay via virtual_alias_maps
> or relay_recipient_maps? Or are all relays done before any content
> filters could be run?
> Is there a clean way I can insert a content filter before the mail
> is relayed?
As documented, Postfix content filters
14 matches
Mail list logo
