Bug#678493: masqmail: prompting due to modified conffiles which were not modified by the user
[2012-06-23 11:39] Andreas Beckmann > On 2012-06-23 11:24, markus schnalke wrote: > > Surprisingly, the piuparts website reports the package to be successful: > > http://piuparts.debian.org/sid/source/m/masqmail.html > That's not an upgrade test. > > Look here (some time in the future, package is not yet tested, > dependencies are still queued): > http://piuparts.debian.org/testing2sid/source/m/masqmail.html Thanks a lot for the clarification. meillo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678493: masqmail: prompting due to modified conffiles which were not modified by the user
[2012-06-22 09:37] Andreas Beckmann > Package: masqmail > Version: 0.3.4-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, Thanks for your report. > during a test with piuparts I noticed your package failed the piuparts > upgrade test Surprisingly, the piuparts website reports the package to be successful: http://piuparts.debian.org/sid/source/m/masqmail.html Nevertheless, we're investigating and working on it. We appreciate the useful and details information you've provided. Thanks. meillo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654643: *** SPAM ***
tag 654643 moreinfo unreproducible thanks Olaf had told me in personal communication, that he would provide more information to the bug in order to enable me to reproduce it and to investigate. He wanted to do this one month ago. Unfortunately, he didn't yet. The bug is still as before: vague and unreproducible. Please, Olaf, provide more information! I really like to get rid of this RC bug. Especially, I like to be able to decide how serious it is for the users. I can't yet, unless I put lots of time into this (possibly not masqmail-concerning) issue. meillo FYI: We are currently preparing a new (and final) version of the 0.2 branch. Thereafter we are going to migrate the package to the 0.3 branch. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654643: masqmail: Silently discards mails when mbox exceeds 2 GiB
[2012-01-04 20:58]
>
> Dear Maintainer,
Hello Olaf,
I'm sorry to hear, you lost mail. I hope we can fix the bug soon.
Could you please provide additional information to speed the fixing up:
> I'm using masqmail -g to fetch email with pop3, and store them in a
> traditional mbox file. New mails silently ceased to arrive. (Luckly I
> discoverd this after irretrievably loosing "only" a bit more than 100
> mails...) It turns out my mbox reached a size of 2 GiB.
Which mbox is 2 GiB large: The remote one from which you fetch
(because you keep retrieved mails there) or the local one, to which
masqmail puts retrieved mails?
If it is the local mail box, is then the problem the same if you send
some message from the local system to this account? E.g.:
date | masqmail olaf
The point is: Does the problem sit in the POP retrieval code (get) or
in the local delivery code? It would be great if you can help to
identify the location.
> Not only does masqmail fail to store the mails: it doesn't even realize
> anything is wrong -- so there is no warning whatsoever, and the
> undelivered mails are purged from the queue.
The problem looks as if the size (in bytes) would be stored in some
signed 32bit data type. That would range until: 2,147,483,647.
Problems of this kind often fail silently.
meillo
P.S.
To explain my general point of view on masqmail:
The 0.2 branch of masqmail is dying out. It is only in a bug fixing
state. Development happens in the 0.3 branch, which, however is
changing to much to be suited to replace the 0.2-branch package in
Debian.
Newer versions of masqmail don't have the POP client anymore. If the
problem lies there, then my advice is clear: Use some other MRA
instead. Futur packages of masqmail in Debian will surely miss the POP
client. (Nontheless, I like to provide a quick fix in masqmail, too.)
If the problem lies in the local delivery, then the advice is similar.
I consider masqmail's local delivery code as a fall-back if you don't
have any better MDA available. If you have another one, than use it:
mda="/usr/bin/procmail -Y -d ${rcpt_local}"
(in masqmail.conf)
The other parts of masqmail are unlikely the cause of this bug.
Masqmail is a Mail Transfer Agent, which *transfers* mail. I believe,
that retrieval and local delivery are different tasks, that should be
covered by different, specialized programs. Such ones are readily
available. The classics are fetchmail and procmail.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638002: Fixed upstream in 0.2.30
tags 638002 fixed-upstream thanks The bug had been fixed in version 0.2.30. The relevant changeset is: http://hg.marmaro.de/masqmail/rev/e507c854a63e meillo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#541297: masqmail: diff for NMU version 0.2.21-7.1
[2009-11-28 11:38] gregor herrmann > > Dear maintainer, > > I've uploaded an NMU for masqmail (versioned as 0.2.21-7.1). The diff > is attached to this message. Thanks. meillo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
