IRC3220 Not Sending to Email

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • goldem

    #1

    IRC3220 Not Sending to Email

    We have an IRC 3220. When trying to perform a scan to email, the message times out.

    When I watch the network traffic, I see the scanner is trying to initiate a non-RFC compliant email conversation and failing, which is basically trailing a dot i.e.:

    EHLO C3200.

    Is there a way to modify the settings on the scanner so it actually complies with the RFC, i.e. remove the trailing dot?
    Last edited by Guest; 05-11-2009, 04:04 PM.
  • SCREWTAPE
    • May 2025

    #2
    Originally posted by golden
    We have an IRC 3220. When trying to perform a scan to email, the message times out.

    When I watch the network traffic, I see the scanner is trying to initiate a non-RFC compliant email conversation and failing, which is basically trailing a dot i.e.:

    EHLO C3200.

    Is there a way to modify the settings on the scanner so it actually complies with the RFC, i.e. remove the trailing dot?
    Do you have your own SMTP server or a third party email carrier?
    All that is needed is the SMTP info and an email address for the machine. If authorization is needed, hopefully you are the IT guy. As for RFC, I've never came across this when setting up emailing. You can also scan to folder using the file(smb) option.

    Comment

    • goldem

      #3
      Yup, I am the IT guy. The SMTP server is internal, running Exchange 2007. We've enabled the ability to relay from the scanner.

      The problem isn't with the email address that is being sent to, it's the way the scanner is communicating with the email system from everything I can see (thereby the mention of the non-compliance with the RFC).

      I am pretty sure this article (Exchangepedia Blog: RFC 2821, HELO again: Validating the HELO/EHLO domain) addresses the issue, but that is for a different version of the SMTP server.

      Comment

      • costd
        Technician

        250+ Posts
        • Jan 2008
        • 409

        #4
        1. If it times out, what is the error code?
        2. As ScrewTape said, check your SMTP settings of the 3220.
        3. Relay? Within an Intranet? The 3220 should be configured as a user. Should be able to set it for a direct send.
        4. No, the "trailing" dot cannot be removed by the 3220 - but - I suspect you could apply the article info and have a mask configured at the server end.

        Since you are the IT guy, it is up to you - but with my customers that have their own SMTP server inside their Intranet, we just configure the machine to send directly. No user/password issues that way.

        Comment

        • Canuck
          Tech Specialist

          1,000+ Posts
          • Nov 2007
          • 1713

          #5
          I've installed e-mail on lots of these....this is never an issue. Your SMTP address is put in the copier and if a third party provider for external e-mail is used that is set-up on computer...ie...Outlook,accounts,etc. This machine communicates with pretty well anything...fix the dot at your end. It may be possible in service mode to make some changes...haven't looked. But you would need a tech.

          Comment

          • KenB
            Geek Extraordinaire

            2,500+ Posts
            • Dec 2007
            • 3945

            #6
            For whatever it may be worth, we just had the exact same issue on a new Ricoh machine (MP C4000) where the trailing dot was causing the message to get bounced by the Exchange server.

            The problem was resolved by updating the firmware.

            You may want to check the firmware on your Canon machine to see if it is current, and update it if is not.

            (I've worked with Canon and Ricoh for many years, and am very familiar with both...)

            Good luck!
            “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

            Comment

            • kuby
              Senior Tech

              1,000+ Posts
              • Oct 2007
              • 1374

              #7
              Make sure that the SMTP ports are set right (default 25), some ISP's are changing this to stop SPAM. Our customers did and did not get a notification until 2 days later.

              Comment

              Working...