New answers tagged

0

postfix/smtp[27379]: cannot load Certificate Authority data: disabling TLS support postfix/smtp[27379]: warning: TLS library problem: error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen('/etc/postfix/cacert.pem','r'): Install certificates of Certification Authorities - they certify other certificates => install package ...


0

Could you please show us the telnet commands used to produce this issue? so that we can reproduce it and fix it. By the way, iRedMail team offers very active support on the online support forum: http://www.iredmail.org/forum/ it's better to ask for support in the forum.


1

https://grox.net/doc/postfix/html/faq.html#paranoid warning: xxx.xxx.xxx.xxx: address not listed for hostname yyy.yyy.yyy Postfix uses hostnames in its junk mail and mail relay controls. This means that in theory someone could be motivated to set up bogus DNS information, in order to get past your junk mail or mail relay controls. When Postfix ...


0

Please ensure that the SMTP port (TCP 25) is not blocked, either by your hosting provider or by the ISP/network operator from which you run your remote nmap check.


1

You may use formail program to feed "one by one" messages in mailbox-file to program/script of your choice. Below please find elaborate example of using formail -s ... to process user system mailboxfile. It is provided in man procmail and makes procmail process every message in the system mailbox. #!/bin/sh ORGMAIL=/var/mail/$LOGNAME if cd $HOME ...


1

To set the MySQL password you need to do the following for your script: ADMIN_PASS=YourPassword #MySql settings echo "mysql-server-5.6 mysql-server/root_password password $ADMIN_PASS" \ | debconf-set-selections echo "mysql-server-5.6 mysql-server/root_password_again password $ADMIN_PASS" \ | debconf-set-selections Just change the numbers for the ...


1

You have a really strange setup telnet mail.abcgreenbrier.org 25 Trying 63.142.252.80... Connected to mail.abcgreenbrier.org. Escape character is '^]'. 220 mn-vps-01.cbcmcalester.com ESMTP Postfix (Ubuntu) helo localhost 250 mn-vps-01.cbcmcalester.com mail from:<> 250 2.1.0 Ok rcpt to:<test@abcgreenbrier.org> 450 4.2.0 ...


1

The email to AOL and the EMAIL to Port 25 - The DKIM signing process is different. When you send to AOL you're signing it with c=relaxed/simple when you send it to port 25 it's c=relaxed/relaxed. You're not really comparing apples to apples. With that being said, many DKIM validators have trouble with Simple conancalization, stick with relaxed. If you ...


0

I've found the error. I didn't configure Dovecot properly. This is the tutorial i used: https://www.crahl.ca/blog/postfixdovecotpostfixadmin-on-ubuntu-14-04/


0

Looks like the configuration works, but my ISP is blocking port 25. Best part of it is that they can't seem to do anything about it since they are reselling a cable trunk.


1

You need to add a MX record to your DNS settings. Let's say your mailserver has IP 1.2.3.4, you'd need to add in your my.doomain.zone file: domain.com. MX 10 mail.domain.com. mail A 1.2.3.4


1

Use pflogsumm to extract delivery statistics. Be careful, the stats may be wrong (double) if you use after queue filters. Using grep to look for delivered messages is not really practical because more than on line is logged for each message. These log lines differ for each type of delivery e.g. the message was sent from a local account, the message was ...


0

check your /etc/postfix/master.cf file, should contain something like: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient}


1

You can pipe the log over some scripts to filter out stuff. Check the following link for an example http://adminlogs.info/2012/07/22/how-to-get-mail-statistics-from-your-postfix-mail-logs/


1

So your antispam routines are using localhost, and bad people are using localhost and postfix cant tell the difference. Ban bad people or remove localhost from trusted network (permit_mynetworks) and configure your antispam to use something else. Or allow your antispam with smtpd_client_restrictions check_ccert_access. Back to your question. You are asking ...


0

One option would be to use iptables to prevent those users from being able to connect to localhost on port 25. For example: iptables -A OUTPUT -p tcp -d 127.0.0.1 --dport 25 -m owner --uid-owner user1 -j REJECT iptables -A OUTPUT -p tcp -d 127.0.0.1 --dport 25 -m owner --uid-owner user2 -j REJECT [etc]


0

I had the same "subsystem public/cleanup: Connection refused" problem but when I looked at the /etc/postfix/master.cf file, the mentioned line was already there. So in my case the solution was to simply restart postfix: service postfix restart After that, I received all the emails that weren't sent before...and that was a lot.


2

