Skip to Content.
Sympa Menu

en - Re: [sympa-users] Cannot create problem

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Patrick von der Hagen <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] Cannot create problem
  • Date: Thu, 28 Aug 2008 17:20:01 +0200

Mark K schrieb:
> On Thu, 28 Aug 2008 12:07:16 +0200
> <address@concealed> wrote:
>
>> Hi
>>
>> Sympa spamming to /var/log/sympa cannot create
>> /var/sympa/bounce/listname@host/OTHER error. How can i fix this?
>>
>> Aug 28 13:03:30 myhost bounced[27048]: Cannot create
>> /var/sympa/bounce/listname@address@concealed|e.mx.mail.yahoo.com|216.39.53.1|f.mx.mail.yahoo.com|209.191.88.247|f.mx.mail.yahoo.com|209.191.88.247|g.mx.mail.yahoo.com|206.190.53.191|g.mx.mail.yahoo.com|206.190.53.191|a.mx.mail.yahoo.com|209.191.118.103|b.mx.mail.yahoo.com|66.196.97.250|c.mx.mail.yahoo.com|216.39.53.3|c.mx.mail.yahoo.com|216.39.53.3|d.mx.mail.yahoo.com|216.39.53.2|ns1.yahoo.com|66.218.71.63|ns2.yahoo.com|68.142.255.16|ns3.yahoo.com|217.12.4.104%22%2c
>> Aug 28 13:03:35 myhost bounced[27048]: error: no address found in
>> message from
>> "address@concealed|e.mx.mail.yahoo.com|216.39.53.1|f.mx.mail.yahoo.com|209.191.88.247|f.mx.mail.yahoo.com|209.191.88.247|g.mx.mail.yahoo.com|206.190.53.191|g.mx.mail.yahoo.com|206.190.53.191|a.mx.mail.yahoo.com|209.191.118.103|b.mx.mail.yahoo.com|66.196.97.250|c.mx.mail.yahoo.com|216.39.53.3|c.mx.mail.yahoo.com|216.39.53.3|d.mx.mail.yahoo.com|216.39.53.2|ns1.yahoo.com|66.218.71.63|ns2.yahoo.com|68.142.255.16|ns3.yahoo.com|217.12.4.104",
>> for list listname
>
> Sounds like a permissions problem.
>
> chown -R sympa:sympa /var/sympa/bounce
No, it doesn't.
Sympa sometimes generates wild filenames containing path-expressions
separated by "|" if it can't find an address to be used as a filename.

First, bouncequeue puts those files in spool/bounce, than bounced tries
to pick them up, parse them and move them to the new location. The new
filename (rarely) is somehow invalid and can't be created, so the file
is stuck in spool/bounce and is discovered and processed repeatedly by
bounced (which of course continues to fail).

Can't say why there is a problem in this particular incident. I did have
some examples once, which I intended to file as bug-reports, but it
somehow slipped.

However, address@concealed should still have that message and be able to
create a bug-report.

--
CU,
Patrick.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.19+.

Top of Page