Thanks for the references. Yes, it is indeed puzzling. Here is a snippet of
the DSNs I get:
UNDELIVERABLE MAIL
Your message to the following recipients cannot be delivered:
a...@domain.tld:
smtp.svc.telus.net [199.185.220.249]:
DATA
552 5.2.0 Invalid 7bit
Sam Varshavchik writes:
BOFHBADMIME was removed in 0.66.0
What's the behaviour of newer courier versions in case of bad mime messages?
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy
Lucio Crusca writes:
Sam Varshavchik writes:
BOFHBADMIME was removed in 0.66.0
What's the behaviour of newer courier versions in case of bad mime messages?
The message is accepted, on the presumption that 8-bit header content data
uses UTF-8. Nothing much really makes use of it, but
On Tue 09/Oct/2012 23:01:53 +0200 William Hue wrote:
Original messages with attachments (or, at least, 2+ MIME sections)
created by M$ LookOut! will usually generate Invalid 7bit data
errors, as will forwarding said messages (and the Invalid 7bit
data DSNs!) using Thunderbird. Creating a
In data martedì 9 ottobre 2012 01:55:49, Sam Varshavchik ha scritto:
Lucio Crusca writes:
Aruba mail services here are considered to be standard and working also
when they do not work, because many people use them. You can look at it
as if it were a de-facto standard.
If you're going to
Lucio Crusca writes:
I assume that opt MIME=8bit and Invalid 7bit data both refer to mime
encoding. Based on my assumption I guess that converting messages to 8bit
could workaround the errors from the remote mailserver, but... do you think
those assumptions are completely off-the-wall? Here
Sam Varshavchik writes:
Lucio Crusca writes:
I ask that because I already have opt BOFHBADMIME=accept in place, I
know that it implies opt MIME=none and I don't feel like changing it
if it hasn't
No, the two are independent settings. The first one controls what gets
accepted for
I just thought I'd add my two cents to this time wasting discussion:
I have been experience this same problem for about a year now with my ISP (one
of the big 3 in Canada). They upgraded their server software and I started
getting rejected messages with Invalid 7bit data. (Talk about trying
Lucio Crusca writes:
Sam Varshavchik writes:
Lucio Crusca writes:
I ask that because I already have opt BOFHBADMIME=accept in place, I
know that it implies opt MIME=none and I don't feel like changing it
if it hasn't
No, the two are independent settings. The first one controls what
I resume this old thread because I think now I have found a possible
workaround.
In data sabato 14 luglio 2012 05:11:51, Sam Varshavchik ha scritto:
Correct. This is an error message from the remote mail server.
and not Courier itself, I suspect
Lucio Crusca writes:
I resume this old thread because I think now I have found a possible
workaround.
In data sabato 14 luglio 2012 05:11:51, Sam Varshavchik ha scritto:
Correct. This is an error message from the remote mail server.
and not Courier itself,
In data lunedì 8 ottobre 2012 14:30:33, Sam Varshavchik ha scritto:
Well, since mail delivery for them is such a low priority, I see no reason
why anyone else has to be concerned, either.
Sure. However it happens I have two customers. The first buys email service
from me. The second buys
Lucio Crusca writes:
Aruba mail services here are considered to be standard and working also when
they do not work, because many people use them. You can look at it as if it
were a de-facto standard.
If you're going to waste your own time every time someone else's so-called
'de-facto
Hello *,
Courier 0.65/Debian, for a particular message, says:
---
UNDELIVERABLE MAIL
Your message to the following recipients cannot be delivered:
i...@domain.com:
mx.domain.com
Lucio Crusca writes:
i...@domain.com:
mx.domain.com [xx.xx.xx.xx]:
DATA
552 5.2.0 Invalid 7bit DATA
This happens while a user is trying to send a message with an attachment to
i...@domain.com, using Courier as outgoing SMTP server.
Is there anything I can do on the Courier
15 matches
Mail list logo
