Re: noreply email technisch und für Empfänger zum Ausdruck bringen
On 28 May 2020, at 15:59, Thomas wrote: > Am 28.05.20 um 23:48 schrieb @lbutlr: >> On 28 May 2020, at 15:29, Thomas wrote: >>> I of cource use my own domain where I pay for. >> Yes, but read the rest of what I wrote, especially the parts I've >> highlighted: >> Do not create a fake address with someone else's domain. Do not use >> mudomain.com because you neither own nor control mydomain.com > > Of cource I will not do! Iam using my own domains I have paid before and only > I control. OK, but I am ALSO talking about when posting to groups, as you did in this thread. > mydomain.com was only an example for this discussion. And that is my point, do not use this as an example; this is a real domain. For example domains you can use example.com example.net and example.net or, at least for now, .tld since .tld is not a top-level domain. -- What was it they said about gods? They wouldn't exist if there weren't people to believe in them? And that applied to everything. Reality was what went on inside people's heads. --Moving Pictures
Re: hostname net6-ip74.linkbg.com does not resolve
On Fri, May 29, 2020 at 01:11:08AM +0200, mauri...@caloro.ch wrote: > I am not shure if this are normal? In my postfix log this message appair now > 2 days. > > May 29 00:59:22 mail postfix/smtpd[12989]: warning: hostname > net6-ip74.linkbg.com does not resolve to address 87.246.7.74: Name or > service not known The host in question does not exist (NXDOMAIN) in the forward DNS zone of linkbg.com. > May 29 00:59:43 mail postfix/smtpd[12781]: warning: hostname > net6-ip70.linkbg.com does not resolve to address 87.246.7.70: Name or > service not known You're getting SMTP connections 87.246.7.70 (et. al.) which claim to be have names like net6-ip70.linkbg.com: $ dig +noall +ans +nocl +nottl -x 87.246.7.70 70.7.246.87.in-addr.arpa. CNAME 70.0-255.7.246.87.in-addr.arpa. 70.0-255.7.246.87.in-addr.arpa. PTR net6-ip70.linkbg.com. However that name is fiction: $ dig +noall +noedns +comment -t a net6-ip70.linkbg.com. ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13194 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > Thanks for any possible Update Postfix logs the fact that the name is fiction. That's all. Nothing to worry about. -- Viktor.
hostname net6-ip74.linkbg.com does not resolve
Hello Iam not shure if this are normal? In my postfix log this message appair now 2 days. * Debian 9 - postfix = 3.1.14 May 29 00:59:22 mail postfix/smtpd[12989]: warning: hostname net6-ip74.linkbg.com does not resolve to address 87.246.7.74: Name or service not known May 29 00:59:43 mail postfix/smtpd[12781]: warning: hostname net6-ip70.linkbg.com does not resolve to address 87.246.7.70: Name or service not known May 29 00:59:44 mail postfix/smtpd[12989]: warning: hostname net6-ip66.linkbg.com does not resolve to address 87.246.7.66: Name or service not known May 29 01:00:07 mail postfix/smtpd[12989]: warning: hostname net6-ip74.linkbg.com does not resolve to address 87.246.7.74: Name or service not known May 29 01:00:30 mail postfix/smtpd[12781]: warning: hostname net6-ip70.linkbg.com does not resolve to address 87.246.7.70: Name or service not known May 29 01:00:30 mail postfix/smtpd[12926]: warning: hostname net6-ip66.linkbg.com does not resolve to address 87.246.7.66: Name or service not known rootl:/var/log# nslookup 87.246.7.74 Server: 46.38.225.230 Address:46.38.225.230#53 Non-authoritative answer: 74.7.246.87.in-addr.arpacanonical name = 74.0-255.7.246.87.in-addr.arpa. 74.0-255.7.246.87.in-addr.arpa name = net6-ip74.linkbg.com. Authoritative answers can be found from: 0-255.7.246.87.in-addr.arpa nameserver = sns.linkbg.com. 0-255.7.246.87.in-addr.arpa nameserver = pns.linkbg.com. pns.linkbg.com internet address = 89.215.246.2 sns.linkbg.com internet address = 89.215.246.3 Thanks for any possible Update Mauri
Re: discard(8) in a virtual mailbox environment
Viktor Dukhovni: > On Wed, May 27, 2020 at 12:52:00PM +, Laura Smith wrote: > > > Is it somehow possilble to make use of discard(8) to /dev/null certain > > addresses in a virtual mailbox setup (e.g.?virtual_alias_maps etc.) ?? > > Or can discard(8) only be applied to "real" receipients > > Yes, the transport table applies to all recipients except (IIRC) > *virtual alias* recipients that fail to be rewritten to a real > domain. > > transport: > disc...@example.com discard:silently > > This works for local, virtual mailbox, relay and even remote recipients, > but (again IIRC) not virtual alias recipients (rejected for lack of > rewrite to a real address prior to transport lookup). Yes, "user unknown in virtual alias maps" cannot be overruled with transport maps. Wietse > On Thu, May 28, 2020 at 11:31:00AM +0200, Ansgar Wiechers wrote: > > > You can define a virtual alias for a local "mailbox" /dev/null. Virtual > > aliases work for both virtual domains and virtual mailbox domains. > > > > 8< > > # /etc/postfix/virtual > > ... > > discardt...@example.org tr...@example.com > > This is unnecessarily complex, and assumes that the transport > for example.com is local(8). > > -- > Viktor. >
Re: noreply email technisch und für Empfänger zum Ausdruck bringen
Am 23.05.20 um 18:00 schrieb Ralph Seichter: From: Thomas Mustermann with the address nore...@domain.tld being *unknown* on your MX. That should result in a generic 5xx rejection. If you want more control over the rejection message, you can use something like the following: # /etc/postfix/main.cf smtpd_recipient_restrictions = ... check_recipient_access pcre:/etc/postfix/recipient_access ... Hi, thanks, that I will try. Thomas
Re: noreply email technisch und für Empfänger zum Ausdruck bringen
Am 28.05.20 um 23:48 schrieb @lbutlr: On 28 May 2020, at 15:29, Thomas wrote: I of cource use my own domain where I pay for. Yes, but read the rest of what I wrote, especially the parts I've highlighted: Do not create a fake address with someone else's domain. Do not use mudomain.com because you neither own nor control mydomain.com Of cource I will not do! Iam using my own domains I have paid before and only I control. mydomain.com was only an example for this discussion. thanks Thomas
Re: noreply email technisch und für Empfänger zum Ausdruck bringen
Am 25.05.20 um 16:17 schrieb Jaroslaw Rafa: Dnia 25.05.2020 o godz. 14:33:36 Thomas pisze: FAX is much better because FAX is same as letter and working digital, nearly 100% yes or no. Email I did not know if it is arrived, [...] What do you actually want to achieve? Because from your messages it's hard to understand what do you actually want. Its legal thing Again, today I print out sign and fax. I got an paper with send OK, date, time and recipient fax number The signed paper will send with postage. So for normal business fax arrived one working day before. Today form legal point fax is OK for due date. Letter can be arrive later. I dont care if recipient has such an bad organisation that fax an/or letter will throw away. Thats not my problem. I dont have an fax number, so recipient has to use letter and stamp. Thats what I want. Same I want to have nearly with Email and so I have to find an way that he could not answer with Email, So the solution seemed to be use sender address nor...@myworkingdomain.com and NORPLY is unkown. His mess age will/can not leave his server, he got only 5XX. Hopefully I have explained it a little better then before. best regards Thomas When you send an email and you get a 250 response, it means your message has been delivered (of course it does not mean the recipient has actually read it - it may have been put to spam, but you said you don't care about that; BTW. the same applies also for fax or paper letter; someone may receive it, but throw it immediately to trash without reading). 250 reply code is basically the same as fax confirmation - fax also doesn't give you any guarantee that anybody has actually read your message. If you get another reply, like 4xx or 5xx, that means your message hasn't been delivered. If you'd use a working return email address, you would receive rejection messages in case your message hasn't been delivered. Rejection messages are "negative confirmations", ie. you get them only when your message HASN'T been delivered. If you get nothing in return, you may assume your message has been delivered. If you explictly DON'T want to have a working return address, you decided yourself that you don't want these "negative confirmations". So you have to check logs, that's your only option. It's as simple as that. What else do you want?
Re: noreply email technisch und für Empfänger zum Ausdruck bringen
On 28 May 2020, at 15:29, Thomas wrote: > I of cource use my own domain where I pay for. Yes, but read the rest of what I wrote, especially the parts I've highlighted: Do not create a fake address with someone else's domain. Do not use mudomain.com because you neither own nor control mydomain.com ***and do not use mydoamin.com as a substitute for example.com** because, again, you neither own nor control mydomain.com. **Do not think that "my domain.com is obviously fake" because it is not** it is a valid domain and has been for 25 years. -- "Are you pondering what I'm pondering?" "Well, I think so, Brain, but snort no, no, it's too stupid!"
Re: noreply email technisch und für Empfänger zum Ausdruck bringen
Am 27.05.20 um 17:20 schrieb @lbutlr: As I said, use a valid domain THAT YOU CONTROL. Hi, I of cource use my own domain where I pay for. thanks
Re: discard(8) in a virtual mailbox environment
On Wed, May 27, 2020 at 12:52:00PM +, Laura Smith wrote: > Is it somehow possilble to make use of discard(8) to /dev/null certain > addresses in a virtual mailbox setup (e.g. virtual_alias_maps etc.) ? > Or can discard(8) only be applied to "real" receipients Yes, the transport table applies to all recipients except (IIRC) *virtual alias* recipients that fail to be rewritten to a real domain. transport: disc...@example.com discard:silently This works for local, virtual mailbox, relay and even remote recipients, but (again IIRC) not virtual alias recipients (rejected for lack of rewrite to a real address prior to transport lookup). On Thu, May 28, 2020 at 11:31:00AM +0200, Ansgar Wiechers wrote: > You can define a virtual alias for a local "mailbox" /dev/null. Virtual > aliases work for both virtual domains and virtual mailbox domains. > > 8< > # /etc/postfix/virtual > ... > discardt...@example.org tr...@example.com This is unnecessarily complex, and assumes that the transport for example.com is local(8). -- Viktor.
Re: discard(8) in a virtual mailbox environment
Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, 28 May 2020 10:31, Ansgar Wiechers wrote: > On 2020-05-27 Laura Smith wrote: > > > Is it somehow possilble to make use of discard(8) to /dev/null certain > > addresses in a virtual mailbox setup (e.g. virtual_alias_maps etc.) ? > > Or can discard(8) only be applied to "real" receipients > > You can define a virtual alias for a local "mailbox" /dev/null. Virtual > aliases work for both virtual domains and virtual mailbox domains. > > 8< > > /etc/postfix/virtual > > = > > ... > discardt...@example.org tr...@example.com > ... > >8 > > 8< > > /etc/aliases > > = > > ... > trash: /dev/null > ... > >8 > > Replace "example.org" with your virtual mailbox domain and > "example.com" with the local domain of the mail server. > > Regards > Ansgar Wiechers > > -- > > "Abstractions save us time working, but they don't save us time learning." > --Joel Spolsky Thank you Ansgar !
Re: Relationship between relay and transport
Scott A. Wozny: > In the standard config on an email gateway in > (http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall) the > proposed config has relay_domains set for example.com and > transport_maps set to a hash with example.com using > smtp:[inside-gateway.example.com]. This would - Deliver example.com to the inside host. - Deliver other domains to the outside network. > My question is, how is this functionally different from setting > relayhost to [inside-gateway.example.com]? This would - Deliver example.com to the inside host. - Deliver other domains to the inside host. So they do different things for other domains. Wietse
Re: discard(8) in a virtual mailbox environment
On 2020-05-27 Laura Smith wrote: > Is it somehow possilble to make use of discard(8) to /dev/null certain > addresses in a virtual mailbox setup (e.g. virtual_alias_maps etc.) ? > Or can discard(8) only be applied to "real" receipients You can define a virtual alias for a local "mailbox" /dev/null. Virtual aliases work for both virtual domains and virtual mailbox domains. 8< # /etc/postfix/virtual ... discardt...@example.org tr...@example.com ... >8 8< # /etc/aliases ... trash: /dev/null ... >8 Replace "example.org" with your virtual mailbox domain and "example.com" with the local domain of the mail server. Regards Ansgar Wiechers -- "Abstractions save us time working, but they don't save us time learning." --Joel Spolsky
Re: lost connection after HELO
On Thu, 28 May 2020 09:59:56 +0200 Matus UHLAR - fantomas wrote: > On 28.05.20 09:36, Enrico Morelli wrote: > >I've an UPS that should send me email in case of problems. The email > >do not arrive because in the log I see "lost connection after HELO". > > > >I added debug_peer_list to my main.cf to debug the ups connection. Is > >there a way to solve the problem? > > >May 28 09:13:15 genio postfix/smtpd[31295]: < > >ups-ced.domain.net[192.168.145.19]: EHLO > >May 28 09:13:15 genio postfix/smtpd[31295]: > > >ups-ced.domain.net[192.168.145.19]: 501 Syntax: EHLO hostname > >May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: > >0x558d6b58d9f0 > >May 28 09:13:15 genio postfix/smtpd[31295]: < > >ups-ced.domain.net[192.168.145.19]: HELO > >May 28 09:13:15 genio postfix/smtpd[31295]: > > >ups-ced.domain.net[192.168.145.19]: 501 Syntax: HELO hostname > >May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: > >0x558d6b58d9f0 > >May 28 09:13:15 genio postfix/smtpd[31295]: smtp_get: EOF > > looks like yout UPS does not provide hostname in EHLO/HELO message, > which postfix doesn't accept. > If you can't set up a hostname on your UPS, you'll have to accept such > invalid helo, perhaps as described on: > https://www.claudiokuenzler.com/blog/664/force-postfix-allow-empty-null-helo-ehlo-smtp-commands > > it would be better only to accept such helo from IP of the UPS, if > possible > > > Thank you, the filter works. Now the mail goes is blocked by amavis, but this is another problem. My UPS is very strange :-)) -- --- Enrico Morelli System Administrator | Programmer | Web Developer CERM - Polo Scientifico via Sacconi, 6 - 50019 Sesto Fiorentino (FI) - ITALY
Re: milter after queue
On 08-05-2020 14:11, NBNabble wrote: > I have a question to your hint using a null SMTP based listener. > > I am Using Ciphermail as an encryption gateway. > Pre-Queue mails are send to an external milter for Spam/Virus Checks. > After that, post-queue, the encryption gateway is a content_filter. > > I am looking for a solution to resend the mails to the milter again, after > the first content filter. > So in case there is malware in a decrypted mail, I also get that. > > Do you have any idea, how I could recheck the mails again with the milter? > Post queue? After the Ciphermail gateway (post-queue), the Ciphermail back-end sends the email back to Postfix on port 10026 for further delivery (reinjection). The default config for the reinjection port (10026) disables milters (see master.cf): receive_override_options=no_unknown_recipient_checks,no_header_body_checks,no_milters Try to see whether it works when you remove "no_milters" Kind regards, Martijn Brinkers
Re: lost connection after HELO
On 28.05.20 09:36, Enrico Morelli wrote: I've an UPS that should send me email in case of problems. The email do not arrive because in the log I see "lost connection after HELO". I added debug_peer_list to my main.cf to debug the ups connection. Is there a way to solve the problem? May 28 09:13:15 genio postfix/smtpd[31295]: < ups-ced.domain.net[192.168.145.19]: EHLO May 28 09:13:15 genio postfix/smtpd[31295]: > ups-ced.domain.net[192.168.145.19]: 501 Syntax: EHLO hostname May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: 0x558d6b58d9f0 May 28 09:13:15 genio postfix/smtpd[31295]: < ups-ced.domain.net[192.168.145.19]: HELO May 28 09:13:15 genio postfix/smtpd[31295]: > ups-ced.domain.net[192.168.145.19]: 501 Syntax: HELO hostname May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: 0x558d6b58d9f0 May 28 09:13:15 genio postfix/smtpd[31295]: smtp_get: EOF looks like yout UPS does not provide hostname in EHLO/HELO message, which postfix doesn't accept. If you can't set up a hostname on your UPS, you'll have to accept such invalid helo, perhaps as described on: https://www.claudiokuenzler.com/blog/664/force-postfix-allow-empty-null-helo-ehlo-smtp-commands it would be better only to accept such helo from IP of the UPS, if possible -- 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. On the other hand, you have different fingers.
lost connection after HELO
Dear, I've an UPS that should send me email in case of problems. The email do not arrive because in the log I see "lost connection after HELO". I added debug_peer_list to my main.cf to debug the ups connection. Is there a way to solve the problem? May 28 09:13:15 genio postfix/postscreen[31258]: CONNECT from [192.168.145.19]:51917 t o [192.168.146.39]:25 May 28 09:13:15 genio postfix/postscreen[31258]: WHITELISTED [192.168.145.19]:51917 May 28 09:13:15 genio postfix/smtpd[31295]: connect from ups-ced.domain.net[192.168.145.19] May 28 09:13:15 genio postfix/smtpd[31295]: smtp_stream_setup: maxtime=300 enable_dead line=0 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_e xceptions: ups-ced.domain.net ~? 127.0.0.0/8 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_exceptions: 192.168.145.19 ~? 127.0.0.0/8 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_exceptions: ups-ced.domain.net ~? [:::127.0.0.0]/104 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_e xceptions: ups-ced.domain.net ~? [::1]/128 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_e xceptions: 192.168.145.19 ~? [::1]/128 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_e xceptions: ups-ced.domain.net ~? 192.168.145.0/24 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_exceptions: 192.168.145.19 ~? 192.168.145.0/24 May 28 09:13:15 genio postfix/smtpd[31295]: > ups-ced.domain.net[192.168.145.19]: 220 genio.domain.net ESMTP Postfix (Debian/GNU) ay 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_create: SASL service=smtp, realm=(null) May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: noanonymous May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: Connecting May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: VERSION?1?2 May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: MECH?PLAIN?plaintext May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: plaintext May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: MECH?DIGEST-MD5?dictionary?active?mutual-auth May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: dictionary May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: active May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: mutual-auth May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply MECH?CRAM-MD5?dictionary?active May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: dictionary May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: active May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: MECH?LOGIN?plaintext May 28 09:13:15 genio postfix/smtpd[31295]: name_mask: plaintext May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: SPID?22734 May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: COOKIE?30c2eef14595100fc106f0be90d07d16 May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_connect: auth reply: DONE May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_mech_filter: keep mechanism: PLAIN May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_mech_filter: keep mechanism: DIGEST-MD5 May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_mech_filter: keep mechanism: CRAM-MD5 May 28 09:13:15 genio postfix/smtpd[31295]: xsasl_dovecot_server_mech_filter: keep mechanism: LOGIN May 28 09:13:15 genio postfix/smtpd[31295]: < ups-ced.domain.net[192.168.145.19]: EHLO May 28 09:13:15 genio postfix/smtpd[31295]: > ups-ced.domain.net[192.168.145.19]: 501 Syntax: EHLO hostname May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: 0x558d6b58d9f0 May 28 09:13:15 genio postfix/smtpd[31295]: < ups-ced.domain.net[192.168.145.19]: HELO May 28 09:13:15 genio postfix/smtpd[31295]: > ups-ced.domain.net[192.168.145.19]: 501 Syntax: HELO hostname May 28 09:13:15 genio postfix/smtpd[31295]: watchdog_pat: 0x558d6b58d9f0 May 28 09:13:15 genio postfix/smtpd[31295]: smtp_get: EOF May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_exceptions: ups-ced.domain.net ~? 127.0.0.0/8 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_exceptions: 192.168.145.19 ~? 127.0.0.0/8 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_exceptions: 192.168.145.19 ~? [:::127.0.0.0]/104 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostname: smtpd_client_event_limit_exceptions: ups-ced.domain.net ~? [::1]/128 May 28 09:13:15 genio postfix/smtpd[31295]: match_hostaddr: smtpd_client_event_limit_exceptions: 192.168.145.19 ~? [::1]/128 May 28 09:13:15 genio postfix/smtpd[31295]:
