Cant send email using IMAP in Exchange 2003


hello,
I have got 1 front end exchange server 2003 and 2 backend mail servers.
The problem is very unusual I have got few IMAP users they all can send and recieve email using IMAP.
I am a sys admin and i was able to send email using IMAP with my domain admin group membership but once i am out of domain admin
membership i cant . Similar all my existing member of staff they all can send n recieve using IMAP.

But new user i am creating in AD cant. Its only while sending i m getting error

The message could not be sent because the server rejected the sender's e-mail address. The sender's e-mail address was 'EmailAddress'. Subject 'Subject', Account: 'Account', Server: 'Server', Protocol: SMTP, Server Response: '454 5.7.3 Client does not have permission to submit mail to this server.', Port: 25, Secure(SSL): No, Server Error: 454, Error Number: 0x800CCC78 I refer to MS - KB at http://support.microsoft.com/kb/818778/en-usand i got exactly the same thing what mention on KB. I just dont understand what could be wrong. If it work for existing user then it should work for me. Also i try to compare the permission with normal IMAP user and myself. In the AD account security tab .Self Group was having permission like Read, Send , cHANGE Password.While i was not having those permission . I apply those permission  and started working. But after certain time all the permission automatically disappear. I will be please if you guys at MSEXCHANGE.org can help me on this...thanks Riz 


Sponsored Links:



I have just finished transferring my Outlook Express 6 to Outlook 2003 -
included everything - address book, etc. I am trying to send an email using
Outlook to a group of people - I set up distribution lists. The email won't
go out if I put a group of people in the BCC field. It went out with 1
person in the BCC field. I tried it with about 12 people in the BCC field
and it wouldn't go out.

How can I fix this as I like to hide the names of the recipients?

Thank you




I have just finished transferring my Outlook Express 6 to Outlook 2003 -
included everything - address book, etc. I am trying to send an email using
Outlook to a group of people - I set up distribution lists. The email won't
go out if I put a group of people in the BCC field. It went out with 1
person in the BCC field. I tried it with about 12 people in the BCC field
and it wouldn't go out.

How can I fix this as I like to hide the names of the recipients?

Thank you




Hi,

I use MailMessage & SmtpClient to send email to exchange server. Then, I use
webdav to retrieve the email content and save it in a file.

First I send a text/plain email, then save the message in file. If it runs
in Exchange 2003, the saved content is the following:
**********************
MIME-Version: 1.0
From: xxxx
To: xxxx
Date: xxxx
Subject: 0: sub
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Return-Path: xxxx
Message-ID: xxxx
X-OriginalArrivalTime: xxxx

0: test
***********************

But if I run it in Exchange 2007, the saved content is:
************************
Subject: 0: sub
Date: xxxxx
MIME-Version: 1.0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: xxxx
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: 0: sub
Thread-Index: xxxx
From: xxxx
X-MimeOLE: Produced By Microsoft Exchange V8.1
To: "Mary" xxxx

0: sub

0: test

*******************************

In exchange 2007, it changes the content format of saved file. Is it
possible not allow Exchange 2007 to convert the content to html file but keep
in text/plain file?

Thanks,
Mary




Hi,

I use MailMessage & SmtpClient to send email to exchange server. Then, I use
webdav to retrieve the email content and save it in a file.

First I send a text/plain email, then save the message in file. If it runs
in Exchange 2003, the saved content is the following:
**********************
MIME-Version: 1.0
From: xxxx
To: xxxx
Date: xxxx
Subject: 0: sub
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Return-Path: xxxx
Message-ID: xxxx
X-OriginalArrivalTime: xxxx

0: test
***********************

But if I run it in Exchange 2007, the saved content is:
************************
Subject: 0: sub
Date: xxxxx
MIME-Version: 1.0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: xxxx
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: 0: sub
Thread-Index: xxxx
From: xxxx
X-MimeOLE: Produced By Microsoft Exchange V8.1
To: "Mary" xxxx

0: sub

0: test

*******************************

In exchange 2007, it changes the content format of saved file. Is it
possible not allow Exchange 2007 to convert the content to html file but keep
in text/plain file?

Thanks,
Mary




Hi,
as per this thread http://forums.msexchange.org/m_1800512756/mpage_2/key_/tm.htm
i have a similar situation but reading through to the last post, the issue was not confirmed as resolved with the last suggested method.

our scenario is this:

