Dear Users,
I'm facing a problem with the header_checks. I want to flip the domainpart /
userpart in the To: field of the mail header, strip off spaces/parentheses, add
a custom domainpart and replace international number scheme ++49 -> 0049.
My input string is, recipients can vary - it mig
Am 09.06.2014 13:22, schrieb Stefan Bauer:
> I'm facing a problem with the header_checks. I want to flip the domainpart /
> userpart in the To: field of the mail
> header, strip off spaces/parentheses, add a custom domainpart and replace
> international number scheme ++49 -> 0049
header_checks
Stefan Bauer:
> Dear Users,
>
>I'm facing a problem with the header_checks. I want to flip the
>domainpart / userpart in the To: field of the mail header, strip
>off spaces/parentheses, add a custom domainpart and replace
>international number scheme ++49 -> 0049.
...
>I have a working pcre but tha
Wietse Venema:
> I could rip out the DNSBL client code from the Postfix SMTP daemon
> source code and make it available as 1) a lookup table to all programs
> 2) a library module that implements the underlying DNS client code.
I played with this idea over the weekend while taking breaks from
chore
Wietse Venema:
> By itself, dnsxl maps may be useful in contexts that perform "list
> membership" lookup such as smtpd_client_event_limit_exceptions,
> where the lookup result value is ignored, For example, to prevent
> password brute-forcing from bot-infected systems:
>
> smtpd_client_event_l
Wietse Venema schrieb:
> Wietse Venema:
>> By itself, dnsxl maps may be useful in contexts that perform "list
>> membership" lookup such as smtpd_client_event_limit_exceptions,
>> where the lookup result value is ignored, For example, to prevent
>> password brute-forcing from bot-infected systems
On 06/09/2014 11:48 AM, Wietse Venema wrote:
> Wietse Venema:
>> By itself, dnsxl maps may be useful in contexts that perform "list
>> membership" lookup such as smtpd_client_event_limit_exceptions,
>> where the lookup result value is ignored, For example, to prevent
>> password brute-forcing from
Am 09.06.2014 22:17, schrieb johnea:
> On 06/09/2014 11:48 AM, Wietse Venema wrote:
>> Wietse Venema:
>>> By itself, dnsxl maps may be useful in contexts that perform "list
>>> membership" lookup such as smtpd_client_event_limit_exceptions,
>>> where the lookup result value is ignored, For exampl
Kai Krakow:
> >> smtpd_client_event_limit_exceptions = dnsxl:xbl.spamhaus.org
> >
> > Except that this does not block AUTH commands. Currently all that
> > smtpd_client_event_limit_exceptions does is not announce AUTH support
> > in the EHLO response.
>
> Hey thanks, I love the potential of t
johnea:
> Hello Wietse,
>
> Is it possible to use this to DNSBL check URLs present in the body of an
> email? (pre-queue)
As described in my posting, the dnxsl query is an IP address, a
domain name, or an email address.
So the answer is "yes" when your email contains only lines of text
with exa
On 06/09/2014 04:56 PM, li...@rhsoft.net wrote:
>>> well, one could say: block them from submission port and don't allow
>>> SASL on 25, but that works only if you are a startup beginning from
>>> scratch,
>>
>> If that's the case then you can put submission on a separate IP address,
>> so that you
On 06/08/2014 08:17 PM, Kai Krakow wrote:
> MX and Submission machine are the same postfix instance (and even the same
> worker process on port 25), it won't work. I'm planning to maybe change this
> in the future. But as with migrating all people to not submit on port 25 it
> is a long way to g
I really should have figured this out ages ago, but...
Quite simply, there exits a small number of organizations that
run afoul of my various smtpd_recipient_restrictions and/or my
smtpd_helo_restrictions, but from which I need to be able to
receive mail anyway. (A small number of companies get
On 6/9/2014 7:12 PM, Ronald F. Guilmette wrote:
> I really should have figured this out ages ago, but...
>
> Quite simply, there exits a small number of organizations that
> run afoul of my various smtpd_recipient_restrictions and/or my
> smtpd_helo_restrictions, but from which I need to be able t
10.06.2014 05:02, Stan Hoeppner wrote:
> On 6/9/2014 7:12 PM, Ronald F. Guilmette wrote:
>> I really should have figured this out ages ago, but...
>>
>> Quite simply, there exits a small number of organizations that
>> run afoul of my various smtpd_recipient_restrictions and/or my
>> smtpd_helo_res
15 matches
Mail list logo