Re: MySQL stored-procedure support for Postfix 3.2

On 12/25/2016 08:45 PM, Wietse Venema wrote: > John Fawcett: >>> I'll diff your new patch against the previous version and see what >>> changes you made. >> if you break out of the loop without reading all the result data you >> will get the following mysql e

Re: MySQL stored-procedure support for Postfix 3.2

On 12/26/2016 01:45 AM, Wietse Venema wrote: > I see room for two improvements: > - Don't loop on mysql_next_result() if that function returns an > error, to avoid going into an infinite loop. A break is needed in the case of >0 return code from mysql_next_result. while ((next_res_st

Re: Postfix delivery problem

On 12/27/2016 12:17 AM, G. Schlisio wrote: >> I managed to find where this is happening. It is not in glibc but in >> systemd. >> >> If your /etc/nsswitch.conf has something like this: >> >> passwd: compat mymachines systemd >> >> then the routines that are being used are systemd ones. >> >> Th

Re: MySQL stored-procedure support for Postfix 3.2

On 12/26/2016 10:35 PM, Wietse Venema wrote: > John Fawcett: >> so long as the loop continues in the presence of a zero return >> code from mysql_next_result() and mysql_store_result is called for >> each one we will stay in sync. With the break above we will be ok, >>

Re: Avoiding spam blacklists

On 12/28/2016 08:32 AM, Alice Wonder wrote: > Virtual machine for a web application, it is still in testing. > > reverse DNS is properly set up. > Postfix only listens on the local host. > Linux firewall drops anything not to port 80, 443, or a custom high > number port I use for SSH. > > This post

Re: Avoiding spam blacklists

On 12/28/2016 09:36 AM, Alice Wonder wrote: > On 12/28/2016 12:28 AM, John Fawcett wrote: >> On 12/28/2016 08:32 AM, Alice Wonder wrote: >>> Virtual machine for a web application, it is still in testing. >>> >>> reverse DNS is properly set up. >>> Post

Re: Postfix delivery problem

On 12/27/2016 08:59 AM, John Fawcett wrote: > On 12/27/2016 12:17 AM, G. Schlisio wrote: >>> I managed to find where this is happening. It is not in glibc but in >>> systemd. >>> >>> If your /etc/nsswitch.conf has something like this: >>> >>&g

Re: smtpd_sender_restriction

On 12/29/2016 11:13 AM, Martin Skjöldebrand wrote: > Den 2016-12-29 kl. 10:45, skrev Dominic Raferd: > >> Two possibilities occur to me - (a) the email is not 'really' from >> i...@rabattgatan.com, maybe this is the envelope sender or just the >> display name? or (b) if your mailserver is relaying

Re: Rate-limiting access to postfix on the firewall, what are decent numbers (depending on overall traffic)?

On 01/03/2017 01:37 PM, Gerben Wierda wrote: > My postfix MTA has been under a lot of DOS-like attention. Such as a botnet > sending many EHLO-requests, then password attempts: > ... > It does the first part from a multitude of machines. > > I want to stop this by setting a rate limiting rule in m

Re: Make smtp client talk through SSH tunnel?

