New answers tagged

0

Check that you have formatted /etc/postfix/sasl/passwd correctly. It should appear as: smtp.gmail.com user@gmail.com:password_or_app_password After setting this file, you need to run postmap on it, to update the hash. postmap /etc/postfix/sasl/passwd Then reload postfix. systemctl reload postfix


0

passwd-file: Unknown setting: username_format For me the reason was extra space: passdb { driver = passwd-file args = scheme=SHA256-CRYPT **extra-space-here**username_format=%u /etc/dovecot/users } i.e. I had two spaces between CRYPT and uesrname.


0

How can i allow the scanner to only send mails through the relay ... Check this --> How to set up an SMTP Relay Server ... only to certain domains Check this --> Is it possible to limit outgoing emails in Postfix to one specific domain?


0

In order to check your alias is working properly you can try to check your MySQL directly first. From your log I don't see any attempt delivering to your mailbox Select goto from alias For alias you should see something like this in your log 29 06:46:59 mail postfix/local[15339]: A8967BF907: to=<yourmailbox@domain.com>, orig_to=<youralias@...


1

Assuming that you have set up SPF, DKIM, rDNS and that you are not blacklisted, your only options is Microsoft Smart Network Data Services. No kidding. That is official MS's program for registering responsible person (administrator) for IP address on which mail server runs. That way you can observe and review status of IP address of your mail server. MS ...


1

Doing an ARIN lookup of your IP, it looks like it's coming from a provider that offers cloud hosting services. It seems pretty standard for Cloud hosting providers to get blacklisted simply because of how often IP addresses can change hands and how easy it is for instances to send Spam. Mail services end up black listing the entire hosting provider's block....


1