company: domainabc.com was acquired and a new company rename was created in existing infrastructure to domainxyc.com. same exchange servers were used so essentially new exchange policies were created to set pri smtp as domainxyz.com with domainabc.com remaining as secondary smtp addresses.
Then the company split and domainabc.com users were migrated off our infrastructure onto another totally independant network. they kept domainabc.com. we kept domainxyz.com on the original exchange setup.

now users in domainxyz.com cant send emails to the external organisation domainabc.com as emails dont route externally and return with a NDR: " The e-mail account does not exist at the organization this message was sent to"

we have a exchange 2003 environment. 1x FE server, and 2x BE servers

so as per the link above, i've done the following:
- I made sure I removed all references for domainabc.com from policies in system manager.
- used Metabase Explorer and removed references to that domains there
- Restarted IIS
(did the above on all 3 exchange servers rather than waiting for replication)

When that didnt resolve the issue I created an smtp routing connector for domainabc.com and to point to the firewall IP of domainabc.com (reminder, this is seperate to our network, so in theory i presume the smtp connections should route out to the internet and hit domainabc.com fw). Restarted the exchange routing service and stop and started the smtp virtual server protocol in ESM – for all exchange servers.

- then Restarted all Exchange Servers for good measure.

still getting the same ND message and ESM tracking shows it doesnt even leave the local exchange server

suggestions?




Good morning to all MSExchangers,

We are using Exchange 2003 and everything is working fine. I have one user that is a consultant and he has his own pc, he is using Outlook 2007 with 2 pop3 accounts that are his own email address, he wants me to add our email as a pop3, but when I go to setup the account everything goes good until I test the account. When I run the test Outlook is able to connect to the POP3 (mail.domainname.com) but it fails to send emails using mail.domainname.com. Where is it that I have to go to make sure that he can send emails from witin our domain using a pop3 account.
I also added in our DNS smtp.domainname.com and tried using that and it did not work also.

Any and every suggestion is greatly apprciated.

Thank you in advance,




We are running a windows 2000 native domain with a exchange 5.5 site which
has 2 exchange 5.5 servers.  We are now migrating to exchange 2003 server
and have installed a exchange 2003 server into the exchange 5.5 site and
moved most of our mailboxes to the new exchange server which is working fine.
We also had a ADC running with two way setup. The problem we are having is when I log on to the exchange 2003 server and use the ADUC in the microsft exchange and then create a new user and the mailbox for the new user, and when I log into a machine, I can log into the network normally but when I open up Outlook I get the following error message: Unable to open your default email folders.  The attempt to log on to the Microsoft Exchange server computer has failed. But if I create a user in ADUC on any of my domain controllers and then just create the mailbox for the new user in the ADUC in exchange 2003 I can open up Outlook fine.   I moved all mailboxes from exchange 5.5 to 2003 and they all log in fine. Its only when I create the user in the ADUC in exchange 2003 that I cant get them to open up outlook. Can anyone help please.




I running exchange 2003, I can got email from outside and very quickly, but
when i send email,it's seems exchange only put it in the queue but not send
out and after 2 or 3 hours, it sent out(one case it restart the server).I
just run routing group connector on server and route all outgoing mail to
other server(but the mail hanging on this server queue),is anybody can
help,thanks!




i'm using exchange 2003 server and outlook 2003 (pop3) as client computer, i
tick the box to keep email in server when use outlook 2003 to receive email,
but I cannot find any mail in server afterwards, anybody know why?

thanks!!!
JY




Anyone tried to do this using Recepient and Sender Filtering in
Exchange 2003. We have suspicious emails but we want to analyze them
w/o halting delivery both ways.

thanks,
Roman Rozinov
Arizona State University




Hi,

I am writing an application which uses SMPTPOP3 to send and received email
messages
and I want to check it against exchange 2003 server

using POP3 connector I can usefully downloaded messages from the internet to
a mail box

and I was wondering if the same can be done using "SMTP connector"

meaning that the SMTP will route messages from a mail box to external email
address

my ISP outgoing server is mailgw.netvision.net.il and I am guessing that
it will only get messages sent using a legal address(which I have of course)

so i need to tell the "SMTP Connectot" to use one of my legeal email
address?!

Thanks




When you give users "send as" rights to a exchange 2003 mailbox and these users
reply to an email in the target users mailbox the email sent goes into the
users mailbox who is doing the replying/"sending as" not the mailbox itself.

IS there a way to get the mail to go the sent items of the mailbox owner not
the user who is "sending as" sent items.




I have a SBS 2003 Premum R2 server with clients using Outlook 2003.
Everyone can send and receive email with the accounts established in
Exchange 2003 sp2.
However, One user needs to have a pop3 account added to her oulook profile.
It's an earthlink account that requires authentication to send.
I have tried everything posted at earthlink to no avail.
She can receive but cannot send using the pop account.

