Am 24.12.24 um 12:07 schrieb Simon Kelley:
On 22/12/2024 10:44, Matthias Andree via Dnsmasq-discuss wrote:
Am 20.12.24 um 22:16 schrieb Simon Kelley:
On 12/20/24 12:27, Matthias Andree via Dnsmasq-discuss wrote:
Simon,
I cannot compile v2.91test1 on FreeBSD 14.2, errors below. (Neither
Am 20.12.24 um 22:16 schrieb Simon Kelley:
On 12/20/24 12:27, Matthias Andree via Dnsmasq-discuss wrote:
Simon,
I cannot compile v2.91test1 on FreeBSD 14.2, errors below. (Neither
tarball nor Git compile.) (2nd to last shown errors). Patch attached,
should be fine with git-am.
Patch
a
structure or union
226 | !callback.af_local(iface_index, ARPHRD_ETHER,
LLADDR(sdl), sdl->sdl_alen, parm))
| ^
9 warnings and 5 errors generated.
From 355acd8963abcfee1ae4d78c81103f68d2577f24 Mon Sep 17 00:00:00 2001
From: Matth
Am 01.12.24 um 14:34 schrieb Michael Tokarev via Postfix-users:
Hi!
For a long time I thought this problem is due to limitation of mailx
email
submission program - when our users submit email message using mailx,
their
From: header (which is filled using getpwnam(), with proper First.M.Last)
is
fetchmail 6.5.0.rc1 has been released and should fix these documentation
flaws. Report remaining issues directly upstream through
https://gitlab.com/fetchmail/fetchmail/-/issues.
Note I do not support Ubuntu (whom I consider freeriders) directly, so
bug reports not forwarded to the Debian or FreeB
Control: tags 700266 + fixed-upstream
To be closed in a future release - or today in upstream Gitlab commit
https://gitlab.com/fetchmail/fetchmail/-/commit/f67145650151ad0bab36e347a6ed73bd0be278f6
Control: tags -1 upstream confirmed fixed-upstream
Control: severity -1wishlist
Am 19.07.24 um 15:30 schrieb Manny:
Package: fetchmail
Version: 6.4.37-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: debbug.fetchm...@sideload.33mail.com
This warning:
fetchmail: WARNING: pop.yandex.com configu
Am 30.12.23 um 18:42 schrieb Mike via Postfix-users:
On 12/30/2023 12:08 PM, Wietse Venema via Postfix-users wrote:
"Hakon Alstadheim wrote:
Just FYI, I got postfix 3.7.9-0+deb12u1 from bookworm-updates (i.e.
Debian) today.
Scott Kitterman:
For those still using Debian Bullseye (oldstable), p
Am 14.12.23 um 14:20 schrieb Wietse Venema via Postfix-users:
As a few on this list may recall, it is 25 years ago today that the
"IBM secure mailer" had its public beta release. This was accompanied
by a nice article in the New York Times business section.
There is some literature at https://ww
Am 18.05.23 um 09:09 schrieb Gert Doering:
Hi,
On Thu, May 18, 2023 at 09:00:26AM +0200, Matthias Andree wrote:
That, and constants usually go on the left-hand side of comparison so
the compiler flags the accidental if (foo = NULL) even if it does not
produce "add a pair of parentheses i
Am 17.05.23 um 22:47 schrieb Antonio Quartulli:
Hi,
On 17/05/2023 22:01, Ilya Shipitsin wrote:
malloc was not checked against NULL, I was able
to get core dump in case of failure
Signed-off-by: Ilya Shipitsin
---
src/openvpn/dco_freebsd.c | 5 +
1 file changed, 5 insertions(+)
diff --
I think not fixing this in the package as a regular fix (it's a patch
after all) is ill-advised,
but for those who find this bug unfixed in their installation:
The workaround is to install asciidoc through pip install --user
asciidoc instead, or possibly with pipx.
Example in line #6 of my test
Package: asciidoc-base
Version: 10.2.0-1
Severity: important
Dear Maintainer,
as a maintainer of the fetchmail upstream package,
I want to build documentation with asciidoc.
As part of fetchmail's build with meson on the legacy_6x branch of
fetchmail, asciidoc is being run, but cannot find icons
Am 28.03.23 um 20:58 schrieb Antonio Quartulli:
Hi,
On 28/03/2023 20:51, Matthias Andree wrote:
Am 28.03.23 um 17:12 schrieb Frank Lichtenheld:
Since we use strlen() to determine the length
and then check it ourselves, there is really
no point in using strncpy.
But the compiler might
Am 28.03.23 um 17:12 schrieb Frank Lichtenheld:
Since we use strlen() to determine the length
and then check it ourselves, there is really
no point in using strncpy.
But the compiler might complain that we use
the output of strlen() for the length of
strncpy which is usually a sign for bugs:
er
Am 28.03.23 um 12:09 schrieb Frank Lichtenheld:
Github will stop supporting them on April, 1st.
ACK nowledged.
OpenPGP_signature
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists
Am 28.03.23 um 10:47 schrieb Frank Lichtenheld:
On Mon, Mar 27, 2023 at 09:45:53PM +0200, Matthias Andree wrote:
Am 27.03.23 um 16:45 schrieb Selva Nair:
Hi,
On Mon, Mar 27, 2023 at 9:59 AM Matthias Andree
wrote:
Am 27.03.23 um 13:49 schrieb selva.n...@gmail.com:
> From: Se
Am 27.03.23 um 16:45 schrieb Selva Nair:
Hi,
On Mon, Mar 27, 2023 at 9:59 AM Matthias Andree
wrote:
Am 27.03.23 um 13:49 schrieb selva.n...@gmail.com:
> From: Selva Nair
>
> - Do not use non-literal initializers for static objects
> - Replace empty initiali
Am 27.03.23 um 13:49 schrieb selva.n...@gmail.com:
From: Selva Nair
- Do not use non-literal initializers for static objects
- Replace empty initializer {} by {0}
Should we go to a revision, I would suggest to not make something
compliant to a compiler because that is assigning it way too muc
Am 24.03.23 um 22:12 schrieb Selva Nair:
Hi,
On Fri, Mar 24, 2023 at 4:18 PM Matthias Andree
wrote:
Am 23.03.23 um 15:31 schrieb Frank Lichtenheld:
> Currently this is not obvious since we never build the
> UTs with MSVC, but it doesn't like the initializers with
Am 23.03.23 um 15:31 schrieb Frank Lichtenheld:
Currently this is not obvious since we never build the
UTs with MSVC, but it doesn't like the initializers with
"const" variables. They cause
error C2099: initializer is not a constant
What MSVC version are you using? What options? I've tried with
Am 20.03.23 um 18:15 schrieb Paul Constantine:
So here is my DNSMASQ problem.
I'm running to VirtualBox Ubuntu 16.04 servers on two seperate 2011
mac mini servers (macos High Sierra).
That's your first problem, unmaintained obsolete OS and likewise
dnsmasq. 18.04 which is also dying shipped dns
Am 10.03.23 um 17:12 schrieb Marvin Renich via Postfix-users:
Additionally, every MUA that I know of recognizes a subject beginning
with "Re:" or "RE:" and when replying avoids duplicating this in the
reply subject.
While I have used mutt exclusively for a long time to send email, I
occasionally
Am 10.03.23 um 11:07 schrieb Jaroslaw Rafa via Postfix-users:
Dnia 10.03.2023 o godz. 18:18:50 Phil Biggs via Postfix-users pisze:
Likewise, To keep my mail client's threaded view sane I resorted to using
header_checks:
/^Subject: \[pfx\] (.*)$/ REPLACE Subject: $1
What a mail client has probl
Greetings,
I have reverted the bytecode triggers changes from the ports tree,
please fix that up first, then commit. Details see attached e-mail or
https://reviews.freebsd.org/D34739
Thanks.
Cheers,
Matthias--- Begin Message ---
Am 18.02.23 um 08:42 schrieb Antoine Brodin:
On Wed, Feb 15,
Am 16.02.23 um 18:52 schrieb Gert Doering:
Hi,
On Thu, Feb 16, 2023 at 08:48:26AM -0500, Jonathan K. Bullard wrote:
On Thu, Feb 16, 2023 at 7:51 AM Frank Lichtenheld wrote:
The OpenVPN community project team is proud to release OpenVPN 2.5.9. This is
a small bugfix release.
Was this sent a b
Am 28.01.23 um 19:55 schrieb Gert Doering:
Acked-by: Gert Doering
To see the actual failure, one needs to build a tarball ("make dist"),
and from that tarball, compile with "configure --enable-dco", on FreeBSD
- so a pure "make distcheck" did not see it. Apologies for that oversight.
Your pat
This file was missing from src/openvpn/Makefile.am.
---
src/openvpn/Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/openvpn/Makefile.am b/src/openvpn/Makefile.am
index 3ed73fa4..a8e44528 100644
--- a/src/openvpn/Makefile.am
+++ b/src/openvpn/Makefile.am
@@ -78,6 +78,7 @@ openvp
Am 25.01.23 um 20:50 schrieb Frank Lichtenheld:
The OpenVPN community project team is proud to release OpenVPN 2.6.0.
This is the new stable version of OpenVPN with some major new features.
Hi Frank,
OpenVPN 2.5.x releases also showed up in .tar.xz format - are there
plans to provide these (an
Am 23.01.23 um 08:40 schrieb Pascal Obry:
Hello devs,
As we are not ready to have an automatic reformatting of the code I
have started at least making the function headers a bit more readable.
From:
void dt_gui_presets_show_edit_dialog(const char *name_in, const char
*module_name, int rowid,
Am 17.01.23 um 23:22 schrieb 17th of this month:
Previous-Subject: Re: [Dnsmasq-discuss] [PATCH] Add run-time option to disable
CHAOS TXT records
In-Reply-To: <9e8bb769-db3e-770b-f058-fcc73f557...@thekelleys.org.uk>
On Mon, Jan 16, 2023 at 10:46:25PM +, Simon Kelley wrote:
...
Have I m
Am 15.01.23 um 12:44 schrieb Gert Doering:
Hi,
On Sat, Jan 14, 2023 at 05:28:09PM -0500, James Bottomley wrote:
What do you mean "a source"? every apache licensed library that's
statically linked with a GPLv2 program would be an example of this ...
in the early days there was no dynamic linking
Am 14.01.23 um 18:29 schrieb Arne Schwabe:
Hey,
This is the first round and will be only to the openvpn-devel list.
After that I will also write to individuals email addresses but I want
to start with sending this to the devel list.
We are writing to you since you are or were a contributor in p
Am 14.01.23 um 19:44 schrieb Arne Schwabe:
Am 14.01.2023 um 19:35 schrieb Matthias Andree:
Am 14.01.23 um 18:29 schrieb Arne Schwabe:
We also considered going for a change from GPL2 to GPL2+ but we think
that GPL3 would hurt the ability to distribute OpenVPN as part of
router or other
Am 14.01.23 um 18:29 schrieb Arne Schwabe:
We also considered going for a change from GPL2 to GPL2+ but we think
that GPL3 would hurt the ability to distribute OpenVPN as part of
router or other embedded devices as the GPL3 has been explicitly
developed (at least in part) to make this use case ha
Francesco,
none of the options in that nroff table "user descriptions and options"
mentions arguments to any options, with the exception of sslfingerprint
that gets it wrong - its intention (as inherited from Eric Raymond)
seems to just list the long and their short equivalents, but the
redudancy
https://gitlab.com/fetchmail/fetchmail/-/issues/56
Am 04.01.23 um 16:43 schrieb Mica Semrick:
You're making a lot of assumptions here. Seems like you have some
deeper issue than someone asking a simple question about support.
Maybe a break from the computer is in order.
You are considering my earlier messages rude and now you are insinuating
I
Am 04.01.23 um 15:58 schrieb Mica Semrick:
This answer is a bit rude and doesn't answer the original query.
It may be rude if you consider "who cares" rude, and prevents people
from wasting their time while pointing out the actual issue, which is
"old distro" which is too old to build darktable
Am 04.01.23 um 04:51 schrieb Bob Tregilus:
Hi -
I'm not sure who I should alert to this issue, someone on this dev
list or should I write to OBS support?
On the openSUSE contributors OBS they list the following four 4.2.0
darktable builds for Unbuntu based distros (I added the support
informati
Am 31.12.22 um 05:29 schrieb Sean Hennessey:
I'm doing some testing and am trying to figure out a way to set up
postfix so that it won't ever send a DSN.
What is the use case for that other than bulk sending of unsolicited
e-mail?
Normally operators will want to know what addresses to remove
Am 24.12.22 um 03:28 schrieb Samer Afach:
Dear Raf:
That's actually what I do on all the bare-metal machines, but from my
understanding of how docker works, every container is made to run
exactly one service, and somehow default Linux images disable system
services. They can be re-enabled, but i
(in
case that's the answer to that question about simplicity)... oh, my...
vSphere and/or KVM are a whole other monster that need resources and
management and introduce their own problems.
I have not implied that they were, but they are ONE means to implement
an inside/outside testing setup
Am 23.12.22 um 03:19 schrieb Samer Afach:
Dear Matthias,
I think there's a misunderstanding here. The server is already
shutdown. I thought you meant that I should shutdown the server
permanently and move on with my life because I'm incapable of running
a server, which seems to have been the con
and it has always been
*the* example of good design, documentation and compatibility with
predecessor versions.
I would really appreciate if people in general learned BEFORE putting
systems live.
Cheers,
Matthias
Cheers,
Sam
On 21/12/2022 10:21 PM, Matthias Andree wrote:
Am 21.12.22 um 09:45 s
Am 21.12.22 um 09:45 schrieb Samer Afach:
Thank you for these hints, Benny. I wanna point out that I'm, in no
way, an expert in any of this, and my configuration is based on online
research and some copy/paste.
Then with all due respect, please shut down your mail server and do not
start it ag
Am 10.12.22 um 17:00 schrieb Matthias Andree:
The branch main has been updated by mandree:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=9e573ff0934a56d8eadd2c75be876b9392aae5b2
commit 9e573ff0934a56d8eadd2c75be876b9392aae5b2
Author: Matthias Andree
AuthorDate: 2022-12-10 15:58:03 +
Athos, just to make sure we do not misunderstand: there has been no word of
patches from me.
Any downstream backporting will be "pluck the commits from Git repo and
integrate them yourselves". I may answer questions, but I will not sort out the
SRU merge for Ubuntu Linux.
--
You received this
Re 1 - Ubuntu's packaging bug. It is the distributor's obligation to
properly integrate packages.
Re 2 - not a bug in fetchmail.
Re 3 - Yes, users can expect as much, but you are right that this is not
really viable because there is no such thing as a standard ftp(1). It is
not part of IEEE 1003.
Control: tags -1 +upstream +fixed-upstream +confirmed
Control: fixed -1 1.12.0
Please note that I have very recently released leafnode 1.12.0 which now
uses PCRE2 instead of PCRE1.
Also note that there is no longer a .bz2 package, only .xz and .gz.
https://sourceforge.net/projects/leafnode/fil
Does this warrant "grave"?
This looks like trying to configure fetchmailconf before fetchmail is
configured, and before fetchmail saw configuration. However why is
fetchmail being "restart"ed? It could not have been running before...
Does this warrant "grave"?
This looks like trying to configure fetchmailconf before fetchmail is
configured, and before fetchmail saw configuration. However why is
fetchmail being "restart"ed? It could not have been running before...
[resending from hopefully subscribed address that it makes it to some of
the lists]
Am 09.04.22 um 05:25 schrieb Kyle Evans:
Hello!
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching th
Am 17.02.22 um 10:10 schrieb Carlos Velasco:
Hi,
Trying to test latest postfix 3.7.0 with PCRE2 I have found a problem
in building documentation.
According to PCRE_README (http://www.postfix.org/PCRE_README.html),
pcre2-config is used:
"AUXLIBS_PCRE=`pcre2-config --libs`"
But "pcre2-config" do
Am 21.01.22 um 00:06 schrieb Wietse Venema:
Jaroslav Skarvada:
Hi,
it seems the following README files are not included in the conf/postfix-files:
BDAT_README
MAILLOG_README
POSTSCREEN_3_5_README
SMTPUTF8_README
Is it intended?
Yikes, these are all "new" files added with Postfix 3.x.
I'll ad
Am 18.01.22 um 20:25 schrieb Alex V. Petrov:
> Compressing man pages (compress-man)
===> Installing ldconfig configuration file
===> Installing for e2fsprogs-1.46.4_2
===> Checking if e2fsprogs is already installed
===> Registering installation for e2fsprogs-1.46.4_2
Installing e2fsprog
Am 17.01.22 um 22:27 schrieb Simon Schwarz:
I use dnsmasq in a docker environment based on this project:
https://github.com/jpillora/docker-dnsmasq
There the --no-daemon option is used which I replaced with
--keep-in-foreground and --log-facility=-
This seems to print all logs to stdout and std
elay announcements.
Unless you want to provoke losing quick mirrors, that is.
Now please keep calm and move on, there is nothing to see here.
Thanks in advance.
Regards,
Matthias Andree
(who has been using Postfix since long before it was called 1.0, 23-ish
years now, just sayin' I have been around for a while)
Am 02.01.22 um 17:11 schrieb Karsten:
Basically you can install the self-signed certificate (if you or a
trusted party signed it, and you have transmitted it over a secure
channel, for instance, via SFTP or SCP) into the trust store (assuming
it suits both the TLS server and the signing CA roles
Am 02.01.22 um 14:03 schrieb Karsten:
Am 02.01.22 um 12:15 schrieb Matthias Andree:
I am the owner of the domain so nobody is hijacked!
Are you the owner of "mydomain.de" or of the unnamed domain you intended
not to show to the public?
Do you want to help with this new certificat
Am 02.01.22 um 14:24 schrieb Karsten:
Am 02.01.22 um 12:28 schrieb Matthias Andree:
But it would be helpful for others what must be done to create and install this new
"client side certificate" that
appears about 2018?
I think the certificate issue was there right from the
Am 02.01.22 um 11:54 schrieb Karsten:
Am 01.01.22 um 17:53 schrieb László Böszörményi (GCS):
On Sat, Jan 1, 2022 at 2:30 PM Karsten wrote:
But it would be helpful for others what must be done to create and install this new
"client side certificate" that
appears about 2018?
I think the cert
Am 01.01.22 um 14:26 schrieb Karsten:
Hello Matthias,
Am 01.01.22 um 14:10 schrieb Matthias Andree:
Notice something?
i notice everything. :-)
You hijack somebody else's domain for "anonymization" purposes and
expect someone to help you, and you did not respond to hints
Happy new year Karsten.
Am 01.01.22 um 13:53 schrieb Karsten:
Hello Matthias,
Am 31.12.21 um 20:05 schrieb Matthias Andree:
What must be done to get it working again?
This question has not been answered.
[...]
The security relevant logdata is of course anonymized or altered.
Notice
Am 31.12.21 um 16:32 schrieb Karsten:
Package: fetchmail
Version: 6.4.16-4+deb11u1
Severity: important
I upgraded the server from Debian 9 to 11 and afterwards it seems not possible
to get fetchmail to work.
I tried every possible option of ssl and sslproto, but fetchmail can't fetch
the mail
Am 15.12.21 um 23:35 schrieb Benny Pedersen:
On 2021-12-15 23:04, raf wrote:
How could I get an Android client and a Postfix server work together
please?
It's just a guess, but maybe the problem is ECDSA.
If you add an RSA key as well, it might work.
Does that sound plausible?
or simply tr
or permissions (= restriction exceptions)
granted to OpenVPN that I have missed and am unaware of?
Any other license incompatibilities that the public should be aware of?
TIA
Matthias Andree
___
Openvpn-devel mailing list
Openvpn-devel@lists.source
Am 24.11.21 um 18:56 schrieb László Böszörményi (GCS):
It would be best if upstream integrates it to the source code. Even
if 6.4.25 is just around the corner.
After some discussion behind the scenes, added to contrib/systemd/ as of
6.4.25.rc2, without installation support.
It should be easy e
Am 07.11.21 um 13:13 schrieb Arne Schwabe:
Am 07.11.21 um 12:57 schrieb Matthias Andree:
Am 07.11.21 um 10:01 schrieb Arne Schwabe:
We already removed the check in d67658fee for OpenSSL 3.0. This
removes the
checks entirely for all crypto libraries.
Signed-off-by: Arne Schwabe
---
src
Am 07.11.21 um 10:01 schrieb Arne Schwabe:
We already removed the check in d67658fee for OpenSSL 3.0. This removes the
checks entirely for all crypto libraries.
Signed-off-by: Arne Schwabe
---
src/openvpn/crypto.c | 15
src/openvpn/crypto_backend.h | 28 ---
src
Am 17.10.21 um 22:04 schrieb Oskari Pirhonen:
> On Sun, Oct 17, 2021 at 08:31:41PM +0100, Claus Assmann wrote:
>> Why don't you use a wrapper which invokes
>> clear
>> after mutt finished? No extra code needed in mutt.
> Wow, I can't believe I didn't think of that *facepalms*.
>
> Thanks for the ti
Just a word of warning, this isn't your pick three git commits with
trivial fixes - the backport will require proper testing, too, and it
will require some of the 42 patches since fetchmail 6.4.21 that are NOT
marked SECURITY - for instance, 74771392 and 616e8c70, and translation
updates as they ar
Am 27.08.21 um 21:00 schrieb Antonio Quartulli:
> OpenVPN shipped a small packet filtering tool called PF. It has never
> been straightforward as it required a plugin to work. On top of that,
> keeping PF support, makes the code more complicated and increases the
> maintenance cost of OpenVPN.
>
>
On Wed, 18 Aug 2021 19:20:01 +0200 Matthias Andree
wrote:
> The attached patch should fix the crash. envelope is special in that it
> can take the value STRING_DISABLED == (char *)-1 for "no envelope", and
> the optmerge() function did not take this into account and tried to
&
The attached patch should fix the crash. envelope is special in that it
can take the value STRING_DISABLED == (char *)-1 for "no envelope", and
the optmerge() function did not take this into account and tried to
strdup(-1).
This will likely become part of a future 6.4.22 and 6.5.0 release.
diff
Am 08.08.21 um 15:02 schrieb Ed W:
> On 19/07/2021 18:52, Ed W wrote:
>> Hi, around 2.82 someone posted a little patch to import the config files in
>> dictionary order, which
>> is very useful for situations where you have overlapping definitions. I'm
>> using an addn-hosts stanza
>> pointing to
Am 03.08.21 um 12:43 schrieb Greg Wickham:
>
>
>
> Hi,
>
>
>
> I inadvertently left a “tag:” off a “dhcp-boot=“ line which resulted
> in dnsmasq crashing.
>
>
>
> This was the line that caused Dnsmasq to crash:
>
>
>
> dhcp-boot=tag:ww3001,UEFI,/ipxe.efi,10.109.0.1,10.109.0.1
>
>
>
> The
I was proposing preconnect, not plugin. -> comment #2. There is also
postconnect in fetchmail.
You may need to script interfaces with delay and readiness checks. As written
before, daemon management is out of fetchmail's scope. Fetchmail is not going
to turn into another systemd.
Again, fetchm
Lucas, it is still a support request rather than a feature request since
the feature is already there - but unsuitable for the use case. That's
why I marked it invalid already. It makes no sense to burden
distributions with feature requests because users are unaware of
existing features for rare
Also, if you really must shoot your feet and knees at the same time,
fetchmail has a "preconnect" directive, too. See the manual.
** Changed in: fetchmail (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bill,
judging from the hydroxide webpage, all you need to do is make sure that
hydroxide is running properly and then you can tell fetchmail to use
that port 1143 to fetch through.
You may need to use the "via" keyword in a fetchmail configuration file
(it is not available through the command lin
Am 18.07.21 um 04:14 schrieb Kubilay Kocak:
> On 18/07/2021 4:35 am, Philipp Ost wrote:
>> Hi ports@,
>>
>> graphics/gdal seems to have fallen through the cracks of the recent
>> Imath update. It is not included in the list of ports in commit
>> 3cda93bdf69bfb4ea99181e638e661c467dad38d.
>>
>> Compi
Bill,
I can sense quite a deal of frustration on your end, and am sorry for
that. I should have mentioned to also look into the NEWS file, which at
least would have told you that sslcertck is now the default.
Fetchmail's -vv verbose mode might also try to log more details on the
decisions along t
Bill,
as to your report, I'll break it down along the same bug numbers.
Note I am speaking as the upstream maintainer here and am unaware of Ubuntu's
Bug #1. Fetchmail behaves properly. You requested some sslproto on a
non-wrapped port (i. e. no "ssl" option), so fetchmail tries STARTTLS
instea
Am 22.03.19 um 12:55 schrieb Graeme Vetterlein:
> Package: fetchmail
> Version: 6.3.26-3
> Severity: minor
> Tags: patch
>
> Dear Maintainer,
>
>
> I've just hit an "issue" WRT fetchmail, which I now relaise I hit about 10
> years ago and didn't report
> (shame on me) the "fix" is a simple text ed
Am 13.06.21 um 01:16 schrieb bob prohaska:
> On Sat, Jun 12, 2021 at 01:26:16PM -0700, Jose Quinteiro wrote:
>> On 6/12/21 10:57 AM, bob prohaska wrote:
>>> Trying it now, hoping to see parallel core use.
>> You won't. Setting PARALLEL_JOBS=1 means exactly one Poudriere worker
>> will run, and that
Am 12.06.21 um 19:29 schrieb bob prohaska:
> In playing with poudriere on raspberry pi 3 and 4 it seems to
> work well on the 8 GB Pi4 but is over-optimistic on the 1 GB Pi3.
>
> Can poudriere be configured to tackle packages one at a time?
Sure, the easiest to try is poudriere bulk -J1 ... (capit
sd.org/bugzilla/show_bug.cgi?id=256331
Fixes: Trac #1409
Reported-by: p...@nethead.se (to FreeBSD)
Signed-off-by: Matthias Andree
---
src/openvpn/options.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/openvpn/options.c b/src/openvpn/options.c
index 8d417206..a54bc562 100644
--
Am 25.04.21 um 00:29 schrieb Steffen Nurpmeso via Dnsmasq-discuss:
> Steffen Nurpmeso wrote in
> <20210422212628.esxga%stef...@sdaoden.eu>:
> |Since a few weeks ago i sometimes see mail delivery from a few
> |domains (most often: mx2.freebsd.org, lesser so netbsd.org,
> |ietf.org, crux.nu) bein
Bill, fetchmail relies on the system resolver so if that cannot resolve
.onion hosts, that's bound to fail. You are not telling fetchmail to
avoid name resolution.
Please provide information how exactly and which fetchmail version fails
in your << poll underwood2hj3pwd.onion plugin "socat STDIO
S
Bill, in your threat scenario, I think it best to avoid the daemon mode
altogether, and then just use some external random delay tool (possibly
some script language one-liner) to delay a one-shot fetchmail run.
You can always set up separate directories, for instance, by way of the
FETCHMAILHOME v
Bill, thanks for the proposal. I'll answer as upstream maintainer. The
former fetchmail maintainer, Eric S. Raymond, years go, decided against
this feature ("do one job well"), but I am open to it.
Technically however I need to change the .fetchids format, so this is
release 7.0 business, meaning
ics/ilmbase) [Matthias Andree]
> * 398a42d37ac6 2021-04-10 | graphics/openexr: update to 3.0.1
> [Matthias Andree]
> * e9f871d1473e 2021-04-11 | UPDATING: Document OpenEXR/Imath 3.0.
> [Matthias Andree]
> * 50731b13c882 2021-04-11 | devel/kf5-extra-cmake-modules: make
> compatible
Am 12.04.21 um 10:33 schrieb Koichiro Iwao:
> On Mon, Apr 12, 2021 at 10:18:20AM +0200, Antoine Brodin wrote:
>> On Mon, Apr 12, 2021 at 10:05 AM Koichiro Iwao wrote:
>>>
>>> The branch main has been updated by meta:
>>>
>>> URL:
>>> https://cgit.FreeBSD.org/ports/commit/?id=f9568249d15022f2ce6a2
Am 30.03.21 um 09:04 schrieb dk8kk:
> Package: fetchmailconf
> Version: 6.4.0~beta4-3+deb10u1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
>
> Dear Maintainer,
>
> apt-get update/apt-get upgrade suggests these package for upgrade:
> - fetchmail (6.4.0~beta4-3+deb10u1)
>
Am 30.03.21 um 09:04 schrieb dk8kk:
> Package: fetchmailconf
> Version: 6.4.0~beta4-3+deb10u1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
>
> Dear Maintainer,
>
> apt-get update/apt-get upgrade suggests these package for upgrade:
> - fetchmail (6.4.0~beta4-3+deb10u1)
>
Am 25.03.21 um 20:57 schrieb Antonio Quartulli:
> Hi,
>
> On 25/03/2021 20:29, Matthias Andree wrote:
>> I find the reasons you present to withdraw the symmetric non-TLS mode
>> too weak to justify its deprecation or removal. Yes, TLS-based
>> configurations may be more
Am 25.03.21 um 01:01 schrieb Arne Schwabe:
> The non-TLS mode is a relict from OpenVPN 1.x or 2.0. When tls mode was
> introduce the advantages of TLS over non-tls were small but tls mode
> evolved to include a lot more features. (NCP, multipeer, AEAD ciphers to name
> a few).
>
> Today VPN that us
Am 24.03.21 um 23:11 schrieb Matthias Andree:
> Am 24.03.21 um 22:50 schrieb Dan Mahoney (Ports):
>
>> There are packages for mailman3 but they’re incomplete and don’t
> result in a working install the way the 2.x build does. You also need
> mysql, django, etc etc.
>
>
Am 25.03.21 um 16:03 schrieb Baptiste Daroussin:
>
> I really think we should as a project move forward to that direction, it does
> not even need to be driven by protmgr or even drive by any @freebsd.org
>
> I would argue here that it is even more interesting to go the gentoo way try
> to
> provi
1 - 100 of 3727 matches
Mail list logo
