Hi Wietse,
At the beginning (line 10) of the postconf manual it says:
"The expressions "${name:value}" and "${name?{value}}" are replaced with
"value" when "$name" is empty."
I guess it should be (? replaced by a :):
"The expressions "${name:value}" and "${name:{value}}" are replaced with
"va
Tuomo Soini:
> On Mon, 10 Jan 2011 17:41:05 +0100
>
> "Stefan" wrote:
> > On Thursday, 6th Januar 2011, 21:02:17 Victor Duchovni wrote:
> > > No warning is necessary. With a large database the cleanup thread
> > > may run longer than the scheduled interval between threads. This is
> > > fine.
>
Viktor Dukhovni wrote:
> On Thu, Jul 11, 2013 at 04:55:00PM +0200, Stefan Jakobs wrote:
[...]
> So 0.9.8j does not implement session tickets correctly. With Postfix
> 2.11 you can add:
>
> tls_ssl_options = NO_TICKET
>
> to main.cf to work-around this specific probl
Viktor Dukhovni wrote:
> On Thu, Jul 11, 2013 at 01:47:09PM +0200, Stefan Jakobs wrote:
> > $ openssl s_client -no_ssl2 -reconnect -starttls smtp -state -cipher \
> >
> > "ALL:+RC4:@STRENGTH" -connect server.example.com:25
> >
> > 250 DSN
> >
Am Mittwoch, 10. Juli 2013, 18:32:32 schrieb Viktor Dukhovni:
> On Wed, Jul 10, 2013 at 05:21:38PM +0200, Stefan Jakobs wrote:
> > I attached a full trace with a successful TLS session, an unsuccessful TLS
> > session and the following fallback to a clear session.
> > The t
Viktor Dukhovni wrote:
> On Tue, Jul 09, 2013 at 04:10:31PM +0200, Stefan Jakobs wrote:
> > postfix/smtp[8106]: setting up TLS connection to
> > server.example.com[a.b.c.d]:25
> > postfix/smtp[8106]: SSL_connect error to server.example.com[a.b.c.d]:25:
> > -1 postf
Hi list,
Postfix logs the following in my logs:
postfix/smtp[8106]: setting up TLS connection to
server.example.com[a.b.c.d]:25
postfix/smtp[8106]: SSL_connect error to server.example.com[a.b.c.d]:25: -1
postfix/smtp[8106]: warning: TLS library problem: 8106:error:1408E0F4:SSL
routines:SSL3_GE
Daniel L. Miller:
> Can a SQL database be used for the recipient verification storage?
The following link has a patch which enables Postfix to write to a MySQL
Database. With that you can keep your verify db in a MySQL database.
Use at your own risk.
https://api.opensuse.org/public/source/home:r
Am Montag, 27. Februar 2012, 13:03:46 schrieb Wietse Venema:
> Stefan Jakobs:
> > What makes me wonder is, that I can't find a hint about the 'queue file
> > write error' in the logfile. From the log it looks as if there wasn't any
> > problem with the mes
Hello list,
I received a message from my mail-daemon:
From: Mail Delivery System
To: Postmaster
Subject: Postfix SMTP server: errors from ahost
Transcript of session follows.
Out: 220 myserver.example.com ESMTP Postfix
In: EHLO ahost.example.com
...
In: DATA
Out: 354 End data with .
Out: 451
On Friday 01 April 2011 14:42:33 Stefan Jakobs wrote:
> PS: Mike's logreporter script supports postscreen logging, see:
> http://sourceforge.net/projects/logreporters/
Sorry, that's not quite correct. A pre-version he posted on the logreporters
mailinglist supports postscr
On Friday 01 April 2011 02:23:08 Wietse Venema wrote:
> I suppose it is a script with a config file with patterns for "known"
> logfile messages.
The script itself contains the patterns.
It reads the logfile line by line and checks for the patterns. So basically
it's something like that:
while
On Thursday 06 January 2011 01:45:00 Victor Duchovni wrote:
> On Wed, Jan 05, 2011 at 06:56:31PM -0500, Wietse Venema wrote:
> > Each verify or postscreen or tlsmgr process will at set times
> > scan the database for old entries.
> >
> > If it so happens that this scan doesn't finish before the n
s, the delete is suppressed and returns
+no results.
+.RE
+.IP
+This parameter is available with Postfix MySQL write support patch.
+
+NOTE: DO NOT put quotes around the delete parameter.
.IP "\fBresult_format (default: \fB%s\fR)\fR"
Format template applied to result attributes. Most c
On Tuesday 14 December 2010 14:43:23 Wietse Venema wrote:
> Stefan:
> > A drawback is that this
> > solution is not as configurable/flexible as the other one. And it's still
> > the case that the first two values of a fetched tuple must be the
> > address and its corresponing cache timings (data).
On Friday 15 October 2010 16:53:40 Victor Duchovni wrote:
> On Fri, Oct 15, 2010 at 03:05:33PM +0200, Stefan wrote:
> > in the appendix you will find a patch against Postfix 2.7.1 which adds
> > write support to Postfix' MySQL client.
> >
> > If someone like to test it, then he will find Postfix R
On Friday 01 October 2010 18:58:26 Wietse Venema wrote:
> Stefan:
> > Hi list,
> >
> > I'm in the process of adding write support to postfix's mysql client (you
> > will find a patch against postfix-2.7.1 in the appendix). But I have two
> > problems: 1) the dict_cache_clean_event writes
> > _LAS
?
Thanks for your help and kind regards
Stefan
Wietse wrote on August 22nd 2008:
> Stefan Jakobs:
> > Hello list,
> >
> > I use Postfix 2.4.3 on two (actually four, but let's assume two)
> > mailgateways. Both do recipient verification and cache the results
On Thursday, 14. Mai 2009 09:54:56 Corey Chandler wrote:
> MacShane, Tracy wrote:
> > The OS administrators do not permit GCC and
> > devel libraries on the SMTP servers I maintain (and fair enough).
>
> Nor should they-- this is what a staging environment is for. Build it
> on a staging box, tes
On Sunday 31 August 2008 01:06, Sahil Tandon wrote:
> Stefan Jakobs <[EMAIL PROTECTED]> wrote:
> > 3) Keep the actual server organisation: 4 servers with postfix,
> > amavisd, spamassassin, clamav.
> > Advantage: Known configuration, easy to extend
> > Disadva
Hello list,
In the moment our mailtraffic is handled by four mailgateways which are
reachable through one round-robin dns-mx record. Each gateway runs postfix,
amavisd, spamassassin and clamav. The four gateways handle 2.8 millions
connections a day.
My employee likes to replace the gateways wi
Hello list,
I use Postfix 2.4.3 on two (actually four, but let's assume two) mailgateways.
Both do recipient verification and cache the results with the
address_verify_map (verify.db). Sometimes it happens that a foreign server
tries to deliver a message and gets a 4xx response from one of my s
22 matches
Mail list logo
