MLMMJ Mailing List Manager
 help / color / mirror / Atom feed
From: Richard Torrens <Richard@Torrens.org.uk>
To: mlmmj@mlmmj.org
Subject: Re: FAQ and instructions?
Date: Mon, 04 Feb 2008 15:10:18 +0000	[thread overview]
Message-ID: <4f6be6277fRichard@Torrens.org.uk> (raw)
In-Reply-To: <4f66334953Richard@Torrens.org.uk>

In article <20080204105915.GO84525@mmj.dk>,
   Mads Martin Joergensen <mmj@mmj.dk> wrote:
> * Richard Torrens <Richard@Torrens.org.uk> [Jan 25. 2008 16:17]:
> > > > I ask because currently there's a mail stuck in moderation - it has
> > > > .sending appended - but has not been sent!
> > 
> > We have traced what happened here. In experimenting with subscribers,
> > I added a subscriber's email address to one of the subscribers.d
> > files. however, the file then did not have a \n terminator. So mlmmj
> > appended the next email address, getting a concatenated line with two
> > @ in it.

> Was there only \r, or was there one emailaddress in the file without a
> newline at the end?

Several email adresses. Last line did not have \n character

> > mlmmj promptly seized up! Including causing about 10 emails to
> > evaporate.

> Yikes ...

> > Dunno whether you consider that a bug, or even worth fixing. It's
> > fairly nasty, but is anyone else likely to hit it?

> It's definately worth fixing.

Then the check would be that the last char in the existing file is \n and
not an alpha!

> > Problems with files with or without \n are vague in my memory: RISC OS
> > uses the same line terminators as Unix, and we used to have programs
> > that did funny things if \n was absent. But that's so long gone, I
> > suppose I had assumed Linux also would not need care taken here!

> I never encountered it, I developed mlmmj mainly on FreeBSD with Linux
> testing as well.

RISC OS is slightly irrelevant to this: the teminal I use runs RISC OS,
connecting to the server via ssh or ftp. Server runs linux. Lots on the
www about RISC OS.

It's less mousing/keyboarding for me to download a subscriber file by ftp,
drag and drop an email address into it and upload it again. In this case 
it was only an email address, not a whole line, hence the problem!


  parent reply	other threads:[~2008-02-04 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 13:35 FAQ and instructions? Richard Torrens
2008-01-25 12:09 ` Morten K. Poulsen
2008-01-25 15:04 ` Richard Torrens
2008-02-04 10:59 ` Mads Martin Joergensen
2008-02-04 15:10 ` Richard Torrens [this message]
2008-02-06 10:51 ` Mads Martin Joergensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f6be6277fRichard@Torrens.org.uk \
    --to=richard@torrens.org.uk \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox