similar to: dovecot-SASL for Postfix: EXTERNAL does not work.

Displaying 20 results from an estimated 6000 matches similar to: "dovecot-SASL for Postfix: EXTERNAL does not work."

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
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
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
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 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>: >
2018 Aug 21
2
Call for testing: OpenSSH 7.8
Hi Damien, Damien Miller wrote on Tue, Aug 21, 2018 at 12:04:41PM +1000: > ok, djm@ Thanks for checking, and thanks to Val and Michael for testing. I just committed the patch to OpenBSD, others will likely take care of merging it to -portable. > (I'd prefer the comment before the return statement, but up to you) Immediately before the return statement, it looked really confusing,
2020 Mar 12
2
[PATCH 0/1] *** SUBJECT HERE ***
On 12.03.20 19:09, Christoph Anton Mitterer wrote: > On Wed, 2020-03-11 at 21:39 +0100, Thomas Koeller wrote: > IMO, the idea itself sounds not the best... one must assume that such > invoked programs are not written "safe"... and thus an attacker could > potentially cause the system to run such programs a huge number of > times. As the anticipated action of the program is
2023 Feb 20
1
fseek/fgetc puzzle
Darren Tucker wrote in <CALDDTe39k4UFJWBvts5HWbbhHO+Vw9OAP0zBhu-Hje-2aR9+xA at mail.gmail.com>: J?rg Schilling convinced me in 2017 Readd removed fflush()/fseek() in between read and write.. The behave:record_a_resend-2 test failed on Solaris 5.10 and 5.11, messages in *record* where separated by four \n / U+000A instead of two. It turns out that the effective sequence
2020 Sep 08
3
[PATCH 0/5] ZSTD compression support for OpenSSH
On 2020-09-07 11:21:13 [+1000], Darren Tucker wrote: > The zstd part would be a larger discussion because we would need to > either carry it as a Portable patch or have zstd added to OpenBSD > base, and I don't know if that would be accepted. Do you have any > performance numbers for zstd in this application? A key stroke is here 10 bytes of raw data which zstd compresses usually
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>,
2002 Feb 04
2
ext3 and chattr +S on postfix spools
Postfix <http://www.postfix.org> does a chattr +S on its spool directory when it is installed on Linux. This is what is written in the postfix startup script -- # # LINUX by default does not synchronously update directories - # that's dangerous for mail. # if [ -f /usr/bin/chattr ] then CHATTR="/usr/bin/chattr +S" else CHATTR=echo fi -- Is this still required on ext3 ?
2005 Sep 14
3
mailbox corruption
Hello, Here is the description of a problem we habe been having for some time. Originally posted on the postfix-users mailing list, but no solution found to date. >>>> We have been having problems with our mail system for a couple of >>>> months. Every now and then, some mailboxes get corrupted: a >>>> half-truncated message, usually without headers, is at
2002 May 01
4
Using openssh 3.1p1 on Solaris with tcp wrappers 7.6
Dear Open SSH and TCP Wrappers Colleagues, We are trying to use open ssh 3.1p1 on SPARC platforms under Solaris 2.8 using gcc 2.95.2, in conjunction with tcp wrappers 7.6 (IPv6 version). The wrapping of open ssh is not too well documented but I think we have figured most of this out (hearty thanks to Wietse Venema, Jim Mintha & Niels Provos for their helpful email exchanges) -- but have one
1998 Aug 05
6
Problem with TCP_wrappers
Hi, I''m running into something weird here. I''m using RH5.1 with tcp_wrappers 7.6. The syntax for hosts.allow and hosts.deny is: <service list> : <access list> [ : <shell_command> ] Everything works when I _don''t_ use the shell_command. I used the _exact_ line as in the man-pages utilising "safe_finger" (comes with tcp_wrappers), tcpdchk
2004 Feb 15
6
Rooted system
Howyd all? Seems that I have been routed. Possibly by a physical B&E, but who knows? Probably some of you do.... anyways, some politically sensitive email was deleted from a user account and the line low -tr & inserted into my .xinitrc . Duncan (Dhu) Campbell
2017 Mar 31
2
Sendmail is considered deprecated
On Fri, March 31, 2017 4:46 pm, Alice Wonder wrote: > On 03/31/2017 02:40 PM, Kenneth Porter wrote: >> On 3/31/2017 2:15 PM, Valeri Galtsev wrote: >>> Well, it sounds like you are one of the companies with whose effort I >>> have >>> to fight constantly in my own effort to protect our users from spam... >> >> What makes Postfix superior in fighting
2006 Mar 01
1
sshd blocking SIGALARM turns out to be due to tcpd
Ian Jackson: > I recently encountered a bug where some ssh login sessions would > apparently inherit a blocked SIGALRM. A web search showed up two > relevant threads: > http://lists.suse.com/archive/suse-linux-e/2005-Dec/2628.html > http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=113533337923128&w=2 > et seq - but sadly no answers. > > Experimentation with
2023 Oct 18
9
ssh wish list?
Hey all, So I do some development based on openssh and I'm trying to think of some new projects that might extend the functionality, feature set, user workflow, performance, etc of ssh. So open ended question: Do any of you have a wish list of things you'd like to see in ssh? Mostly I'm just curious to see what the larger community is thinking of rather than being driven
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 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