Bug#1017936: linux-image-5.10.0-17-amd64: ILO4 remote console keyboard not working after upgrade to kernel 5 (buster to bullseye)
Package: src:linux Version: 5.10.136-1 Severity: normal Tags: upstream After upgrading from buster to bullseye, and so from kernel 4.X to kernel 5.x, ILO4 remote console keyboard stopped working. Hardware is an HPE ProLiant MicroServer Generation 8 with ILO4 version 2.80, which is the latest available on the HP support site. After a bit of investigation I found this to be related to IOMMU (which I don't even know what it is), with error messages like the following ones reported in dmesg after connecting to the ILO4 console: [ 57.124666] DMAR: DRHD: handling fault status reg 2 [ 57.124729] DMAR: [INTR-REMAP] Request device [01:00.0] fault index 15 [fault reason 38] Blocked an interrupt request due to source-id verification failure I tried setting "intel_iommu=off" on the kernel command line, using /etc/default/grub, following the somewhat related bug described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995773 Surprisingly in my case it made no difference. It was like the parameter was ignored, even though it was clearly reported in the dmesg boot log. To solve the problem I had to disable the IOMMU feature in the BIOS, as suggested near the end of the following page, again related to a different IOMMU problem: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04565693 I have to add that while investigating I found few other users reporting the same problem, or similar ILO4 console problems, also on different Linux distribution using kernel 5.X. Hope it helps. -- Package-specific info: ** Version: Linux version 5.10.0-17-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.136-1 (2022-08-13) ** Command line: BOOT_IMAGE=/vmlinuz-5.10.0-17-amd64 root=UUID=f03fef4f-108b-45d2-8ea1-205d13d4efac ro intel_iommu=off ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: HP product_name: ProLiant MicroServer Gen8 product_version: chassis_vendor: HP chassis_version: bios_vendor: HP bios_version: J06 ** Loaded modules: act_police sch_ingress cls_u32 sch_sfq sch_cbq pppoe pppox ppp_generic slhc nft_nat nft_chain_nat nf_nat nft_objref btusb ipmi_ssif btrtl btbcm intel_rapl_msr btintel intel_rapl_common bluetooth nf_log_ipv6 x86_pkg_temp_thermal nf_log_ipv4 jitterentropy_rng intel_powerclamp mgag200 nf_log_common drbg coretemp ansi_cprng nft_counter drm_kms_helper iTCO_wdt intel_pmc_bxt sg ecdh_generic ghash_clmulni_intel iTCO_vendor_support cdc_acm cec joydev hpwdt rfkill ecc evdev nft_log aesni_intel i2c_algo_bit hpilo watchdog libaes acpi_ipmi crypto_simd button ipmi_si ie31200_edac cryptd glue_helper ipmi_devintf nf_conntrack_sip nft_ct rapl nf_conntrack intel_cstate ipmi_msghandler acpi_power_meter nf_defrag_ipv6 serio_raw intel_uncore pcspkr nf_defrag_ipv4 nf_tables nfnetlink nfsd auth_rpcgss nfs_acl lockd grace sunrpc drm configfs fuse ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath linear raid1 md_mod hid_generic sd_mod t10_pi crc_t10dif crct10dif_generic usbhid uas usb_storage hid ahci crct10dif_pclmul xhci_pci crct10dif_common libahci xhci_hcd crc32_pclmul libata psmouse crc32c_intel uhci_hcd ehci_pci ehci_hcd scsi_mod lpc_ich tg3 usbcore libphy ptp pps_core usb_common ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback dns-nameservers 127.0.0.1 dns-search neomerica.lcl di.neomerica.lcl *** /etc/network/interfaces.d/eno1: auto eno1 allow-hotplug eno1 iface eno1 inet static address 192.168.3.254 netmask 255.255.255.0 network 192.168.3.0 broadcast 192.168.3.255 *** /etc/network/interfaces.d/eno2: auto eno2 allow-hotplug eno2 iface eno2 inet manual *** /etc/network/interfaces.d/ppp0: auto ppp0 iface ppp0 inet ppp pre-up /sbin/ifconfig eno2 up provider ppp0 ** Network status: *** IP interfaces and addresses: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 98:f2:b3:f7:14:94 brd ff:ff:ff:ff:ff:ff altname enp3s0f0 inet 192.168.3.254/24 brd 192.168.3.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::9af2:b3ff:fef7:1494/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 98:f2:b3:f7:14:95 brd ff:ff:ff:ff:ff:ff altname enp3s0f1 inet6 fe80::9af2:b3ff:fef7:1495/64 scope link
Bug#1017699: Please close
Sorry, sent by mistake without body, please close this bug. I already resubmitted as bug #1017697. -- Denis Sbragion
Bug#953411: upgrade-reports: Succesfull upgrade from stretch to buster, smooth for the most part
Package: upgrade-reports Severity: normal My previous release is: stretch I am upgrading to: buster Archive date: Upgrade date: 2020-03-07 uname -a before upgrade: forgot to record, sorry. It was stretch fully upgraded to 2020-03-07. uname -a after upgrade: Linux server 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux Method: strictly followed the upgrade procedure described in the buster docs. Upgraded directly from Internet. Contents of /etc/apt/sources.list: # Main packages deb http://deb.debian.org/debian/ buster main contrib non-free deb-src http://deb.debian.org/debian/ buster main contrib non-free deb http://deb.debian.org/debian-security buster/updates main contrib non-free deb-src http://deb.debian.org/debian-security buster/updates main contrib non-free # stretch-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free # Backports deb http://deb.debian.org/debian buster-backports main contrib non-free - Were there any non-Debian packages installed before the upgrade? If so, what were they? No - Was the system pre-update a pure stretch system? Yes - Did any packages fail to upgrade? No - Were there any problems with the system after upgrading? Yes, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953365 BTW this was solvable without much effort. Further Comments/Problems: This system has something like 25 GB of PostgreSQL databases, which is not so big by current standards. pg_upgradecluster took few hours to upgrade them to the buster version of PostgreSQL, which caused some unanticipated downtime. Probably it's time to consider some more efficient approach for PostgreSQL upgrades. PostgreSQL itself already include some faster tools but I think that keeping a distribution specific procedure, using the native PostgreSQL tools if needed, is a good thing. Apart from this few minor problems and the fixing some configuration files for some newer packages the upgrade was quite smooth and as expected. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#953365: php-horde-webmail: Problems with Horde Webmail and PostgreSQL after upgrading from Stretch to Buster (with workarounds)
Package: php-horde-webmail
Version: 5.2.22-3
Severity: important
Dear Maintainer,
after upgrading from Stretsch to Buster I was no longer able to login to
Horde as a normal user, getting errors like the following one:
PHP Fatal error: Uncaught Horde_Exception_PushApp: User denis is not
authorized for Horde (Host: 192.168.3.2). in
/usr/share/php/Horde/Registry.php:1583\nStack trace:\n#0
/usr/share/php/Horde/Registry.php(1193):
Horde_Registry->pushApp('horde', Array)\n#1
/usr/share/php/Horde/Registry.php(2117):
Horde_Registry->callAppMethod('horde', 'logout')\n#2
/usr/share/php/Horde/ErrorHandler.php(30):
Horde_Registry->clearAuthApp('horde')\n#3
/usr/share/horde/imp/lib/Application.php(620):
Horde_ErrorHandler::fatal(Object(Horde_Exception_AuthenticationFailure))\n#4
[internal function]:
IMP_Application->exceptionHandler(Object(Horde_Exception_AuthenticationFailure))\n#5
{main}\n thrown in /usr/share/php/Horde/Registry.php on line 1583,
referer: https://www.neomerica.lcl/horde/login.php
Login worked instead for the Horde administrator. After some
invesigation it turned out to be a permission problem, but I was unable
to properly operate on permissions because of the bug described here:
https://github.com/horde/Db/pull/1
After replacing the stock Schema.php with the GitHub version permissions
started working again and I was able to discover that the default
permission policy must have changed between the Stretch and the Buster
version of Horde.
It looks like in the Stretch version everything was permitted unless
explicitly forbidden, while in the Buster version it is the other way
around, so I had to manually create all the missing permissions to
restore all the functionalities.
Not a big deal, it just took few minutes, but probably adding some
warning to the upgrade procedure could save some time to others in the
same situation.
Hope it helps and keep up with the good work!
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages php-horde-webmail depends on:
ii php-cli2:7.3+69
ii php-common 2:69
ii php-horde 5.2.20+debian0-1+deb10u1
ii php-horde-content 2.0.6-3
ii php-horde-gollem 3.0.12-3
ii php-horde-imp 6.2.22-1
ii php-horde-ingo 3.2.16-3
ii php-horde-kronolith4.2.25-1
ii php-horde-mnemo4.2.14-3
ii php-horde-nag 4.2.19-1
ii php-horde-timeobjects 2.1.4-3
ii php-horde-trean1.1.9-3
ii php-horde-turba4.2.23-1
ii php7.3-cli [php-cli] 7.3.14-1~deb10u1
php-horde-webmail recommends no packages.
php-horde-webmail suggests no packages.
-- no debconf information
Bug#878219: mpd: Audible clicks while playing single flac + cue sheet
Package: mpd Version: 0.19.21-1 Severity: minor Dear Maintainer, the problem is fully described at: https://github.com/MusicPlayerDaemon/MPD/issues/113 There are sample files and graphs clearly showing the bug. After reporting the bug upstream I also tried to find the source of the problem in the mpd code, but had no success. I'm pretty sure there was once a similar problem with ape+cue files, which I think it has been fixed, so may be the cause it's the same. Unfortunately the bug report has been ignored upstream, even though I verified that the bug is present also with the testing mpd version (0.20.9). Nevertheless, I preferred to inform the Debian maintainers, so that you know about it if someone else complains about the same issue. May be also you have better luck getting the bug taken into account upstream. Thanks for your attention. Bye, Denis Sbragion -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mpd depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libadplug-2.2.1-0v5 2.2.1+dfsg3-0.4 ii libao41.2.2-1 ii libasound21.1.3-5 ii libaudiofile1 0.3.6-4 ii libavahi-client3 0.6.32-2 ii libavahi-common3 0.6.32-2 ii libavcodec57 7:3.2.7-1~deb9u1 ii libavformat57 7:3.2.7-1~deb9u1 ii libavutil55 7:3.2.7-1~deb9u1 ii libbz2-1.01.0.6-8.1 ii libc6 2.24-11+deb9u1 ii libcdio-cdda1 0.83-4.3+b1 ii libcdio-paranoia1 0.83-4.3+b1 ii libcdio13 0.83-4.3+b1 ii libcurl3-gnutls 7.52.1-5 ii libdbus-1-3 1.10.18-1 ii libexpat1 2.2.0-2+deb9u1 ii libfaad2 2.8.0~cvs20161113-1 ii libflac8 1.3.2-1 ii libfluidsynth11.1.6-4 ii libglib2.0-0 2.50.3-2 ii libgme0 0.6.0-4 ii libicu57 57.1-6 ii libid3tag00.15.1b-12 ii libiso9660-8 0.83-4.3+b1 ii libjack-jackd2-0 [libjack-0.125] 1.9.10+20150825git1ed50c92~dfsg-5 ii libmad0 0.15.1b-8 ii libmikmod33.3.10-1 ii libmms0 0.6.4-2 ii libmodplug1 1:0.8.8.5-3 ii libmp3lame0 3.99.5+repack1-9+b2 ii libmpcdec62:0.1~r495-1+b1 ii libmpdclient2 2.9-1 ii libmpg123-0 1.23.8-1+b1 ii libnfs8 1.11.0-2 ii libogg0 1.3.2-1 ii libopenal11:1.17.2-4+b2 ii libopus0 1.2~alpha2-1 ii libpulse0 10.0-1+deb9u1 ii libroar2 1.0~beta11-9 ii libsamplerate00.1.8-8+b2 ii libshout3 2.3.1-3 ii libsidplayfp4 1.8.7-1 ii libsmbclient 2:4.5.8+dfsg-2+deb9u1+b1 ii libsndfile1 1.0.27-3 ii libsoxr0 0.1.2-2 ii libsqlite3-0 3.16.2-5 ii libstdc++66.3.0-18 ii libsystemd0 232-25+deb9u1 ii libupnp6 1:1.6.19+git20160116-1.2 ii libvorbis0a 1.3.5-4 ii libvorbisenc2 1.3.5-4 ii libvorbisfile31.3.5-4 ii libwavpack1 5.0.0-2 ii libwildmidi2 0.4.0-2+b2 ii libwrap0 7.6.q-26 ii libyajl2 2.1.0-2+b3 ii libzzip-0-13 0.13.62-3.1 ii lsb-base 9.20161125 ii zlib1g1:1.2.8.dfsg-5 mpd recommends no packages. Versions of packages mpd suggests: pn avahi-daemon pn icecast2 ii ncmpcpp [mpd-client] 0.7.4-1+b3 pn pulseaudio -- Configuration Files: /etc/mpd.conf [Errno 13] Permission denied: '/etc/mpd.conf' -- no debconf information
Bug#659472: libdigest-sha1-perl still needed by mailscanner
Package: libdigest-sha1-perl Version: 2.13-2 Severity: important Dear Maintainer, a full upgrade ask to remove mailscanner because of dependencies on libdigest-sha1-perl. Here's the aptitude report: --- Server:~# aptitude full-upgrade The following packages will be upgraded: libcrypt-openssl-random-perl libdbd-sqlite3-perl libdbi-perl libfilesys-df-perl libhtml-parser-perl liblocale-gettext-perl libnet-dns-perl libnet-libidn-perl libnet-ssleay-perl libnetaddr-ip-perl libsocket6-perl libterm-readline-gnu-perl libtext-charwidth-perl libtext-iconv-perl libunicode-string-perl libuuid-perl libxml-parser-perl perl perl-base perl-modules razor 21 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 11.2 MB of archives. After unpacking 17.0 MB will be freed. The following packages have unmet dependencies: libdigest-sha1-perl: Depends: perlapi-5.12.3 which is a virtual package. The following actions will resolve these dependencies: Remove the following packages: 1) libdigest-sha1-perl 2) mailscanner Accept this solution? [Y/n/q/?] --- I already reported this problem as bug #651424 but so far got ignored. I read about the migration from Digest:SHA1 to Digest:SHA but looks like the mailscanner package haven't been upgraded yet. Looking at the mailscanner website it seems that mailscanner is already able to work with both packages, so probably it's just a matter of repackaging it. Thanks in advance. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdigest-sha1-perl depends on: ii libc6 2.13-26 ii perl5.12.4-4 ii perl-base [perlapi-5.12.3] 5.12.4-4 libdigest-sha1-perl recommends no packages. libdigest-sha1-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651424: mailscanner: Aptitude full-upgrade ask to remove mailscanner
Package: mailscanner Version: 4.79.11-2.2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I was trying to do a full-upgrade of the system. * What exactly did you do (or not do) that was effective (or ineffective)? aptitude update followed by: aptitude full-upgrade * What was the outcome of this action? I copy directly the aptitude messages: The following packages will be upgraded: libcrypt-openssl-random-perl libdbd-sqlite3-perl libdbi-perl libfilesys-df-perl libhtml-parser-perl liblocale-gettext-perl libnet-dns-perl libnet-libidn-perl libnet-ssleay-perl libnetaddr-ip-perl libsocket6-perl libterm-readline-gnu-perl libtext-charwidth-perl libtext-iconv-perl libunicode-string-perl libuuid-perl libxml-parser-perl perl perl-base perl-modules razor 21 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 11.2 MB of archives. After unpacking 17.0 MB will be freed. The following packages have unmet dependencies: libdigest-sha1-perl: Depends: perlapi-5.12.3 which is a virtual package. The following actions will resolve these dependencies: Remove the following packages: 1) libdigest-sha1-perl 2) mailscanner I'm not sure if it's a problem if libdigest-sha1-perl, perlapi-5.12.3 or mailscanner itsef, but aptitude insist on removing mailscanner. The package libdigest-sha1-perl is available in sid, but seems to have disappeared from wheezy. * What outcome did you expect instead? Usual system upgrade. I didn't include configuration files because I think it isn't a configuration issue, but I might supply them if needed. Thanks in advance, and keep up with excellent work! *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mailscanner depends on: ii debconf [debconf-2.0]1.5.41 ii libarchive-zip-perl 1.30-4 ii libconvert-tnef-perl 0.17-11 ii libdbd-sqlite3-perl 1.33-1 ii libdbi-perl 1.616-1+b1 ii libdigest-sha1-perl 2.13-2 ii libfilesys-df-perl 0.92-3+b2 ii libhtml-parser-perl 3.68-1+b1 ii libmailtools-perl2.08-1 ii libmime-tools-perl [libmime-perl]5.502-1 ii libnet-cidr-perl 0.14-1 ii libnet-dns-perl 0.66-2+b1 ii libnet-ip-perl 1.25-3 ii libole-storage-lite-perl 0.19-1 ii libsys-hostname-long-perl1.4-2 ii perl 5.12.4-4 ii sendmail-bin [mail-transport-agent] 8.14.4-2+b1 ii spamassassin 3.3.2-2 ii ucf 3.0025+nmu2 ii unzip6.0-5 Versions of packages mailscanner recommends: ii clamav 0.97.3+dfsg-1 ii clamav-daemon 0.97.3+dfsg-1 ii libnet-cidr-lite-perl 0.21-1 ii tnef 1.4.8-1 ii wget 1.13.4-1 Versions of packages mailscanner suggests: pn libmail-spf-query-perl none pn libnet-ldap-perlnone pn unrar-nonfree none -- Configuration Files: /etc/MailScanner/MailScanner.conf changed [not included] /etc/MailScanner/rules/spam.whitelist.rules changed [not included] /etc/MailScanner/spam.assassin.prefs.conf changed [not included] /etc/default/mailscanner changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626177: milter-greylist: Milter-greylist started after sendmail
Package: milter-greylist
Version: 4.3.8-1
Severity: minor
On startup the milter-greylist service is started after sendmail so sendmail
issue a warning:
WARNING: Xmilter-greylist: local socket name
/var/run/milter-greylist/milter-greylist.sock missing
Sendmail is later able to recover and greylisting works anyway, so this is just
a minor nuisance, but hopefully is also easy to fix.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.38-2-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages milter-greylist depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii libc62.11.2-11 Embedded GNU C Library: Shared lib
ii libmilter1.0.1 8.14.4-2+b1 Sendmail Mail Filter API (Milter)
ii libspf2-21.2.9-4 library for validating mail sender
Versions of packages milter-greylist recommends:
ii sendmail 8.14.4-2 powerful, efficient, and scalable
milter-greylist suggests no packages.
-- Configuration Files:
/etc/default/milter-greylist changed:
ENABLED=1
/etc/milter-greylist/greylist.conf changed:
pidfile /var/run/milter-greylist.pid
dumpfile /var/lib/milter-greylist/greylist.db 600
dumpfreq 10m
socket /var/run/milter-greylist/milter-greylist.sock
user smmsp
quiet
list my network addr { 127.0.0.1/8 192.168.2.0/24 192.168.3.0/24 }
list my friends addr { \
70.103.162.0/24\ # Debian Mail+Listservers. NEVER unwhitelist them.
140.211.166.0/24 \ # Debian Bugs
192.25.206.0/24\ # Debian web/cvs/people
194.109.137.218/32 \ # Debian security/www-master.d.o
}
list broken mta addr { \
12.5.136.141/32\ # Southwest Airlines (unique sender)
12.5.136.142/32\ # Southwest Airlines
12.5.136.143/32\ # Southwest Airlines
12.5.136.144/32\ # Southwest Airlines
12.107.209.244/32 \ # kernel.org (unique sender)
12.107.209.250/32 \ # sourceware.org (unique sender)
63.82.37.110/32\ # SLmail
63.169.44.143/32 \ # Southwest Airlines
63.169.44.144/32 \ # Southwest Airlines
64.7.153.18/32 \ # sentex.ca (common pool)
64.12.136.0/24 \ # AOL (common pool)
64.12.137.0/24 \ # AOL
64.12.138.0/24 \ # AOL
64.124.204.39 \ # moveon.org (unique sender)
64.125.132.254/32 \ # collab.net (unique sender)
64.233.160.0/19\ # Google
66.94.237.16/28\ # Yahoo Groups servers (common pool)
66.94.237.32/28\ # Yahoo Groups servers (common pool)
66.94.237.48/30\ # Yahoo Groups servers (common pool)
66.100.210.82/32 \ # Groupwise?
66.135.192.0/19\ # Ebay
66.162.216.166/32 \ # Groupwise?
66.206.22.82/32\ # Plexor
66.206.22.83/32\ # Plexor
66.206.22.84/32\ # Plexor
66.206.22.85/32\ # Plexor
66.218.66.0/23 \ # Yahoo Groups servers (common pool)
66.218.67.0/23 \ # Yahoo Groups servers (common pool)
66.218.68.0/23 \ # Yahoo Groups servers (common pool)
66.218.69.0/23 \ # Yahoo Groups servers (common pool)
66.27.51.218/32\ # ljbtc.com (Groupwise)
66.102.0.0/20 \ # Google
66.249.80.0/20 \ # Google
72.14.192.0/18 \ # Google
74.125.0.0/16 \ # Google
152.163.225.0/24 \ # AOL
194.245.101.88/32 \ # Joker.com
195.235.39.19/32 \ # Tid InfoMail Exchanger v2.20
195.238.2.0/24 \ # skynet.be (wierd retry pattern, common pool)
195.238.3.0/24 \ # skynet.be
195.46.220.208/32 \ # mgn.net
195.46.220.209/32 \ # mgn.net
195.46.220.210/32 \ # mgn.net
195.46.220.211/32 \ # mgn.net
195.46.220.221/32 \ # mgn.net
195.46.220.222/32 \ # mgn.net
195.238.2.0/24 \ # skynet.be (wierd retry pattern)
195.238.3.0/24 \ # skynet.be
204.107.120.10/32 \ # Ameritrade (no retry)
205.188.0.0/16 \ # AOL
205.206.231.0/24 \ # SecurityFocus.com (unique sender)
207.115.63.0/24\ # Prodigy - retries continually
207.171.168.0/24 \ # Amazon.com
207.171.180.0/24 \ # Amazon.com
207.171.187.0/24 \ # Amazon.com
207.171.188.0/24 \ # Amazon.com
207.171.190.0/24 \ # Amazon.com
209.132.176.174/32 \ # sourceware.org mailing lists (unique sender)
209.85.128.0/17\ # Google
211.29.132.0/24\ # optusnet.com.au (wierd retry pattern)
213.136.52.31/32 \ # Mysql.com (unique sender)
216.33.244.0/24\ # Ebay
216.239.32.0/19\ # Google
217.158.50.178/32 \ # AXKit mailing list (unique sender)
}
list
Bug#626177: milter-greylist: Milter-greylist started after sendmail
On Mon, May 9, 2011 18:43, Paul Martin wrote: I *suspect* that there's a chicken and egg situation: sendmail needs to be around for the milter to start. I'll need to check. Are you using the standard init? I'm using what has been installed by default, so I think everything is standard. As a further information, if I stop both services, then I manually restart milter-greylist first and then sendmail, it works. Doing it the other way around generates the warning. So probably the start sequence could be reversed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
