[pfx] Re: Thunderbird not connecting in-time
Thanks - will re-focus investigation. (evidently web-searching led in wrong direction) -- Regards =dn ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
On 13/03/2023 12.05, Scott Kitterman via Postfix-users wrote: On Sunday, March 12, 2023 7:02:41 PM EDT Gerald Galster via Postfix-users wrote: ... My recommendation to the OP would be to reconsider what they are trying to accomplish and what's the simplest way to do so. Through this thread I haven't seen anything that would need MySQL or for which MySQL would make things particularly easier. Keep it simple to start and only and more moving parts if you really need them. +1 Irony: some of us found the MySQL option easier than trying to understand a different file-format, and the 'compile' (equivalent) function... -- Regards =dn ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
Steffen Nurpmeso via Postfix-users: > Postfix users wrote in > <4pzsd16nkpzj...@spike.porcupine.org>: > ... > |Postfix must wait for fsync() to complete (or whatever its Cloud > |equivalent is), before it can take responsibility for delivery of > > (postfix does not support FULLFSYNC on MacOS.) Indeed. Postfix requires POSIX semantics, not platform-specific stuff. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
On Sunday, March 12, 2023 7:02:41 PM EDT Gerald Galster via Postfix-users wrote: > > unfortunately I don't know this topic, but I'm really willing to study. > > Please do you have any documentation on this? > Sorry, I can't recommend an up to date howto. Perhaps other list members can > help. > > A lot of links at https://www.postfix.org/docs.html are outdated or do not > exist anymore. My recommendation to the OP would be to reconsider what they are trying to accomplish and what's the simplest way to do so. Through this thread I haven't seen anything that would need MySQL or for which MySQL would make things particularly easier. Keep it simple to start and only and more moving parts if you really need them. Scott K ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
> unfortunately I don't know this topic, but I'm really willing to study. > Please do you have any documentation on this? Sorry, I can't recommend an up to date howto. Perhaps other list members can help. A lot of links at https://www.postfix.org/docs.html are outdated or do not exist anymore. Best regards, Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Thunderbird not connecting in-time
On Mon, Mar 13, 2023 at 11:16:26AM +1300, DL Neil via Postfix-users wrote: > Which setting will extend the amount of time allowed for Thunderbird to > connect to send and/or receive messages from Postfix? Postfix is not involved in MUA access to read mail, that's your IMAP server, Dovecot or Cyrus are the most popular options. Only *sending* of mail involves the Postfix submission service. > Brother-in-law is on a very slow connection to the family's server. > Long-ish wi-fi link to the router, through Starlink satellite system, > and (literally) from one side of the world to the other, to the VPS. > > Thunderbird regularly fails to sync before timing-out. "Sync" of email is likely IMAP. > Which setting should be extended? Should more than one time-out value > be expanded? What are the risks associated with increasing such > time-outs? Postfix timeouts for mail submission are quite generous, even for users half-the-world away. You shouldn't need to change any of the timeouts. -- Viktor. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
Postfix users wrote in <4pzsd16nkpzj...@spike.porcupine.org>: ... |Postfix must wait for fsync() to complete (or whatever its Cloud |equivalent is), before it can take responsibility for delivery of (postfix does not support FULLFSYNC on MacOS.) --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: sender address verification: easy bypass for myhostname/mydomain?
Steffen Nurpmeso wrote in <20230312003030.4aldj%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20230311003215.yvtaf%stef...@sdaoden.eu>: ||I see a thread for "double-bounce check applied to itself" from ||February 2021,[.] | ... ||Is there an easy (non-DNS etc) way to say that @sdaoden.eu (or ||even @(.+\.)?sdaoden\.eu MUST NOT come from the outside, so | |Forget about this, i am just too stupid. ... Risking to talk only to myself .. it is of course even worse and a "check_sender_access" could very well have been used, too. I know that. (Now, again; that is. Whoever thought it.) P.S.: but having a shortcut instead of a fully grown thing like check_sender_access (or bl[ao]listing via some policy server) would also be a good thing. That turned my Sunday gray, so to say. Ciao. P.P.S.: regarding the list i am wondering when that "[TAG] Re:" thing started -- now that i see it here, i also consciously see it on other MLs i am subscribed to. This indeed breaks the thread display "squeezing" here, with my MUA, i wonder how other deal with that; ie, in thread display only the first message shows the subject, the remaining only the thread structure tree, for as long as the subject is the same, or only extended via Re:. But this is off-topic for postfix. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Thunderbird not connecting in-time
Which setting will extend the amount of time allowed for Thunderbird to connect to send and/or receive messages from Postfix? NB postfix uses Submission -> smtpd (I've found references to Relay cf Submission but don't appreciate difference) or should it be an lmtp setting vis-a-vis Dovecot? Brother-in-law is on a very slow connection to the family's server. Long-ish wi-fi link to the router, through Starlink satellite system, and (literally) from one side of the world to the other, to the VPS. Thunderbird regularly fails to sync before timing-out. Which setting should be extended? Should more than one time-out value be expanded? What are the risks associated with increasing such time-outs? Would such an adjustment better be made in his Thunderbird config rather than to Postfix? -- Regards, =dn ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
On 13/03/2023 02.10, Antonino Di Mauro via Postfix-users wrote: unfortunately I don't know this topic, but I'm really willing to study. Please do you have any documentation on this? https://dev.mysql.com/doc/refman/8.0/en/ I'm no expert on Postfix, but can talk about databases. To help with your understanding of the system, and our understanding of the problem you face (and perhaps any language-barrier), let's try the following:- As a first step, let's see if the database is set-up correctly (and if postfix has been given two essential elements to link with MySQL). If these are working, then we can move-on to looking at postfix problems... If you would like to check your settings against a working-example, here is what is working for these domains: main.cf (includes) virtual_mailbox_domains = mysql:/etc/postfix/auth/mysql_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/auth/mysql_users.cf virtual_alias_maps = mysql:/etc/postfix/auth/mysql_aliases.cf Thus, there are three files which configure how MySQL is to respond to Postfix enquiries. Taking one of them as an example: mysql_domains.cf user = userNM password = secret hosts = host dbname = dbname query = SELECT 1 FROM dbname.domains WHERE domainNM='%s' NB your system will use different data-values. Substitute those values for what is written below. The three .cf files are very similar. Please check all of them, and discuss any differences in a reply 'here'... Also, if you have handled the db-credentials differently, make appropriate adjustments - this is the simple method illustrated in most web-page how-tos! First, check that MySQL is up-and-running: systemctl status mysql ... Active: active (running) (your system may require a different command, but ultimately the next step will reveal whether the RDBMS is running - or not. Am also assuming Dovecot (or whatever) is also up-and-running) To check that the database logic will work, from the command-line on the server log in to MySQL: mysql -u userNM -p -h host It will then ask: Enter password: secret and respond with: Welcome to the MySQL monitor. Commands end with ; or \g. ... mysql> Copy the query from the .cf file (everything from SELECT onwards, and substitute valid database/schema and domain-names (in this case): mysql> SELECT 1 FROM dbname.domains WHERE domainNM='rangi.cloud'; +---+ | 1 | +---+ | 1 | +---+ 1 row in set (0.00 sec) The response of "1" says that MySQL found exactly one domain called "rangi.cloud" (in my case) in the table. Not finding anything means that the definition is missing - finding two would be unnecessary/greedy!. A number greater than zero proves that the MySQL part works correctly. How does the MySQL server respond to the three .cf files' queries? There are other settings to examine if the above all works as-planned, but the system is still not working correctly... -- Regards =dn ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
i try to remove "smtp_sasl_password_maps" to main.cf but external mail not send ! In the log file, i can see "fatal error smtp_sasl_password_maps". I honestly don't know how to fix it... Il 2023-03-12 13:26 Gerald Galster via Postfix-users ha scritto: I have checked the commands you listed in your first email, but I do not find any errors in the database, table, or MySQL service. Perhaps, as you say, this is not the correct path for the configuration. Currently you are connecting via unix domain sockets. Mysql usually listens to 127.0.0.1 port 3306 (tcp) as well. You could try that but beware that mysql treats connections from unix domain sockets and tcp differently. You might need to allow (grant) host '127.0.0.1' access for mysql postfix user. It may be easier to locate the unix domain socket. You can configure the path via hosts: https://serversmtptrail.com/tracking/qaR9ZGp0AwV3AwplBQtmAGVkBGD1AvM5qzS4qaR9ZQbjHt I already suggested how you could locate the socket path. I just want to send mail directly from the Postfix server without a relayhost. Then you don't neet smtp_sasl_password_maps. Leave it empty. For testing purposes try to send an email via console/ssh, e.g. using /usr/bin/mailx and watch your maillog. Best regards, Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
Demi Marie Obenour via Postfix-users: > On 3/12/23 01:21, Bill Cole via Postfix-users wrote: > > On 2023-03-12 at 00:03:32 UTC-0500 (Sun, 12 Mar 2023 00:03:32 -0500) > > Phil Stracchino via Postfix-users > > is rumored to have said: > > > >> On 3/11/23 19:04, pyh--- via Postfix-users wrote: > >>> Hello list, > >>> > >>> Is it possible to use an object storage system (like aws's S3) to > >>> store > >>> message files? if this can be implemented we may have a more > >>> persistent > >>> storage for email. AFAIK aws's S3 has three replicas for each file in > >>> their system by default. > >> > >> > >> S3 really isn't intended to be used that way. I'm not sure how you'd > >> make that work and it would probably be a bad idea. > > > > Agreed. > > > > As far as Postfix specifically is concerned (i.e. the queues) S3 would > > be a performance disaster. > > Is this because Postfix is designed assuming that queue access has low > latency, and therefore does not try to hide the latency with asynchronous > operations and batching? Postfix must wait for fsync() to complete (or whatever its Cloud equivalent is), before it can take responsibility for delivery of a message. Only then can the sender delete that message from their mail queue. This waiting introduces latency. Postfix can receive and deliver messages in parallel (default 100 parallel connections), but those transactions compete for access to the mail queue. And there is only one scheduler. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
On 3/12/23 01:21, Bill Cole via Postfix-users wrote: > On 2023-03-12 at 00:03:32 UTC-0500 (Sun, 12 Mar 2023 00:03:32 -0500) > Phil Stracchino via Postfix-users > is rumored to have said: > >> On 3/11/23 19:04, pyh--- via Postfix-users wrote: >>> Hello list, >>> >>> Is it possible to use an object storage system (like aws's S3) to >>> store >>> message files? if this can be implemented we may have a more >>> persistent >>> storage for email. AFAIK aws's S3 has three replicas for each file in >>> their system by default. >> >> >> S3 really isn't intended to be used that way. I'm not sure how you'd >> make that work and it would probably be a bad idea. > > Agreed. > > As far as Postfix specifically is concerned (i.e. the queues) S3 would > be a performance disaster. Is this because Postfix is designed assuming that queue access has low latency, and therefore does not try to hide the latency with asynchronous operations and batching? -- Sincerely, Demi Marie Obenour (she/her/hers) ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: [P-U] Re: New List Host and Reply-to Header
Ralf Hildebrandt via Postfix-users skrev den 2023-03-12 16:10: * Patrick Ben Koetter via Postfix-users : approach to subscriber self management. Once you've become a registered MLM platform participant you can easily change settings that will apply to all lists you've subscribed to in one place. I consider that a great usability benefit for subscribers. Furthermore, mm2 get's rid of the awful "this is your password" mails. not always that mailman 3 have password set pr new user, so users need to use lost password, to get access to web admin page, even users are added from majordomo :=) looking forward to see postfix.org do support dane and have arc seal/arc signing back, where rspamd do arc-seal/arc-sign before mailman 3 see any thing i dont use rspamd, if rspamd is doing it right, it possible already works, lol :=) ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: [P-U] Re: New List Host and Reply-to Header
* Patrick Ben Koetter via Postfix-users : > approach to subscriber self management. Once you've become a registered > MLM platform participant you can easily change settings that will apply to all > lists you've subscribed to in one place. I consider that a great usability > benefit for subscribers. Furthermore, mm2 get's rid of the awful "this is your password" mails. -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
PGNet Dev via Postfix-users skrev den 2023-03-12 14:46: systemctl list-units | egrep "regex|clam|spam|dkim" |grep service clamav-daemon.serviceloaded active running clamd scanner clamav-milter.serviceloaded active running clamav milter dkimpy-milter.serviceloaded active running dkimpy milter mregex.service loaded active running regex milter spamassassin-milter.service loaded active running SA milter spamd.serviceloaded active runningSA daemon works great except dkimpy-milter installed from pip3 install dkimpy-milter does not support pep517, with makes it impossible to make gentoo ebuilds for it in the tarball it have dkimpy_milter dir, and the tarball in pypi is dkimpy-milter, details mater in gentoo portage ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
Wietse Venema via Postfix-users:
> EML via Postfix-users:
> > I've written a before-queue milter that I'm trying to integrate with
> > Postfix, but there doesn't seem to be any specific documentation on how
> > to do this. During development, I ran the milter manually, listening on
> > port 7950, with nothing in master.cf, and this in main.cf:
> >
> > smtpd_milters = inet:localhost:7950
> > non_smtpd_milters = $smtpd_milters
> >
> > This works. For production, I'd like to get Postfix to run the milter,
> > so I've added this to master.cf:
> >
> > 7950 inet n y n 0 - samilter { -p inet:7950@localhost }
> >
>
> You can only run POSTFIX programs this way.
>
> Non-Postfix program can be run with the pipe(8) daemon (for transient
> programs) and spawn(8) daemon (for persistemt programs).
Actually, both are for running a transient command. This setup is
not suitable for Milters that want to create their own socket, it
is for programs that read from stdin and that write to stdout.
Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
EML via Postfix-users:
> I've written a before-queue milter that I'm trying to integrate with
> Postfix, but there doesn't seem to be any specific documentation on how
> to do this. During development, I ran the milter manually, listening on
> port 7950, with nothing in master.cf, and this in main.cf:
>
> smtpd_milters = inet:localhost:7950
> non_smtpd_milters = $smtpd_milters
>
> This works. For production, I'd like to get Postfix to run the milter,
> so I've added this to master.cf:
>
> 7950 inet n y n 0 - samilter { -p inet:7950@localhost }
>
You can only run POSTFIX programs this way.
Non-Postfix program can be run with the pipe(8) daemon (for transient
programs) and spawn(8) daemon (for persistemt programs).
Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
Dnia 12.03.2023 o godz. 12:43:00 EML via Postfix-users pisze: > I can run the milter as a > service, if necessary, instead of adding an entry in master.cf, but > this feels like the wrong way to do this. Thanks. It's actually the proper way to do this. Milters are separate services that Postfix communicates with, and it is their job to care for their own startup, not Postfix's. -- Regards, Jaroslaw Rafa r...@rafa.eu.org -- "In a million years, when kids go to school, they're gonna know: once there was a Hushpuppy, and she lived with her daddy in the Bathtub." ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
That's a surprise - thanks. I've just checked and seen that opendkim and opendmarc set up init-style services. I'll do a systemd service for this milter, but I'd be interested to hear if there's any policy or other advice about whether we should be using master.cf or a service. ultimately up to you. my $0.02, let postfix be postfix, not a 3rd-party service manager here, e.g. grep " smtpd_milters" master.cf -o smtpd_milters=unix:/run/mregex/mregex.sock,unix:/run/clamav-milter/clamav-milter.sock,unix:/run/spamassassin-milter/spamassassin-milter.sock -o smtpd_milters=unix:/run/dkimpy-milter/dkimpy-milter.sock systemctl list-units | egrep "regex|clam|spam|dkim" |grep service clamav-daemon.serviceloaded active running clamd scanner clamav-milter.serviceloaded active running clamav milter dkimpy-milter.serviceloaded active running dkimpy milter mregex.service loaded active running regex milter spamassassin-milter.service loaded active running SA milter spamd.serviceloaded active runningSA daemon works great fwiw, i also run the fastmail auth milter in its SMTP mode in a prior stage, and inject into this^^ milter stage ymmv. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
On 12/03/2023 12:49, David Bürgin via Postfix-users wrote: EML: I can run the milter as a service, if necessary, instead of adding an entry in master.cf, but this feels like the wrong way to do this. Thanks. But note that this is how milters are normally operated, eg milters installed from a distro package. That's a surprise - thanks. I've just checked and seen that opendkim and opendmarc set up init-style services. I'll do a systemd service for this milter, but I'd be interested to hear if there's any policy or other advice about whether we should be using master.cf or a service. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
unfortunately I don't know this topic, but I'm really willing to study. Please do you have any documentation on this? Messaggio originale Oggetto: [pfx] Re: MySQL error from not all the receiver Data: 2023-03-12 13:26 Mittente: Gerald Galster via Postfix-users Destinatario: Postfix users Rispondi a: Gerald Galster I have checked the commands you listed in your first email, but I do not find any errors in the database, table, or MySQL service. Perhaps, as you say, this is not the correct path for the configuration. Currently you are connecting via unix domain sockets. Mysql usually listens to 127.0.0.1 port 3306 (tcp) as well. You could try that but beware that mysql treats connections from unix domain sockets and tcp differently. You might need to allow (grant) host '127.0.0.1' access for mysql postfix user. It may be easier to locate the unix domain socket. You can configure the path via hosts: https://www.postfix.org/mysql_table.5.html I already suggested how you could locate the socket path. I just want to send mail directly from the Postfix server without a relayhost. Then you don't neet smtp_sasl_password_maps. Leave it empty. For testing purposes try to send an email via console/ssh, e.g. using /usr/bin/mailx and watch your maillog. Best regards, Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Integrating a new milter with Postfix
EML: > I can run the milter as a service, if necessary, instead of adding an entry > in master.cf, but this feels like the wrong way to do this. Thanks. But note that this is how milters are normally operated, eg milters installed from a distro package. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Integrating a new milter with Postfix
I've written a before-queue milter that I'm trying to integrate with
Postfix, but there doesn't seem to be any specific documentation on how
to do this. During development, I ran the milter manually, listening on
port 7950, with nothing in master.cf, and this in main.cf:
smtpd_milters = inet:localhost:7950
non_smtpd_milters = $smtpd_milters
This works. For production, I'd like to get Postfix to run the milter,
so I've added this to master.cf:
7950 inet n y n 0 - samilter { -p inet:7950@localhost }
In other words, I want Postfix to run program 'samilter', with arguments
'-p inet:7950@localhost'. This doesn't work, because 'samilter' is
actually run with lots of additional arguments that I don't recognise.
When samilter fails it adds this to the system mail log:
usage error (samilter -n 7950 -t inet -u -o stress= -s 2 -p
inet:7950@localhost)
So Postfix is running it with additional arguments '-n 7950 -t inet -u
-o stress= -s 2'.
Is there a list of additional arguments that I can ignore? Or do I
actually need any of these arguments? I can run the milter as a service,
if necessary, instead of adding an entry in master.cf, but this feels
like the wrong way to do this. Thanks.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: MySQL error from not all the receiver
> I have checked the commands you listed in your first email, but I do not find > any errors in the database, table, or MySQL service. Perhaps, as you say, > this is not the correct path for the configuration. Currently you are connecting via unix domain sockets. Mysql usually listens to 127.0.0.1 port 3306 (tcp) as well. You could try that but beware that mysql treats connections from unix domain sockets and tcp differently. You might need to allow (grant) host '127.0.0.1' access for mysql postfix user. It may be easier to locate the unix domain socket. You can configure the path via hosts: https://www.postfix.org/mysql_table.5.html I already suggested how you could locate the socket path. > I just want to send mail directly from the Postfix server without a relayhost. Then you don't neet smtp_sasl_password_maps. Leave it empty. For testing purposes try to send an email via console/ssh, e.g. using /usr/bin/mailx and watch your maillog. Best regards, Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
> Is it possible to use an object storage system (like aws's S3) to store > message files? if this can be implemented we may have a more persistent > storage for email. AFAIK aws's S3 has three replicas for each file in their > system by default. At that scale emails are usually delivered via lmtp so that postfix does not store messages directly. Dovecot has obox, which may not be availble in community edition. https://doc.dovecot.org/configuration_manual/mail_location/obox/ Best regards Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Fwd: Re: MySQL error from not all the receiver
I have checked the commands you listed in your first email, but I do not find any errors in the database, table, or MySQL service. Perhaps, as you say, this is not the correct path for the configuration. I just want to send mail directly from the Postfix server without a relayhost. What i have to do ? Thanks... Messaggio originale Oggetto: [pfx] Re: MySQL error from not all the receiver Data: 2023-03-11 17:34 Mittente: Gerald Galster via Postfix-users Destinatario: Postfix users Rispondi a: Gerald Galster smtp_sasl_password_maps is configured with a connection parameter to db connection and a simply select query. [...] if i use external smarthost, this mail is always sent regularly. I am also not sure what you want to achieve: https://www.postfix.org/postconf.5.html#smtp_sasl_password_maps ### smtp_sasl_password_maps (default: empty) Optional Postfix SMTP client lookup tables with one username:password entry per sender, remote hostname or next-hop domain. Per-sender lookup is done only when sender-dependent authentication is enabled. If no username:password entry is found, then the Postfix SMTP client will not attempt to authenticate to the remote host. ### smtp_* keys are for outgoing connections, like with your external smarthost. With smtp_sasl_password_maps you can configure credentials that are used when you are submitting emails via an external smarthost that requires smtp authentification. In case you want postfix to send mails directly you don't need smtp_sasl_password_maps. In case you want to authenticate your own users submitting mails via submission (e.g. port 587) you need other means like saslauthd or dovecot. Best regards, Gerald ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
