Send Mail to restricted Acount | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. Send Mail to restricted Acount

Send Mail to restricted Acount

  • Javier

    I hope I explained correctly. 

    We have created an account to send mail from a website, for internal use within our domain
    This email account has the restrictions provided by the mdaemon server.

    But the email is sent on behalf of another email account

    we give an example:

    We send an email from the email address of comercial@mail.int, but we use the email account sendmail@mail.int.

    This last account has a restriction that only allows sending emails internally, but when we send it on behalf of comercial@mail.int, it is capable of sending emails outside the domain.

    Is this a normal operation?

    0 likes
  • L

    Hello Javier,

    To make sure I understand, let me ask this: when the message is sent, the MAIL FROM command uses sendmail@mail.int, while the From in the body of the message is comercial@mail.int - is that correct? Or is it reversed?

    Can you provide a copy of the log in which the message is sent?

     

    0 likes
  • Javier

    As you can see the restriction of sending the email, it is in the alias.

    Not in the authenticated account

     

     

    Thu 2023-02-16 12:26:41.830: Session 14441908; child 0001
    Thu 2023-02-16 12:26:41.830: Accepting SMTP connection from 81.47.165.xxx:7673 to 192.168.xx.xx:25
    Thu 2023-02-16 12:26:41.831: --> 220 mail.commcenter.es ESMTP MDaemon 22.0.1; Thu, 16 Feb 2023 12:26:41 +0100
    Thu 2023-02-16 12:26:41.857: <-- EHLO RNP58387929C284
    Thu 2023-02-16 12:26:41.857: --> 250-mail.commcenter.es Hello RNP58387929C284 [81.47.165.xx], pleased to meet you
    Thu 2023-02-16 12:26:41.857: --> 250-ETRN
    Thu 2023-02-16 12:26:41.857: --> 250-AUTH LOGIN CRAM-MD5 PLAIN
    Thu 2023-02-16 12:26:41.857: --> 250-8BITMIME
    Thu 2023-02-16 12:26:41.857: --> 250-ENHANCEDSTATUSCODES
    Thu 2023-02-16 12:26:41.857: --> 250-PIPELINING
    Thu 2023-02-16 12:26:41.857: --> 250-CHUNKING
    Thu 2023-02-16 12:26:41.857: --> 250-STARTTLS
    Thu 2023-02-16 12:26:41.857: --> 250 SIZE
    Thu 2023-02-16 12:26:41.883: <-- AUTH CRAM-MD5
    Thu 2023-02-16 12:26:41.883: --> 334 PE1EQUVNT04tRjIwMjMwMjE2MTIyNi5BQTI2NDE4ODNNRDE4MzJAbWFpbC5jb
    Thu 2023-02-16 12:26:41.917: <-- aW1wcmVzb3JhX2lAY29tbWNlbnRlci5lcyA0ODdlZmZkNWYwYTNlN2YxOGQ1ZGQ0M
    Thu 2023-02-16 12:26:41.917: Autentificando impresora_i@commcenter.es
    Thu 2023-02-16 12:26:41.918: Authenticated as impresora_i@commcenter.es
    Thu 2023-02-16 12:26:41.918: --> 235 2.7.0 Authentication successful
    Thu 2023-02-16 12:26:41.946: <-- MAIL FROM:<tuimpresora@commcenter.es>
    Thu 2023-02-16 12:26:41.947: --> 250 2.1.0 Sender OK
    Thu 2023-02-16 12:26:41.972: <-- RCPT TO:<javier@jmexxxxx.xx>
    Thu 2023-02-16 12:26:41.973: tuimpresora@commcenter.es está actualmente restringido para correo local solamente
    Thu 2023-02-16 12:26:41.973: --> 550 5.1.1 Recipient unknown <javier@jmexxxx.xxxx>
    Thu 2023-02-16 12:26:41.998: <-- QUIT
    Thu 2023-02-16 12:26:41.998: --> 221 2.0.0 See ya in cyberspace
    Thu 2023-02-16 12:26:41.998: SMTP session terminated (Bytes in/out: 194/521)

    Who would have to restrict the sending? The authenticated account or the FROM

    0 likes
  • L

    Hello Javier, I apologize for the delay in responding.

    I set up this scenario and it does restrict the sending of email on behalf of the restricted account. I believe this is intentional. You would need to remove the restriction on the account. I can wishlist allowing to send on behalf of a restricted account if you would like, but I don't have a timeline on when or even if the developers would add this ability.

    0 likes
Please login to reply this topic!