New answers tagged dovecot
0
First thing that probably you have blocked port 25 for outgoing connection, this is a standard for most home internet, to avoid spam.
Second, you website is hidden using CloudFlare proxy, so you connection is pointing to their servers not you one. To force connect locally add a proper entry into 'hosts' file point to your local ip to this will then work ...
0
You may not have to do anything. Check your first_valid_uid and last_valid_uid settings - it limits which of the users you have configure in your user database are actually valid Dovecot users.
For logging in and mail delivery, these settings work the way you want: You can keep your system users, and keep Dovecot configured for reading the system user ...
1
auth_username_format = %n
breaks virtual domains on the same server, better idea is to use a conditional ( should work since 2.2.33 )
(see: https://doc.dovecot.org/configuration_manual/config_file/config_variables/ )
i'm using:
auth_username_format=%{if;%d;eq;hostname.startdedicated.de;%Ln;%Lu}
which is working fine. However you can use %n instead %Ln and ...
0
In my case helped this
chown -R opendkim:opendkim /etc/opendkim
chmod 0750 /etc/opendkim/keys
chmod 0600 /etc/opendkim/keys/default.private
0
The answer to this was to make mydestination = localhost and therefore avoid $myhostname / $domain being handled locally. It was not an issue as anx suggested to have $myhostname & $domain be equal or for that value to be the main domain name e.g example.domain.
Of course this setup requires virtual_mailbox_domains to include the domain so it can be ...
0
I didn't know what the version was. But I have found out since it is 2016.
If you have the machine at hand, the detailed version information can be viewed via File > Office Account > About OutlooK. Besides, considering that it works in the latest version of outlook for MS 365, I'd suggest checking for and installing all the available updates for ...
2
Find a ID of one of the mails in the queue with mailq
Then check the headers to see how it was sent with postcat -q ID (where ID is the ID of the message). This way you can check wether the email is sent by a authenticated user or a rogue script.
Delete all emails from that user in the queue with:
mailq | tail -n +2 | awk 'BEGIN { RS = "" }
# $7=...
1
Postfix - in the default configuration - assumes that mail destined for the mail server gets handled locally. So if you are receiving mail for mailbox@mydomain.example, and your mail server is called mydomain.example, that gets handled locally. This is how you got the "in local recipient table" error message.
You can see that you are using this ...
1
Enable external in auth_mechanisms, and make sure the client provided username matches the extracted username from the certificate.
It would be even better to override the provided username without the possibility to enter a wrong one (such as in the former situation). A suggestion to fix that would be welcome.
It is extremely frustrating to find this ...
0
This is actually a bug in Dovecot's sieve implementation. There is a workaround for this bug (use the quota plugin), however this workaround doesn't help with aliases.
0
Here is the contents of master.cf
[root@server ~]# cd /etc/postfix/
[root@server postfix]# cat master.cf
Postfix master process configuration file. For details on the format
of the file, see the master(5) manual page (command: "man 5 master").
Do not forget to execute "postfix reload" after editing this file.
=========================...
0
pam_authenticate means it's trying a system user lookup, disable pam lookups by commenting out the include for auth-system.conf.ext in 10-auth.conf.
ps: did you get the LUA working? I am trying something similar.
edit - got mine working by adding these fields into the passdb lookup function return fields (NOT userdb lookup function fields):
return dovecot....
0
Postfix handles SMTP(S) protocol. Technically it is an MTA (Mail Transfer Agent). It moves emails around to recipients mail servers or, if it is the server managing recipient's email address, either directly stores them in recipient's mailbox or passes them to another software (i.e. dovecot) which performs this task.
Softwares like dovecot are MDA (Mail ...
0
For your scenario, you won't install a second email server, instead:
Configure an internal SMTP Relay server (or a Send-only SMTP Server) which will send e-mails
Take a look at this tutorial: Configure Postfix to Send Email Using External SMTP Servers
Configure fetchmail on the internal server to retrieve emails from your external mail server
Configure an ...
0
Thanks for your reply.
I am not sure if you got the idea of what I am trying to do here.
This is the actual task:
"Email servers are configured to block, log and report emails with inappropriate protective markings."
"The intended recipients of any blocked inbound emails, and the sender of any blocked outbound emails, are notified."
Build ...
1
For me problem was newer default value in /etc/postfix/main.cf
compatibility_level = 2
When I changed it to
compatibility_level = 1
It started working.
1
Got it -- Totally misunderstood where to put mail_crypt. Here is what I did:
services:
mailserver:
image: docker.io/mailserver/docker-mailserver:latest
hostname: ${HOSTNAME}
domainname: ${DOMAINNAME}
container_name: ${CONTAINER_NAME}
env_file: mailserver.env
ports:
- "25:25"
- "143:143"
- "...
0
Given that the mua_ options aren't even valid (see man 5 postconf), I think you can just delete those lines. That's what worked for me.
1
For completeness, similar problems also apply with multiple GIDs (possibly resulting in something like "Fatal: setresgid ...: Operation not permitted"):
If you need multiple uids/gids you'll need to set dovecot-lda setuid
root or invoke it through sudo. See LDA#multipleuids for how to do
this securely.
source: https://wiki2.dovecot.org/LDA/...
0
postconf: warning: /etc/postfix/master.cf: undefined parameter:
postfix is warning you that you are using some parameter in one file (in master.cf) that is not defined (in main.cf).
First figure out how that happened, fix that, then deal with any remaining problems.
One way this might have happened would be that you inadvertently truncated the file and that ...
Top 50 recent answers are included
