Scan to Email outside the domain

[blackcat4866]

DLP, tmaged,
Thanks. The SMTP Relay worked like a charm. The Tech Republic instructions were good enough that even I could do it. My IT assist knew where to look (with the instructions), and we were out the door in an hour.

You know, if I do this long enough, someday I may know what I'm doing. Thanks for the support. =^..^=

[D_L_P]

...Maybe I'm way off base here, but here's my theory. With authentication Off, it works fine. So their SMTP server is currently set up to function without authentication. For this authentication On setting to work, the SMTP server must be re-configured to function with authentication, and all the users re-configured to authenticate (either automatically, or by logging into one's email)...

Sounds like you got your answer from tmaged, but to answer your theory. If their SMTP server has authentication turned OFF and you turn it ON at the copier then the e-mail will still fail, even if technically it is a valid user/pass. The reason is the user/pass is valid credentials at the DNS server, the SMTP server is not asking for a password. The DNS and SMTP functions can be performed by the same server or separate servers depending on how they have it setup, but either way if SMTP authentication is set to off and you put in a password it will fail.

So, you are right and shame on the IT guy for not realizing if you put in a password it would fail, and for not realizing that isn't why it can't send outside the domain. Also, when STMP authentication is turned on it is typically setup to use the same user/pass used to logon.

In my experience not being able to send outside the domain isn't just limited to the copier, some or all users can't send e-mail outside the domain. The relay should work for them, assuming it is just some users can't send outside the domain. If nobody can send outside the domain then they have other issues.

[tmaged]

I edited my first post to include the link. You can always email me directly. It's baseball & golf season, so I don't frequent here as much !!

[blackcat4866]

I was hoping you would weigh in, Tony. I'll be very intersted in seeing this doc. You know where to send it.

Thanks in advance. =^..^=

I hope this means more to my IT guy than it does to me. Thanks a lot. =^..^=

[tmaged]

D, I've got a document that I can't seem to locate at the moment. Basically in server 2008, you need to set up the IP address so Exchange knows mail is coming from a valid source inside the network. We got the same 3201 errors on a Falcon III & a Taskalfa after our customer switched from Server 2003 to 2008. I'm still looking...........


Here try this Exchange 2007: How to allow relay exceptions | Network Administrator | TechRepublic.com or How to Configure Trusted SMTP Relay in Exchange on SBS 2008 - The Official SBS Blog - Site Home - TechNet Blogs

[blackcat4866]

It's Exchange 2008. So you're saying that getting access outside the domain requires settings changes to the SMTP server? So why do you think the login isn't functioning? Are these settings changes specific to a user, or like a global policy for all users? Scan to email should still work at least within the domain with a valid login. =^..^=

[KenB]

The email server, whether it be Exchange, Domino, or whatever, must be set to allow relay in order to send outside the domain.

It's possible that relay is only allowed for a certain range of IP addresses or by domain name. If either of these is the case, authentication should be a non-factor.

[blackcat4866]

I don't think that it matters that much, but it's on a Copystar CS-250ci. I've set up scan to email often enough. And when told that the enduser wants to scan outside the domain, I've always told them that Authentication is required to email outside the domain. Up until last week, that was the end of the discussion.

Now I have an enduser who says, OK, enable authentication. Silly me, I presumed that from the webpage I would enable authentication, select Other, enter a valid username and password, and that would be it.

Not so. The IT guy insists that the username & password are valid and tested. He's set them up himself specifically for the MFP to have it's own account/identity. We're getting 3201 codes, which is an authentication error.

Maybe I'm way off base here, but here's my theory. With authentication Off, it works fine. So their SMTP server is currently set up to function without authentication. For this authentication On setting to work, the SMTP server must be re-configured to function with authentication, and all the users re-configured to authenticate (either automatically, or by logging into one's email).

Can anyone shed some light on this. I know only a little about scan to email. =^..^=