Your message dated Wed, 13 Apr 2011 13:32:01 +0200
with message-id <[email protected]>
and subject line Re: [pkg-fetchmail-maint] Bug#593814: more information needed
has caused the Debian Bug report #593814,
regarding fetchmail starts too early in init scripts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
593814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593814
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fetchmail
Version: 6.3.17-4
Severity: grave
Justification: causes non-serious data loss

/etc/init.d/fetchmail has 
# Should-Start:      $mail-transport-agent exim4
but fetchmail starts very early and failed to deliver mails because 
The mail transport agent is not ready.
This issue could loss mails.
I suggest that /etc/init.d/fetchmail has :

1.
# Required-Start:    $network $local_fs $remote_fs $syslog $mail-transport-agent
# Required-Stop:     $remote_fs $mail-transport-agent

2.
Fetchmail does not need usually to start immediately after the boot. A delay
of few minutes (one ?) before the fetchmail start could improve security of 
delivering (for ie : to enable a good antispam starting).
.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fetchmail depends on:
ii  adduser               3.112              add and remove users and groups
ii  debianutils           3.4                Miscellaneous utilities specific t
ii  libc6                 2.11.2-2           Embedded GNU C Library: Shared lib
ii  libcomerr2            1.41.12-2          common error description library
ii  libgssapi-krb5-2      1.8.3+dfsg~beta1-1 MIT Kerberos runtime libraries - k
ii  libkrb5-3             1.8.3+dfsg~beta1-1 MIT Kerberos runtime libraries
ii  libssl0.9.8           0.9.8o-1           SSL shared libraries
ii  lsb-base              3.2-23.1           Linux Standard Base 3.2 init scrip

Versions of packages fetchmail recommends:
ii  ca-certificates               20090814   Common CA certificates

Versions of packages fetchmail suggests:
pn  fetchmailconf                 <none>     (no description available)
ii  postfix [mail-transport-agent 2.7.1-1    High-performance mail transport ag
pn  resolvconf                    <none>     (no description available)

-- Configuration Files:
/etc/default/fetchmail changed [not included]

-- no debconf information





--- End Message ---
--- Begin Message ---
Hi,
* Nico Golde <[email protected]> [2010-10-12 01:34]:
> * Alain Rpnpif <[email protected]> [2010-10-12 00:48]:
> > Le 12 octobre 2010, Nico Golde a écrit :
> > 
> > > please take the time to reply to my last questions. I will close the
> > > bug in a week if nothing happened until then.
> > 
> > Sorry for the delay.
> > With the original /etc/init.d/fetchmail, we have :
> > Should-Start:      $mail-transport-agent
> > It means that fetchmail start if the mail-transport-agent (postfix for
> > me) is not started. I experimented loss of mails in this case.
> > So I think that fetchmail **must** not start if the
> > mail-transport-agent does not work.
> > 
> > I suggest that the condition :
> > Required-Start: $mail-transport-agent
> > is notified in the /etc/init.d/fetchmail file.
> > 
> > Same kind of problem in /etc/resolvconf/update-libc.d/fetchmail.
> > Fetchmail is awaken too early when the network is not ready(localhost
> > setting is ready ?). It is the init logs in stdout that says that.
> 
> I understand your point, however like I wrote in my previous mail:
> From the documentation:
> "Should-Start: boot_facility_1 [boot_facility_2...] defines the facilities 
> that
> if present should start before the service provided by the script.
> Nevertheless, the script can still start if the listed facilities are 
> missing."
> 
> Are you sure you have a service installed that provide the 
> mail-transport-agent
> facility? If you do from my understanding this shouldn't happen.
> 
> You now mentioned that you are using postfix, I will look into the postfix
> package and see if I find anything that should prevent it. Thanks for your
> additional input.

I am closing this bug as it is invalid. Like explained it should be sufficient 
to have the mail-transport-agent facility in Shoul-Start. And the postfix 
package does also provide this: $mail-transport-agent postfix.
So I see no bug here.

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - [email protected] - GPG: 0xA0A0AAAA
For security reasons, all text in this mail is double-rot13 encrypted.

Attachment: pgpNnrjXw4Tkm.pgp
Description: PGP signature


--- End Message ---

Reply via email to