Exchange Server guru wanted

Telford

Registered user
Joined
May 21, 2004
Messages
306
Reaction score
0
Location
LE16
Can anyone help with an SMTP problem on exchange server (on Small Business Server)?

Basically, email is collected from various POP3 mail servers and distributed to internal accounts. However, if the incoming email has other addresses in the To: or CC: lines the Exchange SMTP service redelivers them.

This has only happened since a re-install of SBS following a Microsoft Update induced dead box.

I have a microsoft support incident raised but they don't seem able to come up with a solution (already re-installed IIS, Exchange Server, Sevice packs and Hot fixes under their instruction).

Any hints, tips, ideas?

A commercial arrangement would be considered. (If allowed under site policy :chuck)

Mark
 
It's SBS 2000 with Exchange Server 2000 sp3.
Using POP3 for incomming mail and SMTP for outgoing.

I think the problem may now be sorted (or at least gone away for a while).

Basically, when a message was downloaded from the ISP and the message contained more than one recipient on the TO: line it would deliver the mails to the intended recipient internally but if the additional recipients were outside of the domain it would forward the mail on through SMTP - resulting in multiple copies for the other recipients and/or NDRs or 505 errors.

This was not an open relay per se as there is only firewalled access from outside and the standard telnet relay tests passed muster.

I think the problem was caused by the mail POP3 proxy incorrectly formatting the X-Envelope. Going back to the (basic) POP3 connector seems to have stopped the forwarding.

Thanks for the replies and PMs.

Mark
 
A bit OT, and you may have good reasons.......

but routing your mail from your ISP via POP3 is complete crap. You would be better off swapping it out for a SMTP feed, whether direct or etrn triggered.
 
>>You would be better off swapping it out for a SMTP feed, whether direct or etrn triggered.

Agreed.

It's a legacy situation with mail collected from 2 ISPs, a total of 12 POP3 accounts and some 'confusion' over domain mail routing. I need to rationalise the ISP and domain situation before getting the SMTP feed set up.
 
We struggled with SBS 2000 for a few years - it's not at all nice - I don't think Microsoft could be bothered to be honest!

4.5 was an excellent piece of kit, as is 2003, but I couldn't stand 2000 - unlike its predecessor or successor, 2000 just seemed to be several bits of server software botched together and sold in a single box, whereas 2003 and 4.5 combine coherent and easily manageable pieces of software, ideal for the average small business. 2003 in particular is much easier to manage (although it has its foibles too!).

I know it's a bit of an expense, but if you can manage it, 2003 is a much much better package in my opinion. Also - I found that once I got rid of ISA server my life was 10,000 times easier, we use a nice piece of firewall equipment instead and live in perfect harmony with our SBS box!

That said, whenever we had a problem, microsoft's support team couldn't be faulted, I've used them around five times in the past six years, and every single time they've cured my (often complex) problems with skill and efficiency.

Stuart.
 
650EssexBoy said:
We struggled with SBS 2000 for a few years - it's not at all nice - I don't think Microsoft could be bothered to be honest!

4.5 was an excellent piece of kit, as is 2003, but I couldn't stand 2000 - unlike its predecessor or successor, 2000 just seemed to be several bits of server software botched together and sold in a single box, whereas 2003 and 4.5 combine coherent and easily manageable pieces of software, ideal for the average small business. 2003 in particular is much easier to manage (although it has its foibles too!).

I know it's a bit of an expense, but if you can manage it, 2003 is a much much better package in my opinion. Also - I found that once I got rid of ISA server my life was 10,000 times easier, we use a nice piece of firewall equipment instead and live in perfect harmony with our SBS box!

That said, whenever we had a problem, microsoft's support team couldn't be faulted, I've used them around five times in the past six years, and every single time they've cured my (often complex) problems with skill and efficiency.

Stuart.

Got to agree with that, funny how it goes with Microsoft and SBS, it does not seem to be a product line which has much attention, but a lot of companies use it. 4.0 was an utter 'mare mind you, but 2003 seems quite good. The ISA server is not the best though, I quite agree that an external firewall, like a Watchguard, is the better way to go. I've only had to call the support team once, with a 4.0/Exchange problem some years back, and they sorted me out.
 
SBS :barf

v4 was a complete nightmare.. v4.5 worked ok. Not used the latter ones.

TBH, SBS goes against all practical advice when it comes to servers by chucking all these large systems onto a single box.

If at all possible I'd stay well clear.
 


Back
Top Bottom