Hbruijn response seems to be correct, bsically, whenever any user in the machine (root or other) has a cript running in brtch mode without a window where toi address standard output messages, such a messages are addressed to @ address and, even, addressed to root, meanng "Warning: you have some process writing message you cannot red, so take care of email".


2

As you can see, once you group those log entries by internal message ID, those are email messages that stay within your server: u3OHZ16M030895: from=root ... u3OHZ16M030895: to=root ... (u3OHZ1UJ030896 Message accepted for delivery) and u3OHZ1UJ030896: from=<root@ip-1xx-xx-xx-1xx.secureserver.net> ... u3OHZ1UJ030896: ...


0

enable_original_recipient=no I put that in my main.cf and it worked fine but only for mail sent from my domain. I still have duplicates if I send email from outside my domain (yahoo to my domain for eg.) source : http://article.gmane.org/gmane.mail.postfix.user/119783


0

For the above setup to work, the Dovecot dovecot.conf should contain: mail_location=maildir:~ without the /Maildir


0

So configuring postfix as a gateway/firewall as described at http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall did the trick. I can send mail directly through mail2, and incoming mail at mail2 is relayed to mail. MX records are needed as mail servers very often check if it exists for spam policy reasons.


1

You have several locally generated and delivered messages, which you should read, and which (if you don't really want to read them on this server) you should forward somewhere. Once you know what the messages are, you can then take any appropriate action. Most likely these messages are being generated or processed by a process which still thinks the old ...


0

A mail exchange is a router, there is no need to reinvent the wheel. Use a single mail router and configure the applications to use it, you don't need to install a new mail server for every appliance, this would be like installing a new domain controller because you application needs users


0

You're looking for relayhost parameter in the main.cf file: Relayhost documentation Add on the server C to the /etc/postfix/main.cf this line: relayhost = IP.address.of.A Then you have to restart postfix service.


3

smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1,!TLSv1.1 smtpd_tls_protocols = !SSLv2,!SSLv3,!TLSv1,!TLSv1.1 ... tls_medium_cipherlist = AES128+EECDH:AES128+EDH You have overly restrictive settings by restricting the protocol to TLS 1.2 only. A major part of the mail servers uses some kind of UNIX with OpenSSL as the TLS library. Support for TLS 1.2 ...


1

You have configurered Postfix to use strong crypto with the recommended TLS security settings such as found on https://cipherli.st/ By only accepting two strong ciphers with the security settings smtpd_tls_mandatory_ciphers = medium and tls_medium_cipherlist = AES128+EECDH:AES128+EDH and only allowing TLS 1.2 you have traded off security over ...


0

From http://en.redinskala.com/postfix-maillog-interpretation/ : General syntax of maillog The following line represents the basic format in which information is logged into maillog: Jan 2 11:15:39 tmcent01 postfix/smtpd[17397]: connect from unknown[127.0.0.1] As you can see, the first section (in bold) indicates only the date and time in which the event ...


0

As Alex pointed out in his comment, the issue was indeed the aliases. My aliases table was empty and weirdly it was resolving to the number '1' so i disabled in my postfix main.cf alias maps (sql) and that did it ! Thanks to Alex !


1

You can have more than one entry in your virtual_alias_maps. They can even be of different types. Specify zero or more "type:name" lookup tables, separated by whitespace or comma. Tables will be searched in the specified order until a match is found. Note: these lookups are recursive.


1

Apr 17 19:46:18 v22015072919626549 postfix/virtual[8844]: 62D6A3E0DC9: to=<***>, relay=virtual, delay=0.05, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) So Postfix is delivering the mail somewhere, but we don't yet know where. I am can not receive mails. Sending emails works perfect. So are you sure Postfix delivers ...


21

