Logs, Delivery

Hey there @youthful-zorse, I see you had AUTH PLAIN in your snippet. The AUTH PLAIN part of an SMTP trace reveals the auth credentials; they are only obscured by base64 encoding, not encrypted.

If you didn’t redact your credentials, I recommend deleting the snippet and changing your credentials.

swaks --to ashutosh.shukla@sinch.com --from test@mg.us.aclmobile.net --server smtp.mailgun.org --port 587 --auth plain --auth-user sadasdad --auth-password sdadada --tls

in this I am using server maigun sever the mail is going but I want to send it from my local server but not happeing getting the error

Hey there @youthful-zorse, I see you had AUTH PLAIN in your snippet. The AUTH PLAIN part of an SMTP trace reveals the auth credentials; they are only obscured by base64 encoding, not encrypted.

If you didn’t redact your credentials, I recommend deleting the snippet and changing your credentials.

And the output of that SWAKS?

=== Trying smtp.mailgun.org:587…
=== Connected to smtp.mailgun.org.
← 220 Mailgun Influx ready
→ EHLO ip-10-4-1-71.ap-south-1.compute.internal
← 250-ab830b61adae
← 250-AUTH PLAIN LOGIN
← 250-SIZE 52428800
← 250-8BITMIME
← 250-SMTPUTF8
← 250-PIPELINING
← 250 STARTTLS
→ STARTTLS
← 220 Go ahead
=== TLS started with cipher TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128
=== TLS no local certificate set
=== TLS peer DN=“/C=US/ST=Texas/L=San Antonio/O=MAILGUN TECHNOLOGIES, INC/CN=*.mailgun.org”
~> EHLO ip-10-4-1-71.ap-south-1.compute.internal
<~ 250-ab830b61adae
<~ 250-AUTH PLAIN LOGIN
<~ 250-SIZE 52428800
<~ 250-8BITMIME
<~ 250-SMTPUTF8
<~ 250 PIPELINING
~> AUTH PLAIN xxxxxxxx
<~ 235 Authentication successful
~> MAIL FROM:test@acl.pinchappmails.com
<~ 250 Sender address accepted
~> RCPT TO:ashutosh.shukla@sinch.com
<~ 250 Recipient address accepted
~> DATA
<~ 354 Continue
~> Date: Thu, 21 Dec 2023 23:53:16 +0530
~> To: ashutosh.shukla@sinch.com
~> From: test@acl.pinchappmails.com
~> Subject: test Thu, 21 Dec 2023 23:53:16 +0530
~> Message-Id: 20231221235316.008448@ip-10-4-1-71.ap-south-1.compute.internal
~> X-Mailer: swaks v20170101.0 jetmore.org/john/code/swaks/
~>
~> This is a test mailing
~>
~> .
<~ 250 Great success
~> QUIT
<~ 221 See you later. Yours truly, Mailgun
=== Connection closed with remote host.

Hey there @youthful-zorse, I see you had AUTH PLAIN in your snippet. The AUTH PLAIN part of an SMTP trace reveals the auth credentials; they are only obscured by base64 encoding, not encrypted.

If you didn’t redact your credentials, I recommend deleting the snippet and changing your credentials.

And the current configs in gist.github.com pls

ok

https://gist.github.com/anshukla60/a4fd937c0298adec88bbcf2e52580798

please find the file below

Where is shaping.toml located?

/opt/kumomta/etc

this is the path

You are not referencing that in the shaping:setup call.

ok so how would I set up that?

Change the call to shaping:setup to reference the path to your shaping.toml

Dec 22 00:55:21 ip-10-4-1-71 kumod[9174]: 2023-12-21T19:25:21.785399Z DEBUG logger kumod::logging: deadline reached, running expiration for this segment
Dec 22 00:55:21 ip-10-4-1-71 kumod[9174]: 2023-12-21T19:25:21.785565Z DEBUG logger kumod::logging: Flushed “/var/log/kumomta/20231221-192520_recv”
Dec 22 00:55:21 ip-10-4-1-71 kumod[9174]: 2023-12-21T19:25:21.785594Z DEBUG logger kumod::logging: waiting until deadline=None for a log record
Dec 22 00:55:22 ip-10-4-1-71 kumod[9174]: 2023-12-21T19:25:22.091866Z DEBUG localset-7 kumod::ready_queue: Error in Dispatcher::run for unspecified->smtp.mailgun.org@smtp_client: fetching smtp_auth_plain_password: No such file or directory (os error 2) (consecutive_connection_failures=1)

this the error I am getting

The error you are getting to what config? I assume you made changes.

when I am using shaping.toml