On 2016-03-20 16:46, Dimitar Katerinski wrote:
@lbutlr wrote:
/etc/hosts.allow:
ALL : 185.103.253.246 : DENY
Has no effect.
hosts.allow and hosts.deny only work for programs that have been
compiled with TCP wrapper support. Typically this is limited to telnet,
ftp and inetd super daemon
Hi Wietse,
thanks a lot for the reply.
I undestand how sender login maps work as i implemented this feature
about 2 years ago and it looks to be working without issues.
By your reply should i assume it's not possible to pass extra
paramaters to the SQL query sentence?
Also, i suppose there's no
Pau Peris:
> By your reply should i assume it's not possible to pass extra
> paramaters to the SQL query sentence?
The Postfix SMTP smtpd_sender_login_maps feature makes the following
queries:
1) user@domain (complete sender address)
2) user
3) @domain
Those Postfix queries contain n
Hi,
I wonder what the Postfix community thinks or plans to do according to
this standard that is being written:
https://datatracker.ietf.org/doc/draft-margolis-smtp-sts/?include_text=1
I personally find this quite interesting. What I wonder is, if maybe
we have now reached a similar point of comp
David Schweikert:
> Hi,
>
> I wonder what the Postfix community thinks or plans to do according to
> this standard that is being written:
> https://datatracker.ietf.org/doc/draft-margolis-smtp-sts/?include_text=1
>
> I personally find this quite interesting. What I wonder is, if maybe
> we have n
Hi Wietse,
thanks a lot for your replies.
I've integrated a custom vacation script (similar to the famous
vacation.pl which comes with postfixadmin). So users can enable
vacation/atoreply in roundcube for example, once they check
vacation/autoreply an new alias is created inside aliases with a
sp
> On Mar 21, 2016, at 12:18 PM, David Schweikert wrote:
>
> I wonder what the Postfix community thinks or plans to do according to
> this standard that is being written:
> https://datatracker.ietf.org/doc/draft-margolis-smtp-sts/?include_text=1
My take on the draft is that it is a hack to get t
Den 21.03.2016 18.47, skrev Viktor Dukhovni:
>
>> On Mar 21, 2016, at 12:18 PM, David Schweikert wrote:
>>
>> I wonder what the Postfix community thinks or plans to do according to
>> this standard that is being written:
>> https://datatracker.ietf.org/doc/draft-margolis-smtp-sts/?include_text=1
Am 2016-03-21 17:18, schrieb David Schweikert:
Hi,
I wonder what the Postfix community thinks or plans to do according to
this standard that is being written:
https://datatracker.ietf.org/doc/draft-margolis-smtp-sts/?include_text=1
I personally find this quite interesting. What I wonder is, if
> On Mar 21, 2016, at 3:17 PM, Michael Storz wrote:
>
> since Postfix already implements a tls policy mechanism via
> smtp_tls_policy_maps you could use the tcp_table protocol to explore the
> integration of STS into Postfix. This would allow a comparison of the
> possibilities of STS with al
> On Mar 21, 2016, at 3:27 PM, Viktor Dukhovni
> wrote:
>
> I recommend socketmap over tcp_table.
http://www.postfix.org/socketmap_table.5.html
--
Viktor.
Am 2016-03-21 20:09, schrieb Per Thorsheim:
Den 21.03.2016 18.47, skrev Viktor Dukhovni:
On Mar 21, 2016, at 12:18 PM, David Schweikert
wrote:
I wonder what the Postfix community thinks or plans to do according
to
this standard that is being written:
https://datatracker.ietf.org/doc/draft
> On Mar 21, 2016, at 4:04 PM, Michael Storz wrote:
>
> I do not think the big ISPs will implement DANE in the foreseeable future as
> you can see from the authors of this draft. They will implement STS, a SMTP
> variant of HSTS with a flavor of DMARC. And a variant of HPKP (certificate
> pin
Hi Michael,
On Mon, Mar 21, 2016 at 20:17:02 +0100, Michael Storz wrote:
> since Postfix already implements a tls policy mechanism via
> smtp_tls_policy_maps you could use the tcp_table protocol to explore
> the integration of STS into Postfix. This would allow a comparison
> of the possibilities
[ Given the recent interest on postfix-users, FYI below is my response
to the STS draft posted to the UTA WG mailing list. Folks who wish
to participate in the discussion of the STS protocol design should
join the UTA WG list and follow-up there. Further detailed discussion
is likely out o
15 matches
Mail list logo