Group round robin email bouncing - any solutions?

Mr_Oink

This is a really simple fix. The sender is trying to send mail to ZERO2.co.uk (that is 02.co.uk) and not letter 'o'2.co.uk (o2.co.uk). Hence the relay warning as 02.co.uk is not a final destination on the o2.co.uk server ;-) Easy and very common mistake.

debitcardmayhem

usignuolo wrote: »

All very curious. I have checked the incoming emails they sent and all were sent or at least arrived with ZERO2 as the prefix. (This is how 0 appears on my PC and it is the character they have used.)

So now I have sent them a test message using O (Capital Letter O) and o (Lower case o) from my PC as well. Note difference in appearance of letter 0 and number O and 0).

I will just go and check if these have bounced........I'll be,,,,,it seems to have worked using the letter o and O. So why are the O2 users' emails arriving as 02 -all of them - and how come it isn't causing them problems with any other email servers? Are all O2 users equally deluded about the difference between 0 and O? You would think it would be a known problem.

I'll try it again in a minute to see if it really has worked but if so, please accept my grateful thanks. Who'd a thought it?

Usignuolo

O2(Ohhhh) and o(ohhhh)2 are the same in internet considerations same as
moneysavingexpert and mOneySavingexpErt are. 0(zero)2 and O2 and o2 are mapped to the same ip address, so perhaps that Tiscali help desk person may have been unkind to O(or o or 0)2 saying they wont resolve. It is possible that (O0o)2.co.uk IP address 82.132.141.84 is being being resolved by them(Tiscali,Pipex,Talk Talk .... lets not go there) as 02(not O2 nor o2) pure speculation there though, they(O0o) should (Oo0)2 have rules on their SMTP server to Transfer 0(zero)2 to O(o) really.

Oh dear or is that oh dear or 0 dear

Mr_Oink

They should, but they don't. There mx's are well known for only taking 'o2.co.uk'. Whilst o2,O2,02 all resolve to the same mx, the backend doing the recipient verification at their end usually only handles o2. There have been occasions where the data has been inserted incorrectly (oO02) and some recipients have had interesting side effects.

I've probably taken 500 calls on it in the last two years and whilst it is an irritation, the fix is plain and simple. Just use 'o2.co.uk' instead of 'O2.co.uk' or '02.co.uk'.

How it should work -v- how it does work are different things ;-)

debitcardmayhem

Mr_Oink wrote: »

They should, but they don't. There mx's are well known for only taking 'o2.co.uk'. Whilst o2,O2,02 all resolve to the same mx, the backend doing the recipient verification at their end usually only handles o2. There have been occasions where the data has been inserted incorrectly (oO02) and some recipients have had interesting side effects.

I've probably taken 500 calls on it in the last two years and whilst it is an irritation, the fix is plain and simple. Just use 'o2.co.uk' instead of 'O2.co.uk' or '02.co.uk'.

How it should work -v- how it does work are different things ;-)

Indeed but o0O2 should then take 2 minutes to change their sendmail.cf to transfer o0O2 to o2 and not just hit their relay rules to send out rejects. It is simples to change the name comparethemeerkats.com to comparethemarkets.com after hitting the spam filters, and before rejects. It is all down to following RFC822, if they want 02/o2/O2 to resolve to their servers then they should accept them.

johnmc

I use an Access database or Excel spreadsheet and mail merge.

Each email goes out individually, so 30 friends = 30 emails.

You can then personalise the email with "Dear OOO" or "Dear 000". This can get picked up as Spam though.

You do need to get your O's right, though.