|
| |
Forum Tips
» This forum is for users to discuss their software problems and suggestions for improvement.
Remember that only a tiny percentage of our users experience such problems (To be precise less than 0.7% have ever posted on this forum)
» Include your software version number (as displayed in the About Box)
» Check the FAQ before posting as most common questions have already been answered
» You don't need to also e-mail us separately as our support team will respond to all questions on this forum
|
|
| Author |
 Topic  |
|
|
TheWebGuy
New Zealand
8 Posts |
Posted - Feb 03 2009 : 22:44:00
|
Hi,
I've found a couple of instances where I've not been able to validate or deliver mail through MLK (Internal SMTP server) even though I know an address exists and am able to deliver using another mail client.
I suspect it might be limited to addresses that being redirected to a 'catchall' account. Messages sent to these addresses time out at the 'Sending Message' stage in the message sending progress window.
Email addresses that have an associated POP3 mailbox are delivered without a problem. As soon as I change delivery method to use my ISP's SMTP server, problem emails are delivered immediately.
Am I missing any settings that force a check on delivery, or is there a tweak I can make to send to these problem addresses ?
Thanks,
Will. |
|
|
xequte
7504 Posts |
Posted - Feb 04 2009 : 14:20:22
|
Hi Will
Personally i think validation is of questionable value, because servers often mis-report an address as being valid when it is not, and some addresses are reported as unreachable but in fact are being blocked because you are checking from a local server (validation uses MLK's internal mail server).
In my opinion the only recommended way to "validate" your addresses is to enable the option to have MLK delete address after it bounces, say five times. Then you simply send to your mailing list is usual. If a message to a recipient bounces five times then you know that it is a bad address (and MLK will automatically remove them).
In our case I don't think it is due to a catchall account, but simply that the receiving server is blocking your connection for some reason (most likely rejecting it is coming from a local server). When you are sending via the Internal server you should enable the option to automatically resend to failed addresses and also specify that on the final send it goes via normal SMTP.
Nigel
Xequte Software
nigel@xequte.com |
 |
|
|
TheWebGuy
New Zealand
8 Posts |
Posted - Feb 05 2009 : 02:15:12
|
Thanks for the response, Nigel, and also for the inclusion of the SSL connection feature in the latest release. Works like a charm!
In this particular instance I've set up a bounce count of 3 before deleting, as you've suggested below, but I've also enabled the setting to process the bounce immediately when sending results in a bounce.
I'm not sure I understand the reason you give below, though. Do you mean that the recipient's server thinks that MLK's SMTP server is local to it, and is therefore blocking it ?
[quote]Originally posted by xequte
In our case I don't think it is due to a catchall account, but simply that the receiving server is blocking your connection for some reason (most likely rejecting it is coming from a local server). |
|
|
|
xequte
7504 Posts |
Posted - Feb 05 2009 : 02:30:24
|
Hi Will
Sorry, what I mean by a local mail server, is a mail server (such as MLK's) running on a personal computer, rather than one of an ISP or company. As a (somewhat heavy-handed) Spam prevention measure, some destination mail servers will block or flag messages that it determines have come from a personal computer.
For more detail please read the "If you use the Internal SMTP Server" section at:
http://www.xequte.com/support/maillistking/spamissues.html
Nigel
Xequte Software
nigel@xequte.com |
|
|
| |
Topic |
|
|
|
| |
Search
How does MLK validate 'catchall' email addresses ?
