[pfx] Re: said: 550 Mail was identified as spam

2023-05-17 Thread Wietse Venema via Postfix-users
You are ignoring my response. That is rude. Stop spamming 
the postfix-users list with your repeated information.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: said: 550 Mail was identified as spam

2023-05-17 Thread Matus UHLAR - fantomas via Postfix-users

On 17.05.23 10:43, lty--- via Postfix-users wrote:

May 16 08:41:14 smtp3 postfix-sen/qmgr[27776]: 3420CA2062F:
from=, size=56791841, nrcpt=1 (queue active)

May 16 08:41:31 smtp3 postfix-sen/smtp[10076]: 3420CA2062F:
to=, relay=x.x.x.x[x.x.x.x]:25, delay=18,
delays=0.52/0/0.1/17, dsn=5.0.0, status=bounced (host x.x.x.x[x.x.x.x]
said: 550 Mail was identified as spam. (in reply to end of DATA
command))


the recipient's mail dserver with IP address x.x.x.x refused accepting 56MB 
mail from you, noting that it is spam.



Relay server log:

May 16 08:41:14 smtp520 postfix-sen16/smtpd[28709]: connect from
unknown[x.x.x.x]

May 16 08:41:14 smtp520 postfix-sen16/smtpd[28709]: D2E6DFFFD7:
client=unknown[x.x.x.x]

May 16 08:41:31 smtp520 postfix-sen16/smtpd[28709]: lost connection
after DATA (48169779 bytes) from unknown[x.x.x.x]


looks like destination server with the same IP address x.x.x.x refused 
accepting 48MB mail from your relay too.


looks like they just don't like your e-mail.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Microsoft dick is soft to do no harm
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: said: 550 Mail was identified as spam

2023-05-16 Thread Wietse Venema via Postfix-users
lty--- via Postfix-users:
> SMTP server og: 
> 
> May 16 08:41:14 smtp3 postfix-sen/qmgr[27776]: 3420CA2062F:
> from=, size=56791841, nrcpt=1 (queue active) 
> May 16 08:41:31 smtp3 postfix-sen/smtp[10076]: 3420CA2062F:
> to=, relay=x.x.x.x[x.x.x.x]:25, delay=18,
> delays=0.52/0/0.1/17, dsn=5.0.0, status=bounced (host x.x.x.x[x.x.x.x]
> said: 550 Mail was identified as spam. (in reply to end of DATA
> command)) 
> 
> Relay server log: 
> 
> May 16 08:41:14 smtp520 postfix-sen16/smtpd[28709]: connect from
> unknown[x.x.x.x] 
> May 16 08:41:14 smtp520 postfix-sen16/smtpd[28709]: D2E6DFFFD7:
> client=unknown[x.x.x.x] 
> May 16 08:41:31 smtp520 postfix-sen16/smtpd[28709]: lost connection
> after DATA (48169779 bytes) from unknown[x.x.x.x] 
> May 16 08:41:31 smtp520 postfix-sen16/smtpd[28709]: disconnect from
> unknown[x.x.x.x] 

There is a spam filter betwen the sending and the receiving server.
The spam filter drops the connection to the relay server after
48169779 bytes, and replies "550 Mail was identified as spam".

If Postfix has blocked the message, it would have sent an RFC 3463
enhanced status code like

550 5.7.x Mail was identified as spam

Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: said: 550 Mail was identified as spam

2023-05-15 Thread lty--- via Postfix-users
 

Re 

2023-05-16 12:20,l...@cndns.com: 

> https://www.postfix.org/postconf.5.html#debugger_command [1] 
> 
> debugger_command is the default configuration of postfix, I can shield it, 
> but I don't know if it works. 
> 
> header_checks very simple. 
> 
> [root@smtp520 ~]# cat /etc/postfix/header_checks | grep -v '^#' 
> 
> /^Received:.+$/ IGNORE 
> 
> 2023-05-16 12:09,Tom Reed via Postfix-users: Relay server configuration is 
> very simple. debugger_command = 
> PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd 
> 
> $daemon_directory/$process_name $process_id & sleep 5
> header_checks = regexp:/etc/postfix/header_checks 
> 
> I am not sure, but have you checked the configuration above? They seem to
> be influenced by message content.
> 
> 2023-05-16 12:02,l...@cndns.com:
> 
> Relay server configuration is very simple. 
> 
> No additional anti-spam policies. 
> 
> Relay config:
> postconf -n:
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> authorized_submit_users = root
> bounce_queue_lifetime = 1d
> bounce_size_limit = 73400320
> command_directory = /usr/sbin
> config_directory = /etc/postfix-sen16/
> daemon_directory = /usr/libexec/postfix
> data_directory = /var/lib/postfix-sen16
> debug_peer_level = 2
> debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd 
> $daemon_directory/$process_name $process_id & sleep 5
> header_checks = regexp:/etc/postfix/header_checks
> html_directory = no
> inet_interfaces = x.x.x.x
> inet_protocols = ipv4
> mail_owner = postfix
> mailbox_size_limit = 73400321
> mailq_path = /usr/bin/mailq.postfix
> manpage_directory = /usr/share/man
> master_service_disable =
> maximal_backoff_time = 3600s
> maximal_queue_lifetime = 1d
> message_size_limit = 73400320
> minimal_backoff_time = 1000s
> multi_instance_enable = yes
> multi_instance_group = mta
> multi_instance_name = postfix-sen16
> mydestination = $myhostname, localhost.$mydomain, localhost
> myhostname = hostname
> mynetworks = /etc/postfix/network_table
> newaliases_path = /usr/bin/newaliases.postfix
> queue_directory = /var/spool/postfix-sen16
> queue_run_delay = 1000s
> readme_directory = /usr/share/doc/postfix-2.11.0/README_FILES
> sample_directory = /usr/share/doc/postfix-2.11.0/samples
> sendmail_path = /usr/sbin/sendmail.postfix
> setgid_group = postdrop
> smtp_bind_address = x.x.x.x
> smtp_connect_timeout = 300s
> smtp_data_xfer_timeout = 300s
> smtp_tls_security_level = may
> unknown_local_recipient_reject_code = 550
> 
> postconf -Mf:
> smtp inet n - n - - smtpd
> pickup unix n - n 60 1 pickup
> cleanup unix n - n - 0 cleanup
> qmgr unix n - n 300 1 qmgr
> tlsmgr unix - - n 1000? 1 tlsmgr
> rewrite unix - - n - - trivial-rewrite
> bounce unix - - n - 0 bounce
> defer unix - - n - 0 bounce
> trace unix - - n - 0 bounce
> verify unix - - n - 1 verify
> flush unix n - n 1000? 0 flush
> proxymap unix - - n - - proxymap
> proxywrite unix - - n - 1 proxymap
> smtp unix - - n - - smtp
> relay unix - - n - - smtp
> showq unix n - n - - showq
> error unix - - n - - error
> retry unix - - n - - error
> discard unix - - n - - discard
> local unix - n n - - local
> virtual unix - n n - - virtual
> lmtp unix - - n - - lmtp
> anvil unix - - n - 1 anvil
> scache unix - - n - 1 scache
 

Links:
--
[1] https://www.postfix.org/postconf.5.html#debugger_command
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: said: 550 Mail was identified as spam

2023-05-15 Thread Tom Reed via Postfix-users



>
>
> Relay server configuration is very simple.
>
> debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd
$daemon_directory/$process_name $process_id & sleep 5
> header_checks = regexp:/etc/postfix/header_checks


I am not sure, but have you checked the configuration above? They seem to
be influenced by message content.


-- 
sent from https://dkinbox.com/

___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: said: 550 Mail was identified as spam

2023-05-15 Thread Tom Reed via Postfix-users



>
>
> https://www.mail-archive.com/postfix-users@postfix.org/msg99175.html [1]
>
>
> This question has been consulted a few days ago, thanks to the team for
> the reply
>
> We have provided more detailed logs this time
>
> SMTP server og:
>
> May 16 08:41:14 smtp3 postfix-sen/qmgr[27776]: 3420CA2062F:
> from=, size=56791841, nrcpt=1 (queue active)
>
> May 16 08:41:31 smtp3 postfix-sen/smtp[10076]: 3420CA2062F:
> to=, relay=x.x.x.x[x.x.x.x]:25, delay=18,
> delays=0.52/0/0.1/17, dsn=5.0.0, status=bounced (host x.x.x.x[x.x.x.x]
> said: 550 Mail was identified as spam. (in reply to end of DATA
> command))
>

The log has told you that relay server rejected your message due to spam
confirmed. You may check what antispam policies are deployed in relay
server which cause this bounce.

Thanks.


-- 
sent from https://dkinbox.com/

___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org