[mailop] AOL list mail delivery

Greetings, I run a few small (1000 users or less) e-mail lists. I have the lists on Mailman, set up with the DMARC options (From address is the list, Reply-To is the actual sender) and up until recently everything has worked fine. Lately, however, I sometimes have all my AOL users mail fail

Re: [mailop] What are "printing ASCII characters" RFC 850/2822 (was: Re: Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"))

On 09-06-17 18:19, Johann Klasek wrote: On Fri, Jun 09, 2017 at 04:22:56PM +0200, Benoit Panizzon wrote: [..] So I'm trying to figure out, if lotus notes is wrong, or amavis being too picky? Not so easy... If I browse the RFC regarding Message ID and SMTP, I basically get the not so clear

Re: [mailop] What are "printing ASCII characters" RFC 850/2822 (was: Re: Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"))

On Fri, Jun 09, 2017 at 04:22:56PM +0200, Benoit Panizzon wrote: [..] > So I'm trying to figure out, if lotus notes is wrong, or amavis being > too picky? Not so easy... If I browse the RFC regarding Message ID and > SMTP, I basically get the not so clear definition, that "all printable > ASCII

Re: [mailop] DMARC forensic reports

> On Jun 8, 2017, at 5:58 PM, John Levine wrote: > > In article <9bd40d9d-1c4f-4859-8169-d270d2811...@wordtothewise.com> you write: >>> https://dmarcian.com/dmarc-status/ >> >> That doesn’t distinguish between forensic and summary reports,

Re: [mailop] What are "printing ASCII characters" RFC 850/2822 (was: Re: Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"))

Eh? I've not seen that, somehow The typical notes message id is something like this - this is from an ancient version but the format hasn't changed Message-ID: --srs > On 09-Jun-2017, at 7:52 PM, Benoit Panizzon

Re: [mailop] What are "printing ASCII characters" RFC 850/2822

ASCII is 7-bit encoding, it means there can not be ASCII characters with values above 127. 09.06.2017 17:22, Benoit Panizzon пишет: > Hello > > Thank you for the replies suggesting that the problem could be caused > by an amavis virus scanner. That was bullseye :-) > > Indeed, amavis at

[mailop] What are "printing ASCII characters" RFC 850/2822 (was: Re: Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"))

Hello Thank you for the replies suggesting that the problem could be caused by an amavis virus scanner. That was bullseye :-) Indeed, amavis at recipioents site generates a delayed bounce, which is then sent directly to the MX of the sender and thus bypassed my sniffing between our filter and

Re: [mailop] Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"

Hi, Benoit, On 09-06-17 09:30, Benoit Panizzon wrote: Hello We have a 'challenging' problem between two companies sending each other emails. The sender keeps getting notifications, that his emails to the recipient are delayed. But this is not true. Analyzing the email headers the recipient

Re: [mailop] Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"

Hi Benoît, A lot more than ISPConfig has that error string. For example, I've encountered it from an site using Amavisd in response to invalid MIME encoding in a campaign. I'd be looking at the actual originating message to see if there are any obvious abnormalities with it, such as duplicate

[mailop] Lotus Notes and "250 2.6.0 Bad message, but will be delivered anyway"

Hello We have a 'challenging' problem between two companies sending each other emails. The sender keeps getting notifications, that his emails to the recipient are delayed. But this is not true. Analyzing the email headers the recipient sent me I can confirm, the emails take about two seconds!