On 01/04/2017 12:47 PM, Wietse Venema wrote: > Matthias Andree: >> Greetings and a happy new year, >> >> >> I still am in a situation where I occasionally need to have an SMTP >> client (preferable Postfix's) talk through an SSH tunnel. >> >> I know we have the smtp(8) client, and we have the pipe(

Re: connecting to mysql socket

On 04/07/2017 07:33 PM, Robert Moskowitz wrote: > > > On 04/07/2017 01:19 PM, Wietse Venema wrote: >> Robert Moskowitz: >>> I solved my mysql access problem with dovecot; turned out it was trying >>> a tcp connection and mysql is not listening on tcp. Fixed that to use >>> mysql.sock. >>> >>> So t

Re: Issue with SASL authentication

On 05/25/2017 06:20 PM, Daniel Bareiro wrote: > Hi! > > On 24/05/17 21:18, Daniel Bareiro wrote: > >> Hi again. >> >> On 24/05/17 17:46, Daniel Bareiro wrote: >> >>> Maybe this question is not 100% about Postfix, but it is related. I am >>> configuring a Postifx server with SASL authentication. >>>

HISTORY file typo

Hi Just saw this comment in the HISTORY file and noticed that the original and replaced values look just the same. 20170704 Typos (introduced: Postfix 2.10): in comments about IPv4-in-IPv6 addresses, replace :::1.2.3.4 with the correct form :::1.2.3.4. Incorrect o

Re: use different mysql databases for header_checks

On 01/05/2018 09:51 AM, Tavolodo Bela wrote: > Hello, > > I'd like to create a mysql lookup table for header_checks. > I think the following should do the trick: > > header_checks = mysql:/etc/posfix/header_checks.cf > > > header_checks.cf might l

Re: Postfix with sqlite - Database becomes locked

On 01/10/2018 09:28 PM, Sebastian Wolfgarten wrote: > Hi, > > I am uncertain as to what’s causing the DB to get locked - I am also running > Roundcube (webmail) on the server, maybe that’s the reason. I will check the > permission roundcube uses to access the db, I think it can be read-only which

Re: Testing Postfix-3.3....0-RC1

On 18/02/18 14:04, Wietse Venema wrote: > Christian Ro??ner: >> Hi, >> >> sorry for the delay. I gave a party at Friday and I did not find the time to >> anser faster. >> >>> Am 18.02.2018 um 00:48 schrieb Wietse Venema : >>> >>> postconf -xn | grep /etc/postfix/ldap > I copied those settings to m

Re: Testing Postfix-3.3....0-RC1

On 18/02/18 14:26, John Fawcett wrote: > On 18/02/18 14:04, Wietse Venema wrote: >> Christian Ro??ner: >>> Hi, >>> >>> sorry for the delay. I gave a party at Friday and I did not find the time >>> to anser faster. >>> >>>> Am

Suggestion: make compilation fail if m4 is not installed

Hi this is a strange error. I just had the chance to reinstall postfix from latest snapshot source on a new centos 7 server. When running postconf -n I was getting various errors relating to unused parameters from mysql map configuration files. This is an example of the message: postconf: warnin

Re: Suggestion: make compilation fail if m4 is not installed

On 25/02/18 03:09, @lbutlr wrote: > On 2018-02-24 (09:44 MST), John Fawcett wrote: >> due to the fact I had forgotten to install m4. > Interesting. m4 is part of my base install. At least I think it is, it's not > in /usr/local/... and i don't remember installing it

Re: Suggestion: make compilation fail if m4 is not installed

On 25/02/18 01:18, Wietse Venema wrote: > John Fawcett: >> >> I was wondering if it might be wise to make m4 a mandatory prerequisite, >> without which compilation would fail.? > We could add this at the top of the script: > > m4 > but that would be a

Re: Suggestion: make compilation fail if m4 is not installed

On 25/02/18 09:07, Peter wrote: > On 25/02/18 19:27, Bastian Blank wrote: >> On Sat, Feb 24, 2018 at 07:18:32PM -0500, Wietse Venema wrote: >>> We could add this at the top of the script: >>> m4 > Using "set -e" is much more effective and finds all errors. > Please no. set -e is an attempt to

Re: Suggestion: make compilation fail if m4 is not installed

On 25/02/18 08:54, @lbutlr wrote: > On 2018-02-25 (00:37 MST), John Fawcett wrote: >> I normally start out with the minimal set of packages and only add >> software that I need to those. While make was already there, the >> compiler and m4 were missing. I installed the compi

Re: Suggestion: make compilation fail if m4 is not installed

On 25/02/18 01:18, Wietse Venema wrote: > John Fawcett: >> I was wondering if it might be wise to make m4 a mandatory prerequisite, >> without which compilation would fail.? > We could add this at the top of the script: > > m4 > but that would be a point solu

Re: Question regarding VRFY

On 27/02/18 20:36, J Doe wrote: > Hi, > > I read in both the Postfix man file (man 5 postconf), and the SMTP RFC > (5321), that VRFY can be disabled on a site-by-site basis. > > I disabled this on my server for port 25 but am wondering if I should leave > this enabled on my Postfix instance that

Re: Question regarding VRFY

On 01/03/18 05:09, J Doe wrote: > Hi John, > >> On Feb 27, 2018, at 3:25 PM, John Fawcett wrote: >> I can't think of a compelling reason either to enable VRFY or to disable >> it. Disabling it stops people abusing it, but then they can just use >> RCPT TO to get

Re: Not receiving mail from some legitimate domains

On 06/03/18 19:12, jlftl wrote: > I have a server running Postfix (3.1.0-3ubuntu0.3) that has been in > production for a few months and is generally working well. However I've > been struggling to resolve an issue where some legitimate servers cannot > send inbound mail, where there appears to be

Re: LMTP and virtual users confusion

On 09/03/18 11:47, Joe Buck wrote: > Hi fair folks. After years of using OS X servers I'm back on FreeBSD and > well... owls have sure aged since then. > > So I'm trying to do a virtual domain+virtual users setup with Dovecot where > I'd have several virtual domains and several users. Each user is

Re: unknown recipient issue

On 09/03/18 11:40, Alfredo De Luca wrote: > Hi all.  > We have Postfix 2.10 as company mailserver.  > I noticed that when I send an email to a not-existing user mailbox in > our domain I don't receive an email back saying unknown mailbox or > similar. > > What do I need to do on main.cf

Re: Not receiving mail from some legitimate domains

On 12/03/18 07:12, jlftl wrote: > Wietse Venema wrote >> jlftl: >>> Thank you very much for the responses! >>> >>> This is a small, personal setup with low traffic so I will definitely >>> explore using notify_classes to try to get more feedback on the failures. >>> >>> Remote server legitmacy - *.

Re: Strange errors in mail.warn log

On 18/03/18 19:12, Mario wrote: > How to avoid getting strange records in the mail.warn file? > I started to receive it after Debian upgrade from jessie to stretch and > postfix upgrade from 2.11.3 to 3.1.8. > It is generated once, just after the system reboot. > > Despite the strange errors reco

Re: Add UTF8 support in PostgreSQL lookup table interface

On 24/08/18 22:54, Wietse Venema wrote: > Viktor Dukhovni: >> Yes, but that'd have to be done by the dictionary lookup layer, >> possibly in proxymap, based on a suitable signal from the lookup >> client, but the low-level API (dict_get()) does not presently >> support any per-lookup flags. So we'

Re: Add UTF8 support in PostgreSQL lookup table interface

ing(name, strlen(name))) { >> if (msg_verbose) >> msg_info("%s: %s: Skipping lookup of non-UTF-8 key '%s'", >> myname, dict_ldap->parser->name, name); >> return (0); >> } >> >> This code h

