Hello Werner,
the above is an excerpt from the exim log, I do not think the full bounce is more enlightening, vsrv21575.customer.vlinux.de got 550 from ellsberg.gnupg.com after " MAIL FROM:<ametzler@bebt.de>":
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 13 2024
Mar 10 2024
The mail server is misconfigured. no SPF <> not allowed.
Mar 9 2024
Dec 13 2023
Sorry for the fallout and thank you for taking care of it.
Dec 1 2023
Dec 14 2022
In T6309#166019, @ametzler1 wrote:Missed some, will post an updated patch.
Dec 13 2022
Missed some, will post an updated patch.
Dec 12 2022
Nov 29 2022
In T6285#165459, @gniibe wrote:Now, the use of AM_PATH_GPGME_PTHREAD shows warning. Also I update the documentation.
Nov 27 2022
Something like this?
Nov 25 2022
In T6288#165435, @werner wrote:Bootstrapping is an issue. Recall that pkg-config is not a simple program but requires the use of glib (which depends on libffi, libmount, libpcre) - catch-22. Makes building GnuPG on AIX not actually easy.
FWIW I would vote for a) "document gpgrt-config in detail" and suggest using pkg-config (variant) for direct invokations. There seems to be little benefit in investing effort/complicating gpgrt-config when pkg-config works fine.
Nov 22 2022
thank you, works for me.
Thank you, looks good to me.
Nov 13 2022
Oct 26 2022
@gniibe - Thanks for the quick response. It now works for me.
cu Andreas
Oct 25 2022
the pushed fix breaks when libgpg-error does not require special CFLAGS, i.e. when @GPG_ERROR_CFLAGS@ expands to an empty string:
Sep 7 2022
bernhard added a comment.Mon, Sep 5, 6:05 PM
If it is was broken for you and works now, let us know here. if "lists." still is there in email addresses somewhere, please also list.
Feb 9 2022
In T5816#154715, @ikloecker wrote:Try gcrypt-devel@gnupg.org, i.e. without the lists subdomain.
Recently, the gnupg.org mailing list manager started to prepend the lists. subdomain to the List-Id (which caused my email filters to fail) and to everything else. Probably due to an accidentally changed configuration.
Feb 8 2022
Feb 5 2022
Sep 4 2021
This works for me:
Aug 30 2021
Jun 22 2019
This bug has been assigned CVE-2019-12904. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12904
Jun 1 2019
gniibe wrote: