similar to: Fwd: Re: sasl parameters missing (in postfix)

Displaying 20 results from an estimated 1000 matches similar to: "Fwd: Re: sasl parameters missing (in postfix)"

2008 May 07
1
[bug] bit of a clearer error message desired - Can't load CA file... : Success
Not the clearest of error messages. A successful cannot load. May 7 21:05:29 10.10.10.213 dovecot: child 21500 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21501 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21502 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21503 (login) returned error 89 May 7 21:05:29 10.10.10.213
2008 May 18
1
compile troubles - stat.mtim - 1.1hg
having trouble compiling dovecot-1.1hg latest pull I'm amost thinking _GNU_SOURCE needs to be defined as its built to work Any suggestions welcome. make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/list' Making all in index make[4]: Entering directory
2020 Aug 21
0
[EXT] Re: dovecot-SASL for Postfix: EXTERNAL does not work.
> On 21/08/2020 02:17 Steffen Nurpmeso <steffen at sdaoden.eu> wrote: > > > Hello and good evening. > > Sorry for responding so late, it is midsummer and i spend as much > time as possible on the outside (bicycle, mostly). (Just one more > day, then 10 degrees colder!!) > > I Cc: Wietse Venema, because i quote a message of him. > (this is "set
2020 Aug 20
2
dovecot-SASL for Postfix: EXTERNAL does not work.
Hello and good evening. Sorry for responding so late, it is midsummer and i spend as much time as possible on the outside (bicycle, mostly). (Just one more day, then 10 degrees colder!!) I Cc: Wietse Venema, because i quote a message of him. (this is "set quote-add-cc" here.) Aki Tuomi wrote in <84881193.5398.1597934431687 at appsuite-dev-gw2.open-xchange.com>: The dovecot
2002 Feb 03
1
[wietse@porcupine.org: Re: syncronous directory operation for linux (ext2)]
There's a big thread about filesystems on postfix-users@postfix.org Could you shed some light on that issue? ----- Forwarded message from Wietse Venema <wietse@porcupine.org> ----- From: wietse@porcupine.org (Wietse Venema) Date: Sun, 3 Feb 2002 07:53:26 -0500 (EST) To: Lawrence Greenfield <leg+@andrew.cmu.edu> Cc: Wietse Venema <wietse@porcupine.org>,
2011 Mar 03
5
auth on tcp socket?
Hello, >> is it possible to provide service auth on tcp-socket instead of >> unix-socket? >> I changed my conf and dovecot 2.0.5 is restarting but on telnet test it >> throws: >> dovecot: auth: Fatal: getsockname(12) failed: Socket operation on >> non-socket >> >> Want to separate smtp and imap to different servers but keep using >>
2020 Aug 21
0
[EXT] Re: dovecot-SASL for Postfix: EXTERNAL does not work.
> On 21/08/2020 17:56 Steffen Nurpmeso <steffen at sdaoden.eu> wrote: > > > Aki Tuomi wrote in > <1907575568.4364.1597984769802 at appsuite-dev-gw1.open-xchange.com>: > |> On 21/08/2020 02:17 Steffen Nurpmeso <steffen at sdaoden.eu> wrote: > ... > |> Wietse Venema wrote in > |> <4BXSTk189nzJrP3 at spike.porcupine.org>: >
2008 Jun 10
3
Multiple SSL certificates with dovecot.
Hello all, By advance, I hope you'll excuse my probably not perfect English, which is not my mother tongue. I have always appreciated dovecot for this simplicity to setup and lightweight, but today, after many installations, I cannot find how to setup dovecot for my configuration. - I use only IMAPS to retrieve the mails. - I manage two domain names - I use CA-Cert certificates So,the
2008 Jun 29
2
fd limit 1024 is lower in dovecot-1.1.1
Hi, all. I just upgrade from 1.0.15 to 1.1.1 in a test box(RHEL 5.2, x86_64). after upgrade, i got this warning msg: ----8< ---- # /etc/init.d/dovecot restart Stopping Dovecot Imap: [ OK ] Starting Dovecot Imap: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1280). Either grow the limit or change
2020 Aug 20
0
dovecot-SASL for Postfix: EXTERNAL does not work.
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> </div> <blockquote type="cite"> <div> On 20/08/2020 17:28 Steffen Nurpmeso <<a href="mailto:steffen@sdaoden.eu">steffen@sdaoden.eu</a>> wrote: </div> <div>
2020 Aug 21
4
[EXT] Re: dovecot-SASL for Postfix: EXTERNAL does not work.
Aki Tuomi wrote in <1907575568.4364.1597984769802 at appsuite-dev-gw1.open-xchange.com>: |> On 21/08/2020 02:17 Steffen Nurpmeso <steffen at sdaoden.eu> wrote: ... |> Wietse Venema wrote in |> <4BXSTk189nzJrP3 at spike.porcupine.org>: |> ... |>|Steffen Nurpmeso: |> ... |>|> until SASL says it is done?!. How could EXTERNAL ever work
2002 Feb 05
0
[akpm@zip.com.au: Re: ext3 and chattr +S on postfix spools]
postfix-users seems to be a subscription only list. I'd recommend incorporating TDMA <http://tdma.sf.net/> to allow for easy discussion by outsiders Andrew Morton (of ext3 fame) had sent this message to postfix-users list I am forwarding so that Wietse can hopefully provide the definitive answer to the question Andrew Morton/Stephen Tweedie seek ----- Forwarded message from Andrew
2017 Apr 10
2
Fwd: Obsolete NSA exploit for Postfix 2.0 - 2.2
This was just posted on the Postfix list. Centos 7 ships with: postfix-2.10.1-6.el7 Has this cert advisory been applied to the Centos build of Postfix? thank you -------- Forwarded Message -------- Subject: Obsolete NSA exploit for Postfix 2.0 - 2.2 Date: Sun, 9 Apr 2017 16:18:06 -0400 (EDT) From: Wietse Venema <wietse at porcupine.org> To: Postfix users <postfix-users at
2020 Aug 20
3
dovecot-SASL for Postfix: EXTERNAL does not work.
Hello. I am not subscribed and new here, so first of all i want to thank you for dovecot. I personally do not use it in "production" (yet), but it is my sole point of interaction for testing the little MUA i maintain for quite some years. I also have used its code for affirmation purposes. (Interesting that OAUTHBEARER treats hostname and port as optional. I currently do
1998 Aug 02
0
ipportfw - security
Hi Are there any known security holes or necessary precautions in using port forwarding with ipportfw? I'm planning on forwarding ports from an outer firewall/router (connected to the Internet) to a host in the DMZ, then on from the DMZ host to the inner firewall, and finally from the inner firewall to some host on the inside. Thanks, Jens jph@strengur.is From mail@mail.redhat.com Wed
2016 Dec 26
0
Noise Cancellation of Server Noise
On Mon, December 26, 2016 9:51 am, Valeri Galtsev wrote: > > On Mon, December 26, 2016 12:16 am, geo.inbox.ignored wrote: >> >> >> On 12/25/2016 09:25 PM, Always Learning wrote: >>> On Sun, 2016-12-25 at 13:38 -0600, geo.inbox.ignored wrote: >>>> On 12/25/2016 11:53 AM, Mark Woolfson (Notebook) wrote: >>>>> If the server decision makers
2002 Jul 29
1
Valgrind
http://developer.kde.org/~sewardj/ Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * Use of uninitialised memory * Reading/writing memory after
1998 Aug 04
0
summary of responses to "firewalls, a practical question"
A little over a week ago I posted asking about setting up a linux box between an existing router and a switch in order to provide firewall service to a subnet of machines. I was curious what experience others had with this type of setup in terms of machines, configurations, and the appropriateness of using linux in this manner. There were basically three issues discussed in replies: hardware
1998 Dec 15
1
portmap & tcpwrappers
I don't know if this is RedHat 5.1 specific, but be aware that the version of portmap distributed is the enhanced (Wietse Venema) version. That's great, except for two things. The first is documented, but easy to overlook: "In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name...The upshot of all this is that only network
2023 Nov 09
1
2.8.1 build buglet: sockdebug.c
Jim Klimov <jimklimov+nut at gmail.com> writes: > By the way, on the NUT CI farm the libwrap is present on some (though not > all) systems - covering linux, freebsd, openindiana... and neither > complained about `sockdebug` :\ > > What version do you have? Maybe it is some alternate implementation? Looks like 7.4, as amended in NetBSD over the years. Looks like the