Re: dnsblog and "Name service error"

On 14/09/18 03:39, Alex wrote: > Hi, > > On Thu, Sep 13, 2018 at 7:56 PM Wietse Venema wrote: >> Alex: >>> Domain Name System (response) >>> Transaction ID: 0xded6 >>> Flags: 0x8182 Standard query response, Server failure >>> 1... = Response: Message is a response >>

hostnames in postscreen_access_list

Hi I was recently trying to whitelist a client hostname that frequently changes ip. >From the documentation check_client_access restriction for use with smtpd allows to specify access table lookups which contains hostnames. postscreen_access_list does not seem to allow hostnames in lookup tables

hostnames in postscreen_access_list

On 26/11/2018 23:18, Noel Jones wrote: > On 11/26/2018 1:53 PM, John Fawcett wrote: >> Hi >> >> I was recently trying to whitelist a client hostname that frequently >> changes ip. >> >> From the documentation check_client_access restriction for use with

Re: hostnames in postscreen_access_list

On 27/11/2018 00:09, Wietse Venema wrote: > John Fawcett: >> Hi >> >> I was recently trying to whitelist a client hostname that frequently >> changes ip. >> >> >From the documentation check_client_access restriction for use with >> smtpd allow

Logging suggestion

Hi I'd like to make two suggestions for additional logging. The first one is to leave an explicit trace in the log when starttls is enforced (for example on the submission port) but the client does not issue STARTTLS. The second one is to explicitly log that a protocol error has occurred. Curren

Small correction to a comment

Hi while looking through the code for the previous post I noticed that the return type for smtpd_sasl_auth_cmd in the comment does not correspond to the one in the code. John --- smtpd/smtpd_sasl_proto.c.orig    2018-12-29 12:00:06.168219924 +0100 +++ smtpd/smtpd_sasl_proto.c    2018-12-29 12:00

Re: Logging suggestion

On 29/12/2018 13:59, Patrick Ben Koetter wrote: > * John Fawcett : >> The first one is to leave an explicit trace in the log when starttls is >> enforced (for example on the submission port) but the client does not >> issue STARTTLS. > Have you tried to set reject_plainte

Re: Logging suggestion

On 29/12/2018 23:20, Wietse Venema wrote: > Sorry, I did not recognize the diff because all whitespace was using > UTF8 code points, and I read mail with a text editor that is optimized > for programing, not for text processing. > > After fixing the whitespace: Thanks for reviewing it further. I've

Re: Logging suggestion

On 30/12/2018 01:19, Wietse Venema wrote: > John Fawcett: >>> I would not log this for EVERY command. Especially because the >>> logged text size by far exceeds the command size (each logfile >>> record takes ~100 bytes, while the client needs to send only

Re: Logging suggestion

On 30/12/2018 18:05, Wietse Venema wrote: > John Fawcett: >> On 30/12/2018 01:19, Wietse Venema wrote: >> Here's a revised patch implementing the above logging. >> >> I did not take out the existing pipelining logging since it provides >> additional

Re: Logging suggestion

On 30/12/2018 20:20, John Fawcett wrote: > On 30/12/2018 18:05, Wietse Venema wrote: >> John Fawcett: >>> On 30/12/2018 01:19, Wietse Venema wrote: >>> Here's a revised patch implementing the above logging. >>> >>> I did not take out the existing p

Re: Logging suggestion

On 01/01/2019 17:56, Wietse Venema wrote: > John Fawcett: >>>> JFTR, this is what a full implementation would look like. >>>> A full implementation would update a new SMTP_STATE violation_mask >>>> field for specific violation categories (syntax, pipeli

Re: Limiting global number of outgoing connections

On 03/01/2019 11:23, Lorenzo Milesi wrote: > Hi. > > I need to limit the maximum number of outgoing SMTP connections done by > Postfix for delivering messages. > Our VPS provider is limiting to 5 conns/s, so I need Postfix not to open more > than 5 connections to remote SMTP servers. > > I canno

Re: SMTP filter using geo-localization

On 05/01/2019 22:26, Philippe - Forums wrote: > Hello, > > I would like to filter SMTP access using geo-localization. > > I have installed geoip-bin on my mailserver. > > This tool works like nslookup with an IP (geoiplookup @IP) and give > geographic informations about this IP and especially the c

Re: Turn off command pipelining for a domain

On 06/01/2019 03:24, Lefteris Tsintjelis wrote: > Is there a possible way to turn off command pipelining completely for > a whole domain based on DNS? The pipelining-firewalling of yahoo.com > seems to be broken quite often. > > Something like: > > yahoo.com    pipelining I think you're looking fo

Re: Assistance to protect from spam flood

On 12/01/2019 12:09, Nick Howitt wrote: > Hi all, > Until recently I did not receive too much spam and had it pretty-much > under control. This week has gone mental. So far this week I have > received 29860 connection attempts form {some_random_number}@qq.com to > {the_same_random_number}@howitts.c

Re: Assistance to protect from spam flood

On 12/01/2019 15:23, Nick Howitt wrote: > > > On 12/01/2019 11:43, John Fawcett wrote: >> On 12/01/2019 12:09, Nick Howitt wrote: >>> Hi all, >>> Until recently I did not receive too much spam and had it pretty-much >>> under control. This week has gone me

Re: Assistance to protect from spam flood

On 12/01/2019 15:52, Nick Howitt wrote: > > > On 12/01/2019 14:47, John Fawcett wrote: >> restrictions only for inbound email on port 25 they may block some badly >> configured servers, but I don't think its a big issue. YMMV. I'd >> configure the backup se

Re: Assistance to protect from spam flood

On 12/01/2019 21:58, Nick Howitt wrote: > > > On 12/01/2019 16:42, @lbutlr wrote: >> On 12 Jan 2019, at 07:52, Nick Howitt wrote: >>> Unfortunately I don't have access to the MX Backup service. It is >>> provided by my DNS provider. >> Honestly, you should not have an MX server outside of your con

Re: Mysql and postfix mail que

On 03/02/2019 07:51, JDN wrote: > hello you all > > > Can I set a mysql database for the mails that our in the mail que to get > send? and map that database to two postfix servers that our behind a F5 load > balancer set active passive? > > so if active goes down the second one still could send th

Re: How to act based on the interface on which the mail was received?

On 11/02/2019 08:42, RA wrote: > Hi. > > I have this postfix instance to relay all mail to a relay host but I wish to > make this instance also an archiving MX for a domain. Initially the > configuration was: > > mynetworks = 127.0.0.0/8 > mailbox_size_limit = 0 > inet_interfaces = loopback-only

Re: Unexpected directories in virtual_mailbox_base

On 27/02/2019 17:56, Thomas Seilund wrote: > Hi All, > > I run a mail server with Postfix (version 2.6.6), Dovecot and > Spamassassin. > > The first time I saw an unexpected directory in virtual_mailbox_base > what medio dec. 2018. The mail server has been running for 5+ years. > > There are more d

latest 3.5 experimental release

Hi Wietse just in case you're not aware of it: the latest experimental release does not seem to be present at this link ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/postfix-3.5-20190301.tar.gz or the equivalent mirror links. John

Re: unknown tls_ssl_options value "tlsext_padding"

On 30/03/2019 21:20, A. Schulze wrote: > Hello, > > postfix-3.4.4 linked with openssl-1.1.1b > > $ postconf tls_ssl_options > tls_ssl_options = no_compression, tlsext_padding > > produce such log: > Mar 30 21:04:12 danube postfix/smtpd[9075]: warning: unknown tls_ssl_options > value "tlsext_paddin

Re: Postfix and smfi_setmlreply() milter command resulting in SMTP protocol breakage.

On 02/04/2019 10:48, Andreas Thienemann wrote: > Hi, > > I have a locally developed milter using the python-milter bindings > which seems to trigger a Postfix bug. > > The milter in question uses the smfi_setmlreply() command to set a > multiline response as defined in rfc5321. > > Multiline replie

Re: GF 3.3, unsupported dictionary type: mysql

On 06/04/2019 01:43, li...@sbt.net.au wrote: > I'm trying to migrate server to new vm, installed postfix* from GF (1) > > but, after copying over main.cf/master.cf get this: > > > Apr 6 00:34:46 emu postfix/proxymap[15601]: error: unsupported dictionary > type: mysql > Apr 6 00:34:46 em

Re: I need some help with the correct value for myhostname in main.cf

On 07/04/2019 20:14, Chris Green wrote: > ... > > The machine on which postfix runs is called esprimo and thus, within > my LAN, its name is esprimo.zbmc.eu. However the above seems to mean > that mail sent outside gets the name esprimo.zbmc.eu in its headers > and that seems to have provoked some

Re: Route unknown user to new domain

On 25/04/2019 18:42, luis.dominguez wrote: > Hello. I'm using postfix + dovecot for my example.com domain, but i > want that any missing local users change the mail to @net.example.com > and go to my relay host. I was configured luser in postfix but when I > send a mail to a unknown user is not wor

Link for experimental postfix-3.5-20190418

Hi is this the right link for the latest experimental release? I can't seem to get it to work. http://ftp.porcupine.org/mirrors/postfix-release/experimental/postfix-3.5-20190418.tar.gz John

Re: Link for experimental postfix-3.5-20190418

On 28/04/2019 23:38, Viktor Dukhovni wrote: > On Sun, Apr 28, 2019 at 11:17:01PM +0200, John Fawcett wrote: > >> is this the right link for the latest experimental release? I can't seem >> to get it to work. >> >> http://ftp.porcupine.org/mirrors/postfix-releas

Re: TLS client certificates and auth external

On 28/04/2019 21:49, Wietse Venema wrote: > ... > > Once the above is implemented, the same approach could be used to > improve other parts of Postfix by making existing hard-coded behavior > configurable, for example how check_client_access looks up subnet > and partial address information, or how

Re: TLS client certificates and auth external

On 01/05/2019 22:04, Viktor Dukhovni wrote: > On Wed, May 01, 2019 at 09:57:29PM +0200, John Fawcett wrote: > >>> virtual_alias_maps = { >>> hash:/etc/postfix/virtual, >>> { search = full, full-noext, localpart-if-local, at-domain } &g

Re: AWS timeout

On 14/05/2019 01:27, Wietse Venema wrote: > Wietse Venema: >> If you look at the non-VPN captures, then you will see the following: >> >> - In one trace, we see a client ACK 138, followed by a client packet >> with "." (data 443:446, ACK 138, and a timestamp field >> tht is unlike those of al o

Re: AWS timeout

On 14/05/2019 01:27, Wietse Venema wrote: > Wietse Venema: >> If you look at the non-VPN captures, then you will see the following: >> >> - In one trace, we see a client ACK 138, followed by a client packet >> with "." (data 443:446, ACK 138, and a timestamp field >> tht is unlike those of al o

[pfx] Re: 25 years today

On 14/12/2023 14:20, Wietse Venema via Postfix-users wrote: As a few on this list may recall, it is 25 years ago today that the "IBM secure mailer" had its public beta release. This was accompanied by a nice article in the New York Times business section. Thanks Wietse and to all who have con

[pfx] Re: Regarding reject_unlisted_sender and preventing sender address spoofing

On 05/01/2024 19:44, Taco de Wolff via Postfix-users wrote: Hi, I'm trying to understand how the reject_unlisted_sender option works in the smtpd_sender_restrictions option. This is what I understand it to do: For any received mail (it is an smtpd option after all), either for receiving ma

[pfx] Re: recipient_bcc_maps clarification.

On 08/01/2024 05:54, anant--- via Postfix-users wrote: Hello, We have in main.cf always_bcc = zz...@xx.com and our domain is xx.com For specific 2 recipients of our domain, we don't want always_bcc to be implemented.  ie. if a mail is addressed to a...@xx.com  (our domain only), mail should

[pfx] Re: relay_domains override for smtpd

On 16/01/2024 18:12, Marc Dierksen via Postfix-users wrote: Salutations, I am running Postfix 3.5.23 on Debian 11 as an edge mailserver that accepts mails on port 25 for a list of domains defined as relay_domains in the main.cf. I am currently trying to setup a second smtpd process on port

[pfx] Re: client checks with suspect IPs

On 16/01/2024 20:28, Alex via Postfix-users wrote: Hi, I need help with making a decision involved in determining whether to add an IP to my client_checks to bypass a blocklist entry on the Barracuda blocklist that is impacting one of our users. The problem is that this would also bypass the

[pfx] Re: Dovecot logging to files causes postfix to break

On 18/05/2024 18:18, Richard Rosner via Postfix-users wrote: Am 18.05.24 um 17:55 schrieb Wietse Venema: Richard Rosner via Postfix-users: I have a mailing server setup based on Debian Stable that uses postfix for IMAP and SMTP and dovecot for internel mail handling, You mean, Postfix for SMT

[pfx] Re: SASL reject force disconnect

On 24/05/2024 03:03, John Hill via Postfix-users wrote: I learn something every time I read this group, when I can keep up with the conversation! I had auth on ports I did not need. I use auth on submission port 587, for users access. I do get a boat load of failed login attempts on 587. F

[pfx] Re: How to allow only one specific sender to use smtp ?

On 25/05/2024 23:58, Mike via Postfix-users wrote: Hello, My setup like below: I have Postfix setup and use dovecot as SASL. Now, all email accounts can use the smtp server to send emails. I want to allow only one email account to send out emails and rest of others can only use POP3 or IMAP

[pfx] Re: SASL reject force disconnect

On 25/05/2024 20:50, John Hill via Postfix-users wrote: On 5/25/24 11:22 AM, John Fawcett via Postfix-users wrote: On 24/05/2024 03:03, John Hill via Postfix-users wrote: I learn something every time I read this group, when I can keep up with the conversation! I had auth on ports I did

[pfx] Re: SASL reject force disconnect

On 27/05/2024 13:31, John Hill via Postfix-users wrote: On 5/27/24 4:13 AM, Matus UHLAR - fantomas via Postfix-users wrote: > postscreen_dnsbl_sites = zen.spamhaus.org=127.0.0.[2..11] John Hill via Postfix-users: Is this the same thing? On 25.05.24 15:54, Wietse Venema via Postfix-users

[pfx] Re: SASL reject force disconnect

On 28/05/2024 11:39, Christophe Kalt via Postfix-users wrote: On Sun, May 26, 2024 at 5:57 AM John Fawcett via Postfix-users wrote: For submission I only use xbl (return code 127.0.0.4) excluding other other data contained in zen like pbl that lists isp dynamic ip ranges from

[pfx] Re: Masters.cf

On 29/05/2024 00:27, John Hill via Postfix-users wrote: On 5/28/24 4:50 PM, John Hill via Postfix-users wrote: On 5/28/24 4:43 PM, Benny Pedersen via Postfix-users wrote: John Hill via Postfix-users skrev den 2024-05-28 22:12: On 5/28/24 3:38 PM, Benny Pedersen via Postfix-users wrote: Joh

[pfx] Re: Masters.cf

On 29/05/2024 01:11, Bill Cole via Postfix-users wrote: On 2024-05-28 at 18:50:11 UTC-0400 (Wed, 29 May 2024 00:50:11 +0200) John Fawcett via Postfix-users is rumored to have said: [...] Hi John I think you are missing the following in master.cf for the submission service -o

[pfx] Re: Masters.cf

On 29/05/2024 02:18, John Hill via Postfix-users wrote: On 5/28/24 8:10 PM, John Hill via Postfix-users wrote: On 5/28/24 8:00 PM, Bill Cole via Postfix-users wrote: On 2024-05-28 at 19:18:10 UTC-0400 (Tue, 28 May 2024 19:18:10 -0400) John Hill via Postfix-users is rumored to have said: [..

[pfx] Re: Masters.cf

On 29/05/2024 14:07, Viktor Dukhovni via Postfix-users wrote: On Wed, May 29, 2024 at 07:26:10AM -0400, John Hill via Postfix-users wrote: The wrapper-mode TLS "smtps" rejects are naturally after the TLS handshake.    465    inet  n   -   n   -   -   smtpd     -

[pfx] Re: Masters.cf

17:46, John Fawcett via Postfix-users wrote: On 29/05/2024 14:07, Viktor Dukhovni via Postfix-users wrote: On Wed, May 29, 2024 at 07:26:10AM -0400, John Hill via Postfix-users wrote: The wrapper-mode TLS "smtps" rejects are naturally after the TLS handshake.    465 

[pfx] Re: managesieve filter not working

On 04/06/2024 11:18, Celal.Dikici via Postfix-users wrote: Hello, For the e-mail infrastructure we use roundcube 1.6.6 postfix 3.7.10, dovecot 2.3.19.1 installed on debian 12.05.  We use the larry theme as the interface. We use managesieve plugin for filtering. I have extracted some configura

[pfx] Re: dnsbl submissions

On 07/07/2024 06:18, Nick Edwards via Postfix-users wrote: Howdy, I've never seen the point in this before, but i've been asked by a client to implement it if possible, that is, place dnsbl checks on submission and smtps connections, I've tried a few combinations but it does not seem to be wo

[pfx] Re: dnsbl submissions

On 07/07/2024 13:09, Victoriano Giralt via Postfix-users wrote: El dom, 07-07-2024 a las 12:51 +0200, John Fawcett via Postfix-users escribió: On 07/07/2024 06:18, Nick Edwards via Postfix-users wrote: ... I haven't personally used the $ syntax you're using so I can't say

[pfx] Re: Does unix:passwd.byname do anything in local_recipient_maps on MacOS?

On 07/07/2024 18:57, Robert Fuhrer via Postfix-users wrote: Hi, I'm running PostFix 3.2.2 on Mac OS Sonoma, configured to accept local delivery for a single local login user, i.e. a user that actually has an account on the Mac. To that end, I have the following in main.cf: local_recipien

[pfx] Re: Local delivery for both login and virtual users in a single domain?

On 07/07/2024 18:59, Robert Fuhrer via Postfix-users wrote: Hi, I've got a Mac running PostFix 3.2.2, configured for local delivery for a single domain, call it "mydomain.net ", using dovecot's local delivery agent. At the moment, there's just one relevant login user o

[pfx] Re: Local delivery for both login and virtual users in a single domain?

ut perhaps PostFix’s invocation of the Dovecot LDA overrides the path using the “home_mailbox”. (?) In that case, without virtual_mailbox_base, I don’t see how to point PostFix to the right Maildir for non-login users. Thanks so much for the help!! Cheers,  - Bob On Jul 7, 2024, at 4:12 PM, John Fawce

[pfx] Re: Mysteries of user semi-banning

On 12/07/2024 00:14, John R. Levine via Postfix-users wrote: Last month I asked for advice on limiting specific senders to specific recipients, and Wietse offered this: /etc/postfix/main.cf:     smtpd_sender_restrictions =     check_sender_access hash:/etc/postfix/restricted_senders     sm

[pfx] Re: How to bounce e-mail when using catchall

On 12/07/2024 07:17, Francis Augusto Medeiros-Logeay via Postfix-users wrote: On 11 Jul 2024, at 20:22, Bill Cole via Postfix-users wrote:  On 2024-07-11 at 02:42:26 UTC-0400 (Thu, 11 Jul 2024 06:42:26 +) Francis Augusto Medeiros-Logeay via Postfix-users is rumored to have said:

[pfx] Re: How to bounce e-mail when using catchall

On 12/07/2024 15:30, Ralph Seichter via Postfix-users wrote: I can imagine a custom milter which stores message data, rejects the original SMTP delivery attempt after the end of the DATA phase, and later re-injects the captured data in some fashion (not necessarily using SMTP), but this way

[pfx] Re: How to bounce e-mail when using catchall

one point was badly worded below, the following is better: If you accepted both valid and invalid recipients your reject would be for both recipients. (I implied the reject went to the receipient which is nonsense). On 12/07/2024 16:59, John Fawcett via Postfix-users wrote: On 12/07/2024

[pfx] Re: Now Dovecot doesn't like me

On 12/07/2024 23:13, John R. Levine via Postfix-users wrote: Hi, now that Viktor spotted the config error and fixed yesterday's problem, I'm back with what I hope is another dumb question. Having wrestled Cyrus authentication to a draw, now I'm trying Dovecot which I would have hoped would be

[pfx] Re: Now Dovecot doesn't like me

On 12/07/2024 23:56, John Levine wrote: It appears that John Fawcett via Postfix-users said: I didn't see anywhere what your value of smtpd_sasl_type is (as applicable to the sasl type used by the smtp server. Bingo. Thanks. In my defence, if you look at https://www.postfix.org/postc

[pfx] Re: Now Dovecot doesn't like me

On 13/07/2024 02:27, Viktor Dukhovni via Postfix-users wrote: On Sat, Jul 13, 2024 at 12:01:38AM +0200, John Fawcett via Postfix-users wrote: I checked https://www.postfix.org/postconf.5.html and I can see: smtpd_sasl_type (default: cyrus)     The SASL plug-in type that the Postfix SMTP

[pfx] Re: How to bounce e-mail when using catchall

On 13/07/2024 06:54, Francis Augusto Medeiros-Logeay via Postfix-users wrote: Hi everyone, Thanks a lot for your feedback. I learned a lot. So I’ll forget the whole thing. I have a last question, though: are there disadvantages of using a catchall compared to not using it, just letting mes

[pfx] Re: How to bounce e-mail when using catchall

On 13/07/2024 12:50, Francis Augusto Medeiros-Logeay via Postfix-users wrote: Thanks a lot John and Peter! In fact this is a family server, so it’s kinda important for us to not miss emails. And it happened once that mails were not delivered because of typos. I was a bit worried about nas

[pfx] [OT] Null MX or not?

Hi this is completely off topic for this list (there is only a marginal connection since Postfix is the MTA but it's not a Postfix question), but maybe someone has knowledge on this. I came across something that I have not seen before: a domain (call it example.com) that has no email address

[pfx] Re: [OT] Null MX or not?

On 31/07/2024 23:34, Wietse Venema via Postfix-users wrote: I came across something that I have not seen before: a domain (call it example.com) that has no email addresses. No one sends or receives email for that domain. If there is no email from sen...@example.com, the domain should say so in

[pfx] Re: [OT] Null MX or not?

On 01/08/2024 09:32, Laura Smith via Postfix-users wrote: My doubt is that since the outgoing email server identifies itself as host1.example.com in the EHLO, is there a requirement or even an expectation that postmas...@example.com will be able to receive email. I think the reality is tha

<    1   2   3   >