The headers you posted don't really look like Hotmail Headers. Can you log into hotmail online not through thunderbird and grab the headers from the actual email. They normally contain all the codes to tell you why it's going to spam. I did check your IP at Symantec and it was clean (sometimes that's the culprit for Hotmail issues). You also might have a ...


0

As the other question states, there are two important parts that need to be added to master.cf under the submission port -o smtpd_client_restrictions=permit_sasl_authenticated,reject This ensures only sasl authenticated people send. -o smtpd_sender_login_maps=hash:/etc/postfix/virtual This is a map to your user DB, change it to be the one you use ...


0

By default, permit_mynetworks is set under smtpd_recipient_restrictions . mynetworks is set to 127.0.0.0/8 and its IPv6 equivalent. This allows unauthenticated mail from localhost. There is likely a rogue process that's just sending mail to localhost. If you remove that option, at least the mails may stop. But you'll still need to find the rogue process. You ...


-1

This is the job of the LDA (local delivery agent). See the complete install example for Ubuntu (13.10 so slightly old): https://github.com/opensolutions/ViMbAdmin/wiki/Mail-System-Install-on-Ubuntu If followed, this absolutely works fully :-D And see the configuration for the LDA: https://gist.github.com/barryo/8918488#file-dovecot-15-lda-conf


0

I don't know postfix-admin nor ViMbAdmin but creating a maildir is as simple as: mkdir -p $USERHOME/Maildir/{new,cur,tmp} chown -R <mail user>,<mail group> $USERHOME/Maildir chmod -R 700 $USERHOME/Maildir where $USERHOME is the mailbox home directory (virtual user home directory). You can write a simple bash script to run every time you ...


1

You can do this using smtpd_restriction_classes in main.cf like this: smtpd_recipient_restrictions = ... check_recipient_access hash:/etc/postfix/recipient_access ... smtpd_restriction_classes = tocustomerx tocustomerx = check_sender_access hash:/etc/postfix/customer_x_sender_access In /etc/postfix/recipient_access put something like this: ...


0

If you want to do that using only Postfix builtin filters, then it can be done only if you can assign different public ip addresses to the postfix server. If so you can follow this example to get what you want: Postfix BUILTIN_FILTER_README Or you could write an external filter, following instructions and examples at Postfix FILTER_README Regards Paolo B....


0

Do you want to just force everyone to append @example.com to their e-mail usernames, or are you looking to actually support virtual mail hosting (where different people may have different domains on their usernames)? If the former, I'd question the utility, but if you're dead-set on it, you could probably tweak some option or another in the dovecot config ...


0

TLS configuration is likely a red-herring. SASL CRAM-MD5 is atypical. Perhaps you want SASL PLAIN or SASL LOGIN. Since you are using dovecot for IMAP you may want to use dovecot's sasl provider for postfix as well. http://www.postfix.org/SASL_README.html#server_dovecot


1

Honest advice, use normal user accounts and let your Linux system authenticate the users. This is easy to manage and very secure. I don't want to say that other systems are insecure but I trust my Linux system when it comes to storing and authenticating passwords. I use these commands to create users manually. This way they can do no harm on my system. ...


3

Consider the client/server relationship with regards to SMTP and the settings make sense: 2.1. Basic Structure The SMTP design can be pictured as: +----------+ +----------+ +------+ | | | | | User |<-->| | SMTP | | +------+ | Client- |Commands/...


1

exim can detect the presence of the A record && absence of the PTR record with ACL and then any action can be performed via routers. $sender_host_name, $host_lookup_failed and $host_lookup_deferred do all the trick. The problem is that spammers are often use such poorly configured but still legal hosts for submission (ISP's dynamically addressed ...


1

if you want all the emails being sent via gmail, you have to set relayhost to smtp.gmail.com:587 as you wrote. This is not enough, though. You need to create and edit the file /etc/postfix/sasl_passwd Write a line in it like below: smtp.gmail.com:587 user@example.com:password where: user@example.com is a valid username in your gmail hosted domain ...


0

I left the idea of using postfix and dovecot and simply installed sendmail to achieve it.


0

I found below link very helpful, it shows step by step guide to disable postfix for external domain delivery. http://www.codeinsects.com/allow-postfix-php-send-email-to-work-with-extenal-mx-record.html


0

Do not use LDA from postfix, use dovecot's deliver instead. Detailed explanation can be found at http://wiki.dovecot.org/LDA/Postfix If implemented, dovecot become the only service that have an access to the storage so there is no permission collision between postfix and dovecot.


0

Based on the information provided and the fact that you do have a valid PTR record, the only thing you seem to be missing is experience. For most lists, having a neutral reputation does not mean much when the volume analyzed is too low to draw conclusions. Sending more and more clean messages to different domains will progressively improve your inbox ...


0

Thanks to @ychaouche I found the solution. The client-side did not accept the certificate. Which means the SSL transmission was not allowed. After restarting client-site mail-application and trusting this untrusted openssl cert everything worked as expected! Thanks!


1

The answers and responses already given contain all the parts of the solution, here's my attempt to tie that info together, having struggled with and now fixed the same problem: Overview: Dovecot only acts upon the service lmtp section if lmtp appears in the protocols setting. Especially if you have a custom dovecot.conf file you may have omitted something. ...


3

When I format the smtpd_sender_restrictions so it becomes a little more readable: smtpd_sender_restrictions = reject_unknown_sender_domain, reject_unauthenticated_sender_login_mismatch, reject_known_sender_login_mismatch, hash:/var/spool/postfix/plesk/blacklists, ...


0

As noted by Sven, email is not a 100% reliable system. That said, there are a couple of things you can do to make sure you're as close to 100% as possible. I would suggest that you put your Postfix config files into a configuration management app such as git, Mercurial, Subversion, etc. This will allow you to identify a known working config and can easily ...


0

The question you might want to ask yourself, is what is the benefit in knowing what script sent the email? Certainly you should be looking to fix your security, but the exploit is not the same thing as the vulnerability - there are multiple things an attacker might do with your system, not just sending email. So really your focus should be on fixing the ...


0

Did you check web log? Try to look process with ps to identify process which sending spam. Maybe you can catch it there. Second, maybe spammer periodically send by crontab, check every crontab in your system to identified the bogus script. Сheck one of the email with postcat to see which script tries to send them: postcat /var/spool/postfix/deferred/1/{$...


1

You write: my domain points to my server as I'm already hosting the website. This is wrong, and it is one of your two problems. The name www.one3community.com points to 104.27.163.48, so far so good. Mail, however, is sent to the MX record of the domain, and failing that it is sent to the IP address of the domain. There is at the time of writing no MX ...


0

From what I see it looks like Spamhouse has answered differently second time. I.e. first answer was "there is a spammer", but 8 minutes later answer was "there is nothing special". Why it was answered it is hard do say. If you have access do DNS server query logs which is set to resolve your mail server's dns queries, you might find some clues there. For ...


0

If you like to block the IP of the sending client, than you will have to set up the RBLs in ... smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net, reject_rbl_client cbl.abuseat.org, permit ...


0

Okay, I think this finally has it fixed. My master.cf now has: smtp inet n - n - - smtpd -o content_filter=smtp-amavis:[127.0.0.1]:10024 -o smtpd_sasl_auth_enable=no submission inet n - n - - smtpd -o smtpd_tls_security_level=encrypt -o tls_preempt_cipherlist=yes smtp unix - ...


0

I think the problem is that you're selecting your endpoint from mailbox, not from the virtual users table, so postfix knows where it should go, but not dovecot. Change : SELECT username as user, password, '/var/mail/%d/%n' as userdb_home, 'maildir:/var/mail/%d/%n' as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%...


-1

Tried the above and not working I tried the following, but only the last content_filter was executed.. smtp inet n - n - - smtpd -v -o content_filter=autoresponder:dummy -o content_filter=dfilt: -o receive_override_options=no_address_mappings


0

Your configuration isn't optimal, better use RBLs in the client restrictions. Here's what I would suggest, though some is a bit restrictive and I don't know your complete setup of Postfix. This is an example, see Postfix manual and advices for more information about the params … smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated,...


0

With that configuration your MTA is accepting mails from a wide network range: mynetworks = 127.0.0.0/8,123.123.0.0/16 smtpd_client_restrictions = permit_mynetworks … That means if any of these 65,024 hosts in the network 123.123.0.0/16 is compromised, it can send spam via your machine with no restrictions. You should only allow the host IP addresses for ...


1

Since many years postgrey is a very good solution for me in the fight against spam/malware. It reduces the traffic load in SA/ClamAV up to 90% with almost no false positives. A good similar solution is policyd/cluebringer with a frontend for an easy configuration handling via web browser. With cbpolicyd you can also handle a throttle for outgoing mails in ...


2

This address is part of a network served by a provider in Poland: http://www.tcpiputils.com/browse/ip-address/155.133.82.96 I have also often scans against my MTA coming from that network, mostly/only for SASL login break attempts. What I recommend to keep that stuff away: A solution with Postfix only is not possible as far as I know. But you could use i. ...


0

I think you may want to modify your sql select statement to be sql_select: SELECT password FROM mailbox WHERE username='%u@%r' AND active ='1' as that should select both the user and domain..


0

Emails started going out as soon as I replaced postfix with sendmail. Additional configuration may be appropriate, but my site has passed the smoke test.


0

If the file just contains one line with the text "# Generated by resolvconf" it is most likely a problem with boot order. First check if "/etc/resolv.conf" contains the nameserver. If this is the case your network is correctly configured and up. Even on modern distributions with systemd postfix is currently still booted up by init.d scripts that are ...


0

I think the issue is because mx record is not configured from virtual server. Need to make sure the following thing is done. 1) Webmin -> Servers -> Postfix Mail Server -> General Options -> What domain to use in outbound mail (Use hostname) 2) Webmin -> Servers -> Postfix Mail Server -> General Options -> What domains to receive mail for (Local machine) ...


1

Change the value in the Gecos in /etc/passwd by setting it to "mydomain". By system command, run chfn -f "mydomain" root


1

You need to add following in virtual /etc/postfix/virtual postmaster@domain.com boss@domain.com editor@domain.bg novini@domain.bg, editor@domain.bg, boss@domain.bg, user@webmail.com novini@domain.bg novini@domain.bg, editor@domain.bg, boss@domain.bg, user@webmail.com postfix is smart, so it does not "loop".


2

The problem is postfix use header_checks for every header line. So if there is header line like Subject: I love you :p and postfix will apply that regex into this line. The result is postfix will reject this email. The solution is adding if endif in your regex pattern if /^From:/ !/(^From:.*domain\.com|^From:.*domain\.net|^From:.*domain\.co\.il)/ REJECT ...


2

Generally, all configuration parameters defined for postfix (see man 5 postconf) should be placed in one and only one file, $etcdir/postfix/main.cf. So postfix doesn't have some kind of Include this file/directory in its configuration syntax like other software such as apache httpd, sudo and the others. Fortunately, you can always use external source for ...


1

There two common methods to use postfix SASL with MySQL: Using saslauthd service combined with pam_mysql Using sasl auxprop with sql plugin Unfortunately, the second method has serious security drawback: you must store the password in plaintext format. So, in your case you need to use saslauthd and pam_mysql. In your config above, you mixed these two ...


2

What's the hostname of the server where this script is on, and what's the hostname of your mail server (if different)? If they fall under the same domain but they are in fact 2 different servers, then it's likely Postfix "thinks" email sent to the domain name should be delivered locally - and so ignores MX records and does just that. This would explain why ...



Top 50 recent answers are included