Bulkmail job not being accepted by list server

Squiz Matrix Support
1

I’m having a problem with an e-newsletter and I was hoping somebody else might have encountered the same problem and found a solution they'd like to share…


We use a combination of the Matrix Bulkmail functionality and a Lyris list server to send out e-flyers and e-newsletters to subscribers. We build the documents as HTML within Matrix, then use a Bulkmail Job to send them to an appropriate Lyris list, which handles their distribution to the list subscribers.



Most of our e-flyers have worked reasonably well. However, we’re about to send out the first issue of an e-newsletter, which is a much longer and more complicated document, in terms of the underlying code. It involves about 3 levels of nested tables, for instance. Its overall structure is of a table with two columns, with main content (most of which is in a series of tables) in the left column and feature content (also a series of tables) in the right column. And we’ve been finding that, while Matrix would send it okay, it just wouldn’t arrive at Lyris, or be accepted by it.



We found that the only way to ensure the document would be accepted by Lyris was to delete some of the content, thereby shortening the length of the document a bit. It sort of suggests there might be a character limit on the HTML code – but we can’t find anything about such a limitation in the list server’s documentation, or on the web, etc.



So my question is, has anybody else had a similar problem with getting a list server to accept an HTML-format email from the Matrix bulkmail facility – and if they have, were they able to work out how to circumvent it?



I hope that made sense. Many thanks for any help, all.



Steve S

2

It's okay, we've managed to get it to work after all.


It looks like it was a single, solitary sentence in the e-newsletter that must have looked to our mail server like spam, so it was preventing the email from actually reaching our list server. Once the errant sentence was removed, there was no longer a problem, and it reached the list server every time. Whew.



Cheers, all.



Steve S