PowerMTA queue detail

Help

Queue Detail
name	k12datainsights.com/pmta-vmta3
recipients	2
kbytes	2.1
active connections	0
paused	no
mode	normal
backoff reason
next retry	2025-01-09 07:53:34

Last Errors
time	error
2025-01-09 07:43:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 07:33:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 07:23:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 07:13:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 07:03:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 06:53:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 06:43:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 06:33:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 06:23:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)
2025-01-09 06:13:34	Connection attempt failed, status = ECONNREFUSED while connecting from ip175.k12datainsights.com (192.95.36.175) to [127.0.0.1] (127.0.0.1) (2x)

Recipient Events (Deliveries: 0, Bounces: 0, Deferrals: 0)
Event	Time	Source IP	Address	Job ID	Destination MTA	Additional Information

Settings
VMTA Settings
max-smtp-msg-rate	unlimited	max-smtp-out	unlimited
Source IP Limits
Source IP Address	source-ip-max-smtp-out	source-ip-max-msg-rate	source-ip-max-connect-rate
192.95.36.175	unlimited	unlimited	unlimited
Queue Settings
type	smtp	dkim-headers-canon	relaxed
add-gm-token	no	dkim-identity	sender-or-from
allow-cancel-during-transfer	yes	dkim-sign	yes
allow-priority-interruption	yes	ignore-8bitmime	no
allow-priority-interruption-during-transfer	no	ignore-chunking	yes
assume-delivery-upon-data-termination-timeout	yes	ignore-pipelining	no
auth-password		log-commands	no
auth-username		log-connections	no
backoff-max-connect-rate	unlimited	log-data	no
backoff-max-msg-rate	1/m	log-disabled-ips	no
backoff-max-smtp-out	2	log-resolution	no
backoff-notify		log-transfer-failures	no
backoff-reroute-to-virtual-mta		max-cold-virtual-mta-msg	0/d
backoff-retry-after	20m	max-connect-rate	unlimited
backoff-to-normal-after	1h	max-errors-per-connection	10
backoff-to-normal-after-delivery	yes	max-events-recorded	10
backoff-upon-all-sources-disabled	no	max-msg-per-connection	100
bcc-upon-delivery		max-msg-rate	10000/h
bounce-after	1d	max-rcpt-per-message	1000
bounce-upon-5xx-greeting	yes	max-smtp-out	2
bounce-upon-no-mx	yes	notify-of-delay-every	4h
bounce-upon-pix-transfer-failure	no	pix-bug-workaround	yes
bounce-upon-transfer-failure	no	queue-priority	50
check-mfrom-outbound	no	reenable-source-ip-after	never
check-pra-outbound	no	remove-header
connect-timeout	2m	replace-smtp-421-service-response	no
data-send-timeout	3m	require-starttls	no
default-smtp-port	25	retry-after	10m
deliver-local-dsn	yes	retry-upon-new-mail	no
disable-acct-records		smtp-421-means-mx-unavailable	no
disable-mx-rollup	no	smtp-553-means-invalid-mailbox	yes
dk-sign	yes	smtp-data-termination-timeout	10m
dkim-add-body-limit	no	smtp-greeting-timeout	5m
dkim-add-timestamp	no	smtp-hosts	[127.0.0.1]:2525
dkim-algorithm	rsa-sha1	smtp-pattern-list	blocking-errors
dkim-body-canon	relaxed	smtp-tls-allow-SSLv3	yes
dkim-disallow-adding-headers		smtp-tls-allow-TLSv1	yes
dkim-expire-after	never	use-starttls	yes
dkim-headers		use-unencrypted-plain-auth	no