@lbutlr:
> On Fri Feb 05 2016 12:51:06 Wietse Venema said:
> >
> > @lbutlr:
> >> Would it work to put something like this in headerchecks.pcre:
> >>
> >> /To:.*u...@example.com && From:.*remoteu...@example.net/ REDIRECT
> >> u...@example.com, localu...@example.com
> >
> >
> > Not if you u
On Fri Feb 05 2016 12:51:06 Wietse Venemasaid:
>
> @lbutlr:
>> Would it work to put something like this in headerchecks.pcre:
>>
>> /To:.*u...@example.com && From:.*remoteu...@example.net/ REDIRECT
>> u...@example.com, localu...@example.com
>
>
> Not if you use this in the header_check
After some interesting experiences using a less than stellar communications
(I didn't appreciate just how lucky I am to live in a big city until this
trip) I have managed to get things setup and working.
Because of the poor communications I decided to use the families server as
a guinea pig.
I decided to go with the folowing option:
Setup "check_client_access hash:/etc/postfix/client_access" in main.cf
In "client_access" add: "1.2.3.4 REJECT Message"
This way I will reject with 554 (custom setup in main.cf) only for specific
IPs and get rid of the log spam.
This is only valid for "pro
@lbutlr:
> Anyone?
>
> On Feb 2, 2016, at 7:42 PM, @lbutlr wrote:
> >
> > ?
> >
> > Would it work to put something like this in headerchecks.pcre:
> >
> > /To:.*u...@example.com && From:.*remoteu...@example.net/ REDIRECT
> > u...@example.com, localu...@example.com
>
Not if you use this in
Anyone?
On Feb 2, 2016, at 7:42 PM, @lbutlr wrote:
>
> …
>
> Would it work to put something like this in headerchecks.pcre:
>
> /To:.*u...@example.com && From:.*remoteu...@example.net/ REDIRECT
> u...@example.com, localu...@example.com
--
There's nothing to do, so you just stay in bed [ah
I've decided to stop using SPF checking until I've got the later version
of python-ipaddr (or whatever it was called)
On 05/02/2016 2:49 pm, Scott Kitterman wrote:
> On Friday, February 05, 2016 11:09:03 AM L.P.H. van Belle wrote:
>> Switch to the perl version of this and your problem is fixed.
>>
Lister:
[ Charset ISO-8859-1 converted... ]
> Hi all,
>
> I got a notification recently that my box is bouncing mail, and the
> recipient got the following:
>
> Command time limit exceeded: "/usr/lib/dovecot/deliver"
>
> This is quite an unusual situation, but this server should never boun
Hi all,
I got a notification recently that my box is bouncing mail, and the
recipient got the following:
Command time limit exceeded: "/usr/lib/dovecot/deliver"
This is quite an unusual situation, but this server should never bounce
mail externally. I've set soft_bounce = yes for now, b
On Friday, February 05, 2016 11:09:03 AM L.P.H. van Belle wrote:
> Switch to the perl version of this and your problem is fixed.
>
> Use postfix-policyd-spf-perl
> Not postfix-policyd-spf-python
>
> Both work the same, but the perl version works fine with ipv6 on my server.
Both work fine with I
Switch to the perl version of this and your problem is fixed.
Use postfix-policyd-spf-perl
Not postfix-policyd-spf-python
Both work the same, but the perl version works fine with ipv6 on my server.
Greetz,
Louis
> -Oorspronkelijk bericht-
> Van: t...@whyscream.net [mailto:owner-pos
Hi,
As the ticket says, the error is caused by handling ipv6 addresses. When
you hit any troubles later, you could look into disabling ipv6 :/
Regards,
Tom
On 05-02-16 00:08, Danny Horne wrote:
> Thanks for both replies,
>
> I've just checked and I'm running python-ipaddr 2.1.9, with no
First in reply to. .
... cannot find your hostname
Optional to add:
unknown_hostname_reject_code = 550
but if you have dns problems, everything gets rejected as Wiets already told
you.. .. but I think.. , so what, the sender does get the NDR, he can send
again but thats a choice. And think c
13 matches
Mail list logo
