On Wed, 12 Mar 2003, Jerry Amundson wrote:
>
> I also refuse to make it easy for the sloppy, anarchist developers of
> the world to propagate their crap. Such misdeeds can only lead to
> complete chaos and system meltdown. I'm sure there is an expert in Chaos
> Theory out there that can back me on
Hi,
Why it is so hard to code simple thing? If your want to interoperate -
follow the standards. Simple, no? Standards might be badly engineered,
but that's another story.
The same thing happened to html. I am not talking about tags or
atributes available only on specifict browsers. I am talking
- Original Message -
From: "Jesse Cablek" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 12, 2003 10:10 AM
Subject: Re: [courier-users] RFC compliance: goodbye to courier MTA
> Gregor Lawatscheck wrote:
> [...]
> > an ISP
Gregor Lawatscheck wrote:
[...]
an ISP should have to hack it to get full compatibility with all the
flawed clients around.
[...]
As good as this may be, it only promotes the flawed clients to not be
fixed, because what they use, works. I wouldn't want any software that
promotes the use of non
Eduardo Roldan wrote:
Please tell us what are the top problems you face with your customers
caused by the strict RFC compliance of Courier.
I apologize. Thomas gave me the right solution
opt BOFHBADMIME=accept(without spaces between '=' and accept!!!)
in /etc/courier/bofh
and that solved m
On 11/03/03 17:19, "Giovanni Panozzo" <[EMAIL PROTECTED]> wrote:
> Thomas von Hassel wrote:
>
>>>
>>
>> I must say i have no problems with receiving mail, even badly formatted
>> ones, with courier. All that can be turned off if you want to ?
>>
>> /thomas
>
> Maybe I forgot something about t
On Tue, 2003-03-11 at 09:19, Giovanni Panozzo wrote:
> After two years of courier MTA/IMAP use in a ISP (1k mailboxes),
> we learned that being so RFC compliant
> is only a big cost for us, in terms of helpdesk calls and
> customer unsatisfaction, so we are truly considering to
> change again our M
PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Giovanni
Panozzo
Sent: Tuesday, March 11, 2003 4:19 AM
To: [EMAIL PROTECTED]
Subject: [courier-users] RFC compliance: goodbye to courier MTA
After two years of courier MTA/IMAP use in a ISP (1k mailboxes),
we learned that being so RFC compliant
is only a bi
Thomas von Hassel wrote:
I must say i have no problems with receiving mail, even badly formatted
ones, with courier. All that can be turned off if you want to ?
/thomas
Maybe I forgot something about turning off errors... how ?
One year ago I removed ERR8BITCONTENT as specified in the FAQ.
The
On Tuesday, March 11, 2003, at 01:19 PM, Giovanni Panozzo wrote:
After two years of courier MTA/IMAP use in a ISP (1k mailboxes),
we learned that being so RFC compliant
is only a big cost for us, in terms of helpdesk calls and
customer unsatisfaction, so we are truly considering to
change again ou
At 12:19 11/03/2003, you wrote:
Just one thought read RFC 1958, paragraph 3.9
3.9 Be strict when sending and tolerant when receiving.
Implementations must follow specifications precisely when sending to
the network, and tolerate faulty input from the network. When in
doubt, discard
After two years of courier MTA/IMAP use in a ISP (1k mailboxes),
we learned that being so RFC compliant
is only a big cost for us, in terms of helpdesk calls and
customer unsatisfaction, so we are truly considering to
change again our MTA (not the IMAP/POP3 server).
Just one thought read RFC 19
12 matches
Mail list logo
