Marc G. Fournier wrote:
> On Mon, 25 Apr 2005, John Fawcett wrote:
>
>> Sometimes I check what I'm discarding and only remember seeing spam.
>> That could explain the upward trend in these messages (in line with
>> the general increase in spam), although I've not seen that and have
>> too small nu
Hi!
I'm using cyrus-imapd-2.2.8-6.3 with success.
but I noticed that the cyr_expire is based on the Date header instead of the Internal email's
creation date
This cause me problem when I restored (from backup)+reconstruct some student emails which then just
get deleted again on next cyr_expire
Hello info-cyrus,
I'm completely tired by stupid users that violate RFC and send
e-mails with 8-bit characters in headers. I can do nothing with
those users, so our customers permanently receive some amount of
mail from "X" to "X" with subject "X X".
After all I make pat
On Thu, 28 Apr 2005, John Fawcett wrote:
Marc G. Fournier wrote:
On Mon, 25 Apr 2005, John Fawcett wrote:
Sometimes I check what I'm discarding and only remember seeing spam.
That could explain the upward trend in these messages (in line with
the general increase in spam), although I've not seen th
Derrick J Brashear wrote:
If anyone else wants to try this (I'd guess auth_unix use in mupdate
isn't common?)
I use saslauthd for authentication which then uses pam. Is there a way
to get rid of auth_unix ?
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
http://www.contrib.andrew.cmu.edu/~s
On Thu, 28 Apr 2005, John Fawcett wrote:
> Anyone know whether a patch for cyrus to strip out nuls would be
> welcome?
Make it clean, and optional (as in either reject the message, or remove the
NULs...), and I don't see why not. The default would need to be reject,
though.
But we really need to
On Thu, 28 Apr 2005, Igor Belikov wrote:
> After all I make patch, that adds option "ignore8bit" into
> imapd.conf. If this option set to "true" - Cyrus don't pay attention
> to 8-bit characters in headers at all, and our customers receive
> readable from, to and subject fields. If this opt
On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
On Thu, 28 Apr 2005, John Fawcett wrote:
Anyone know whether a patch for cyrus to strip out nuls would be
welcome?
Make it clean, and optional (as in either reject the message, or remove the
NULs...), and I don't see why not. The default woul
特惠邮址及软件 零售价（光盘EMS寄送）
网站下载
7800万分类邮件地址（地区、行业及服务器分类） 80元
50元
2200万2003-2005年最新邮件地址 80元
50元
60.2万股市论坛的会员邮址（送终身会员资格）280元
250元
1.2亿台湾详
Igor Brezac wrote:
>
> On Thu, 28 Apr 2005, John Fawcett wrote:
>
>> Marc G. Fournier wrote:
>>
>>> On Mon, 25 Apr 2005, John Fawcett wrote:
>>>
Sometimes I check what I'm discarding and only remember seeing spam.
That could explain the upward trend in these messages (in line with
Hello Henrique,
Thursday, April 28, 2005, 6:33:18 PM, you wrote:
HdMH> To the bitbucket, it will not be accepted.
[]
HdMH> So far, nobody that keeps complaining about the "X" things has taken the
HdMH> time to do the above.
I don't complain about "X", but I also have no time to do more
"correc
Igor Brezac wrote:
>
> On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
>
>> On Thu, 28 Apr 2005, John Fawcett wrote:
>>
>>> Anyone know whether a patch for cyrus to strip out nuls would be
>>> welcome?
>>
>>
>> Make it clean, and optional (as in either reject the message, or
>> remove the
On Thu, 28 Apr 2005, Igor Belikov wrote:
> I don't complain about "X", but I also have no time to do more
> "correct" modifications.
>
> Sorry.
Same here. So far, nobody stepped up to fix the issue properly, or offered
to pay, e.g. Ken to do it. So, "X" it is :-)
--
"One disk to rule them a
On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
But we really need to do something about the also non-RFC compliant crap
that sends too-big lines as well, cyrus screws up when breaking those lines.
Is that bug completely fixed yet?
No. If you have a suggestion for how to do it without touch
On Thu, 28 Apr 2005, João Assad wrote:
Derrick J Brashear wrote:
If anyone else wants to try this (I'd guess auth_unix use in mupdate isn't
common?)
I use saslauthd for authentication which then uses pam. Is there a way to get
rid of auth_unix ?
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAI
On Thu, 28 Apr 2005, John Fawcett wrote:
> postfix can do it with a content filter. I just wondered whether
> there was any chance of a patch being accepted in cyrus?
>
> I mean that would address the problem at it's root instead of
> working round it in n different MTAs.
You don't seem to get it
Derrick J Brashear wrote:
auth_unix's purpose is for groups, not for something pam will do for
you. technically if you're not using unix groups for access control
you don't need any of the group functionality. Really, though, I
should figure out what the getgr*_r interface difference which is
h
On Thu, 28 Apr 2005, John Fawcett wrote:
Igor Brezac wrote:
On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
On Thu, 28 Apr 2005, John Fawcett wrote:
Anyone know whether a patch for cyrus to strip out nuls would be
welcome?
Make it clean, and optional (as in either reject the message, or
re
Henrique de Moraes Holschuh wrote:
The correct place to do it is in the MTA. Doing it in the MTA means you get
the trash out before anything else has a chance to bounce it back, log it,
store it, or whatever.
Which doesn't mean I would be against a good patch for Cyrus, but I would
rather the MTAs
On Thu, Apr 28, 2005 at 03:14:22PM -0300, Henrique de Moraes Holschuh wrote:
> Which doesn't mean I would be against a good patch for Cyrus, but I would
> rather the MTAs started either fixing or rejecting all such crap worldwide.
> If exim, sendmail and postfix rejected broken messages, that would
On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
On Thu, 28 Apr 2005, John Fawcett wrote:
postfix can do it with a content filter. I just wondered whether
there was any chance of a patch being accepted in cyrus?
I mean that would address the problem at it's root instead of
working round it i
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> mupdate is self-forking. Start just one.
A reasonable suggestion, which does absolutely nothing to address
the issue of *why* such a behavior would happen.
Darrell
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http:/
On Thu, 28 Apr 2005, Amos wrote:
Maybe *ideally* it needs to be fixed by the MTA. However, just casually
following this list and the postfix-users list, whenever the issue of NUL
characters have come up, it has always been centered around Cyrus. I know
that there are folks using Postfix with oth
On Thu, 2005-04-28 at 14:57 -0400, Igor Brezac wrote:
> > that not every delivery agent/message store will reject NULs
> > so there is no need for the MTA to strip them out.
>
> So cyrus should also be broken?
I don't know if it's fair to say they're broken; conventional wisdom
says "be strict i
On Thu, 28 Apr 2005, Igor Brezac wrote:
They do not need to be patched, just configured correctly.
Please elaborate?
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---
Cyrus Home Page: ht
On Thu, 28 Apr 2005, Amos wrote:
Henrique de Moraes Holschuh wrote:
The correct place to do it is in the MTA. Doing it in the MTA means you
get
the trash out before anything else has a chance to bounce it back, log it,
store it, or whatever.
Which doesn't mean I would be against a good patch for
On Thu, 28 Apr 2005, Marc G. Fournier wrote:
On Thu, 28 Apr 2005, Igor Brezac wrote:
They do not need to be patched, just configured correctly.
Please elaborate?
Someone just mentioned that for postfix you can setup a content filter.
For sendmail, add '1' to your mailer flags. It is pretty simple
--On Thursday, April 28, 2005 16:22 -0300 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
Someone mentioned that this was, in fact, not forbid'd in the RFCs ...
could you point to the relevant RFC where it is? Considering how
'strict' postfix seems to be, having an RFC to back that up might show
Derrick J Brashear wrote:
On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
But we really need to do something about the also non-RFC compliant crap
that sends too-big lines as well, cyrus screws up when breaking those
lines.
Is that bug completely fixed yet?
No. If you have a suggestion fo
On Thu, 28 Apr 2005, Marc G. Fournier wrote:
> On Thu, 28 Apr 2005, Henrique de Moraes Holschuh wrote:
> >You don't seem to get it. The RFCs forbid NULs. What Cyrus is rejecting
> >may be anything, but an email it is not.
>
> Someone mentioned that this was, in fact, not forbid'd in the RFCs ...
--On Thursday, April 28, 2005 4:22 PM -0300 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
Someone mentioned that this was, in fact, not forbid'd in the RFCs ...
could you point to the relevant RFC where it is? Considering how
'strict' postfix seems to be, having an RFC to back that up might show
Andrew Morgan wrote:
Maybe I need to read back in this thread to remember, but what was the
suggested solution in Cyrus?
I think Cyrus is correct to bounce these messages back to the sender.
Accepting them seems somewhat dangerous. What happens when parts of
Cyrus or the IMAP protocol see a NU
--On Thursday, April 28, 2005 4:13 PM -0400 Joseph Brennan
<[EMAIL PROTECTED]> wrote:
--On Thursday, April 28, 2005 16:22 -0300 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
Someone mentioned that this was, in fact, not forbid'd in the RFCs ...
could you point to the relevant RFC where it is?
On Thu, 28 Apr 2005, David R Bosso wrote:
> So as before, it's illegal to send them.
Which means the MTAs have to accept *and strip* them, as forwading is just
an subcase of sending, IMHO.
Now, if the requirements for a spool (MDA) are the same as those for a MTA,
then Cyrus must accept and strip
On Thu, 28 Apr 2005, Darrell Fuhriman wrote:
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
mupdate is self-forking. Start just one.
A reasonable suggestion, which does absolutely nothing to address
the issue of *why* such a behavior would happen.
It's not even worth addressing the issue u
On 4/28/05, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
>
> What you *have* to do to get such a thing accepted is to, instead, write
> something that *fixes* the headers with the following capabilities:
>
> 1. Notion of a default source charset, which is a hint of the charset to
> e
On Fri, 29 Apr 2005, Adrian Buciuman wrote:
> Why not encode the header using unknown-8bit as the charset?? This is
> simpler, and has many advantages:
It still would cause problems for IMAP search. Well, mostly, as one could
just not index (and thus not search) any unknown-8bit headers at all...
Ahhh :o)
Thanks Eric. Still broken though. When I have:
virtdomains: on
defaultdomain: my.domain
cm [EMAIL PROTECTED] gives "createmailbox: Permission denied"
When I have:
virtdomains: userid
defaultdomain: my.domain
cm [EMAIL PROTECTED] gives "createmailbox: Permission denied"
Cunningly, when
It's pretty easy to stop messages with null characters if you use
Mimedefang, a milter. A built-in function called SuspiciousCharsInBody
tags messages with either nulls or bare CR or LF. We've let this go
but since we're testing a Cyrus server it looked like we should
stop them coming in.
We star
39 matches
Mail list logo
