Has anyone ever written a proxy server for policy services? I have a
policy server (grossd, one of the best greylisting engines I've ever
used) that, if it goes down, causes my Postfix servers to temp fail
everything with 'Server configuration problem'. This is a real problem
for me. I'd lik
> > /etc/postfix/main.cf:
> > # Rewrite envelope sender only.
> > sender_canonical_classes = envelope_sender
> > sender_canonical_maps = pcre:/etc/postfix/sender_canonical
> >
> > /etc/postfix/sender_canonical:
> > # Replace non-local address by foo...@example.com.
> > if !/@exa
Len Conrad a écrit :
The above is caught by:
/[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}.*\[/
client_filter.class
>>> remove the \[ part.
>>> and BTW, here is a shorter version:
>>> /(\d{1,3}[-\.]){3}\d{1,3}/ class_client_filter
>>>
>>>
... but is n
Noel Jones a écrit :
> mouss wrote:
>> Len Conrad a écrit :
>>> ... they work, and works for each different PCRE in the .class.
>>> The above is caught by:
>>>
>>> /[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}.*\[/
>>> client_filter.class
>>>
>>
>> remove the \[ part.
>>
>> and BT
On Tue, May 12, 2009 at 05:35:48PM -0400, Wietse Venema wrote:
> For example, to replace the envelope sender address of outside
> senders by foo...@example.com:
>
> /etc/postfix/main.cf:
> # Rewrite envelope sender only.
> sender_canonical_classes = envelope_sender
> sender_canonical_
Gary Smith:
> Hello,
>
> (this may come twice send I sent it once prior to confirming
> subscription to group -- sorry)
>
> We encountered a couple problems with our blackberry and other
> users when people on our exchange server setup forwards. Typically
> we forward a lot of email to technici
Hello,
(this may come twice send I sent it once prior to confirming subscription to
group -- sorry)
We encountered a couple problems with our blackberry and other users when
people on our exchange server setup forwards. Typically we forward a lot of
email to technicians in the field. The pr
Postfix legacy releases 2.5.7, 2.4.11 and 2.3.17 contain fixes that
were already included with Postfix versions 2.6 and 2.7.
Postfix 2.5.7:
- (low) The installation/upgrade procedure did not automatically
create the data_directory.
- (medium) In the "new queue manager", the _destination_rate_d
Sorry - the hostname parameter was not blank on my initial config, I
just omitted it from the email when I pasted my postconf -n. I guess I
should have specified that before. I removed the trailing 'permits'
from the 'smtpd_*_restrictions' as shown below. Also removed blank
entries like 'relayhosts
Len Conrad wrote:
Here's what I use to match IP-containing hostnames, should work for you.
/(\d{1,3}[-\.]){3}\d{1,3}[^.]+\.[^.]/ class_client_filter
ie. there must be a dot somewhere after the IP-containing section.
OK, same idea as mine, but I say "there must be a [ after the PTR domain name"
Reinaldo de Carvalho:
> On Tue, May 12, 2009 at 10:17 AM, Wietse Venema wrote:
> >
> > - Postfix no longer adds (Resent-) From:, Date:, Message-ID: or To:
> > ?headers to email messages with "remote" origins (these are origins
> > ?that don't match $local_header_rewrite_clients). Adding such
> > ?
On Tue, May 12, 2009 at 10:17 AM, Wietse Venema wrote:
>
> - Postfix no longer adds (Resent-) From:, Date:, Message-ID: or To:
> headers to email messages with "remote" origins (these are origins
> that don't match $local_header_rewrite_clients). Adding such
> headers breaks DKIM signatures tha
Postfix stable release 2.6.0 is available. After Postfix was declared
"complete" with version 2.3, the focus has moved towards improving
the code/documentation, and updating it for changing environments.
- Multi-instance support introduces a new postmulti(1) command to
create/add/remove/etc. add
Len Conrad:
> I've got a restriction class client_filter.class, which has several PCREs.
>
> The problem is that some PTRs that should be shunted into that class are not.
>
>
> When I test/paste actual maverick PTRs, eg this "access net" PTR:
>
> postmap -q "79-70-88-236.as9105.com["
> pcre:
LuKreme schrieb:
On 11-May-2009, at 09:41, Mathias Meinelt wrote:
Simon Wilson wrote:
TXT v=spf1 a mx ip4:59.167.212.191 ~all
Is my TXT record OK? Do I need the IP4 entry?
[115 total lines deleted]
Mathias
Was it really necessary to quote all of the previous message? Yes,
top postin
>>>The above is caught by:
>>>
>>>/[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}.*\[/
>>>client_filter.class
>>remove the \[ part.
>>and BTW, here is a shorter version:
>>/(\d{1,3}[-\.]){3}\d{1,3}/ class_client_filter
>>
>>
>>>... but is not going to the restriction class as
16 matches
Mail list logo
