Yes, you have right but this is already fixed. In postfix's config files is
clear and setting works nice. But I am curious why set
smtp_bind_address=X.X.X.X in master.cf like docs say didn't work in my
case. I added it to main.cf then it works.
2018-04-17 13:06 GMT+02:00 Wietse Venema
On 17.04.18 13:26, Poliman - Serwis wrote:
Yes, you have right but this is already fixed. In postfix's config files is
clear and setting works nice. But I am curious why set
smtp_bind_address=X.X.X.X in master.cf like docs say didn't work in my
case. I added it to main.cf then it works.
Poliman - Serwis:
> Thank you for answer. You understand me wrong. I can't believe that I made
> a typo there and left comma. I know that comma is a form of whitespace. ;)
> But I am curious why set smtp_bind_address=X.X.X.X in master.cf like docs
> say didn't work in my case. I added it to
Now all works fine. I have to add smtp_bind_address in main.cf, because any
modification of original smtp_bind_address from master.cf did not work at
all (thus in logs which I put you can see combinations like this one from
port and comma). Based on documentation I thought I should modify
I finally managed to isolate this. I have no been receiving mails from some
mail servers and there's very little being logged. I obviously set some
configuration that mucked things up. Here is the entire mail.log from the first
minute after midnight:
Apr 17 00:00:09 mail
On Tue, Apr 17, 2018 at 06:38:00AM -0600, @lbutlr wrote:
> I finally managed to isolate this. I have no been receiving mails
> from some mail servers and there's very little being logged. I
> obviously set some configuration that mucked things up. Here is
> the entire mail.log from the first
On Apr 17, 2018, at 07:58, Dominic Raferd wrote:
> What do the 'dovecot: imap-login' messages signify?
That wouldn't be involved. This wasn’t a user logging in, this was mail
delivering from the dovecot list
> Judging from the final smtpd log message, STARTTLS wasn't
On Tue, Apr 17, 2018 at 01:39:45PM +0200, Poliman - Serwis wrote:
> Now all works fine. I have to add smtp_bind_address in main.cf,
> because any modification of original smtp_bind_address from
> master.cf did not work at all (thus in logs which I put you can
> see combinations like this one
On 17 April 2018 at 13:38, @lbutlr wrote:
>
> I finally managed to isolate this. I have no been receiving mails from some
> mail servers and there's very little being logged. I obviously set some
> configuration that mucked things up. Here is the entire mail.log from the
>
Poliman - Serwis:
> Yes, you have right but this is already fixed. In postfix's config files is
> clear and setting works nice. But I am curious why set
> smtp_bind_address=X.X.X.X in master.cf like docs say didn't work in my
> case. I added it to main.cf then it works.
There is no difference.
> On Apr 17, 2018, at 8:38 AM, @lbutlr wrote:
>
> Apr 17 00:00:09 mail postfix/postscreen[67061]: CONNECT from
> [94.237.32.243]:46598 to [65.121.55.42]:25
> Apr 17 00:00:09 mail postfix/dnsblog[74920]: addr 94.237.32.243 listed by
> domain hostkarma.junkemailfilter.com as
Try
debug_peer_list = 94.237.32.243
in main.cf
Willi
Am 17.04.2018 um 14:38 schrieb @lbutlr:
> I finally managed to isolate this. I have no been receiving mails from some
> mail servers and there's very little being logged. I obviously set some
> configuration that mucked things up. Here is
to apply a limit to the url??
{64}.* (your linked profile)/
it's correct this rule?
El 11/04/18 a las 02:59, Dominic Raferd escribió:
On 11 April 2018 at 01:24, Stephen Satchell > wrote:
The | operator is supposed to bind to a single token
> On Apr 17, 2018, at 12:22 PM, Emanuel wrote:
>
> to apply a limit to the url??
>
> {64}.* (your linked profile)/
>
> it's correct this rule?
The above is much too cryptic. Perhaps you can state a clear goal and a more
precise question.
--
Viktor.
Hi.
I would like to limit one sasl user and permit him to send only to one
domain.
I have a few users in my my postfix server.
Rest of users can send to wherever.
How do it?
Could help me?
Peter.
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
my idea is to limit the possibilities of the regular expression
by indicating only * there is an infinite number of possibilities
I've been having no luck with a simple regex to match strings with 64 or
less characters.
Regards,
El 17/04/18 a las 13:56, Viktor Dukhovni escribió:
On Apr
On 04/17/18 13:33, Emanuel wrote:
> my idea is to limit the possibilities of the regular expression
>
> by indicating only * there is an infinite number of possibilities
>
> I've been having no luck with a simple regex to match strings with 64 or
> less characters.
In a Perl-compatible regular
> On Apr 17, 2018, at 1:39 PM, Phil Stracchino wrote:
>
> In a Perl-compatible regular expression, you want something like this:
>
> /.{,64}(your linked profile)/
Which (when used verbatim) is equivalent to:
/your linked profile/
To restrict the match to strings
On 04/17/18 13:53, Viktor Dukhovni wrote:
>
>
>> On Apr 17, 2018, at 1:39 PM, Phil Stracchino wrote:
>>
>> In a Perl-compatible regular expression, you want something like this:
>>
>> /.{,64}(your linked profile)/
>
> Which (when used verbatim) is equivalent to:
>
>
19 matches
Mail list logo