Anyone have a suggestion?




I have an exchange account set up as well as an IMAP account set up in my
outlook. When I send any email using IMAP account, it always shows in outbox
folder of EXCANGE SERVER and not on IMAP outbox folder. Shouldn't message be
shown in IMAP outbox folder?
Now the main problem. If I am not sitting inside my company network, the
IMAP email I send does not go through. This probably happens because instead
of IMAP, outlook tries to send it through exchange server. If I am sitting
inside my company network, all emails go through. What I need is, my IMAP
mails should be send through IMAP server so that it always go through. And
then it should show in IMAP outbox and subsequently IMAP send mail folder.
How do I solve this problem?




Dear Community,

Knowledge Base Article ID: 930364 (http://support.microsoft.com/kb/930364
)shows how to change the IMAP Append size
limit for Exchange 2000. Can I use the same Registry Key in Exchange 2003
to set the limit or is there something similar to
"HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServic esIMAP4SVCParametersAppendSizeLimit" for Exchange 2003?

Thanks a lot!
René




Hi All,

One of my clients is having problems is sending emails to specific servers due to the fact that they were being blacklisted by spamhaus and spamcop. They have exchange 2003 setup and operational for sending and recieving emails, since few days back they started encountering series of problems one after the other which were as following. and yes one more thing they have recently deployed GFI MailEssentials 12 and MailSecurity like 10 days back.

Problem #1: Four days back some one reported that he is unable to send email to one of his regular recepient and "undelivery message" arrives in his mailbox upon checking the network admin found that the message is saying that there server is blocked by spamhaus xbl-sbl list. Therefore, he sent the request to spamhaus and by next day the ban was lifted.

Problem #2: Two days back it was reported by many users that they are unable to send emails to many different recepient. upon checking the network admin found that there exchange server is blacklisted by spamcop this time. but since we know that you cannot send the removal request to spamcop to be unlisted from the blocked list and have to wait because they remove it automatically and only if they do not receive spam from the server. therefore the only way is to make sure that no one is infected inside the network and generating spam. so they excersied and checked all network machines for any infection and YES did found many infected machines and cleaned them.

Problem #3: during this finding, cleaning and waiting durtion I found something strange. they have one domain say www.abc.com which is hosted by another web hosting company and since they are the primary DNS for www.abc.com (this web hosting company) they also have the MX and A record for mail.abc.com pointing to 1.2.3.4 accessible from outside for web exchange users.

Strange part in all this is; that when there exchange got blocked by spamhaus and spamcop, the undelivery message which the users were receving claimed that their email server is blacklisted by spamcop/spamaus, where the server IP which they were showing was not the one their exchange; meaning it should be 1.2.3.4 but instead it was showing 
11.22.33.44...

any ideas or help would be great to actually get me started up with this issue. i have tried to resolve there email server ip and it also shows the one which it orginally belongs to (1.2.3.4) even checked it on dnsreport.com and other sites as well as nslookup. plus inside there network this ip is alive.

problem #4: while looking up on spamcop, they are reporting that two email addresses were caught spamming and amoung these two addresses one does not even exist in the exchange, actually it belongs to a person who had left long time back and they had deleted the account along with the email address but still on the GFI Security this email address is being seen spamming and sending emails forged automatically, is there a way in exchange 2003 to DIG and completely remove or block it? thanks in advance.




Is these a way to archive email account in exchange 2003 to a pst file, when a user leaves the company and you looking to backup the user email and delete the account.

best regards

Graham Duffy




Hi,

Let me know "How do I forward emails coming to a user to two different email addresses in exchange 2003"

Same domain.

Regards




I have installed Exchange 2003 on a Windows 2003 R2 server.  My ISP blocks port 25 for incoming email.  I use a service that sends email to port 9925 on my SMTP protocol.  I can send and receive email using Outlook POP3 to internet addresses, hotmail, at work, etc.  I use my ISP's outgoing SMTP server.  My domain is registered thru GoDaddy.  My MX records point to the service to receive incoming email.  I can access OWA from the internet and receive email using OWA.  I can send and receive email using OWA to users within the local network 192.168.0.whatever.  I cannot send email using OWA to any internet email address,  work, hotmail etc.  I have searched and searched but cannot find a solution for using OWA for internet email addresses.  Any suggestions would be greatly welcomed.  I think the problem has to do with SMTP.  I even added another network card, different IP address using port 25 and created another virtual SMTP service for the added network card. No luck