Short answer: it will work, technically, but you will have lots of undeliverable mail. Long answer: Take your SMTP logs. Sed out all the domain names you send mail to. Check if they have IPv6 DNS and MX. Once you get 100% (you won't, not anytime this decade), then you can try if the IPv6 IPs actually work. I don't have any interesting production logs at ...


20

The answer depends on your success criteria. But most likely will be no. If you are running a business where any undelivered mail means a measurable cost. Then the answer is no, IPv6-only is not viable yet. There are many providers including some large providers who are still running IPv4-only. The largest provider I know of with dual stack support is ...


0

Have you tried telnetting directly to your server on port 25 from another box? One of the most common mistakes is to have iptables block incoming tcp/25. If this gets rejected, you just need to allow incoming tcp/25 through iptables.


1

You have to use virtual mailbox. This is done normally with a database. In database are stored virtual accounts with directory specified where e-mail should be stored. Then IMAP/POP3 server (Dovecot) can provide access to e-mails stored on server. For more information try searching for: "dovecot postfix virtual mailbox" For example read this: ...


1

Use canonical to rewrite sender adresses as for example: Within /etc/postfix/main.cf: canonical_maps = hash:/etc/postfix/canonical Within /etc/postfix/canonical: user1 user1@site1.com user2 user2@site2.com Then run: postmap canonical postfix check postfix reload


2

Try "maillogconvert.pl" (perl script), which is included in the AWStats (http://www.awstats.org/).


0

I have created a Perl script: https://github.com/brablc/postfix-tools/blob/master/pflogrep You can use is as grep: pflogrep infractor@example.com /var/log/maillog Or you can feed the output to pflogsumm and get nice statistics: pflogrep infractor@example.com /var/log/maillog | pflogsumm


0

This is just a mail routing question if I understand correctly, the domain mail exchange records and their priority won't really help here - since the news letter is routing mail from a dedicated host simply configure it's mail server to be mail2 - there is no need to make an MX record for it unless it's going to be the backup mail exchange for your domain, ...


0

Are you perhaps running into the limit that AWS puts upon sending emails? (As noted in http://stackoverflow.com/questions/26311747/aws-ec2-email-sending-limit-when-using-third-party-smtp-server). You might want to consider using their Simple Email Service.


0

You need a valid SSL certificate and private key setup for your Postfix server, with lines in your main.cfg file like smtpd_tls_cert_file=/etc/pki/tls/certname.crt smtpd_tls_key_file=/etc/pki/tls/certname.key smtpd_tls_CAfile=/etc/pki/tls/ca.bundle smtpd_tls_protocols=SSLv3, TLSv1, !SSLv2 smtp_tls_protocols=SSLv3, TLSv1, !SSLv2 ...


0

In Postfix 2.6 or later, I guess you can return the keyword DUNNO, which is documented in sender_dependent_relayhost_maps topic. no-relay@mydomain.com DUNNO @mydomain.com ses.amazon.com If it doesn't work and you use Postfix 2.7 or newer, I suggest you to substitute sender_dependent_relayhost_maps for sender_dependent_default_transport_maps. ...


0

You can try this PCRE table: /^([^@]+@example\.com)$/ $1 /.+@.+/ email@example.com In this scenario, if Postfix queries me@example.com, the first entry matches and me@example.com (the captured string) is returned. Or else, the second entry matches and email@example.com is always returned.


0

At a minimum you need the SMTP (25) port open in both directions. You should have the Submission (587) port open for incoming traffic, if you want mobile clients to be able to send email. For your clients to pick up mail you need either IMAP (143) or IMAPS (993) open for incoming traffic, although it would be better to have both open as sometimes one or the ...


0

Not quite, you need some more research, but you're on the right track :-) To begin with, you can secure any of the ports you mentioned as non "secure" by negotiating STARTTLS instead of protocol-over-SSL. Your 465 should only have been in SMTP, not IMAP, and you should forget about it in any case. POP is OK when mail is just passing through to one device. ...


1

if emails are being sent by legitimate user/accounts, some of them might have fallen victims of malware that is using their email clients to send these messages, do you have any way to know their current OS/mail client? Logs may help you with that if you are not using SSL/TLS for your IMAP connections, IMAP credentials might have been captured through many ...


1

most likely you are open relay mail server, you can check here http://mxtoolbox.com/diagnostic.aspx open relay means that anyone can use you mail exchange unchallenged. you will need to look at the documentation around securing you mail server.


0

Your Postfix installation is undoubtedly configured to send and receive e-mail for local users only. In order to receive messages from the Internet, Postfix must be able to receive connections on ports 25/tcp (SMTP) and 465/tcp (SMTP over SSL). I'm not sure if GMail initially tries to establish a secure SMTP connection (465/tcp), but GMail certainly uses the ...


0

It should be in the mail queue Send a simple email # echo "Hello world" | swaks -4 --server smtp.example.net --from alex.hha@gmail.com --to sf-768072@example.net --h-Subject "Test message" --body - === Trying smtp.example.net:25... === Connected to smtp.example.net. <- 220 smtp.example.net ESMTP Postfix -> EHLO tl-resin-node1.example.net <- ...


0

I think I solved: smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/restricted_senders, reject smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, ...



Top 50 recent answers are included