Tag Info

New answers tagged

3

check out your /etc/aliases folder. there is a long list of aliases that all go to root.


1

I tried this answer that addresses this very problem. But messages don't seem to be easily modifiable in the version I have (2.11.0). For instance there is no /var/spool/mqueue dir, but, instead, /var/spool/postfix/... I want to clarify two things. First, that answer was applied to sendmail NOT postfix. Second, direct-manipulating-raw-queue-files ...


1

Your mailserver isn't accepting connections on port 25: [jenny@sameen ~]$ telnet mail.simendsjo.me 25 Trying 151.236.221.202... telnet: connect to address 151.236.221.202: Connection refused telnet: Unable to connect to remote host


3

Is there a reliable way to reject incoming mails with a spoofed e-mail address? Over the years, there are some techniques implemented to identify spoofed email address, for example: SPF, Sender ID, DKIM, and DMARC. Take a look on these two excellent answers about email spoofing on security.stackexchange, here and here. What kind of checks does ...


0

You can't determine the culprit process through the Message-ID as it can be forged (and probalby is). The only way ist to replace the sendmail program with a wrapper shell script. This script can then be used to log everything you need. Like parent process ID, user and other process information. The pickup program of Postfix is triggered by the sendmail ...


0

You should not disable a user at the Postfix level. You'd better add a flag in the LDAP like "disableMail". Then query this flag through your ldap_mailbox_maps.cf for filtering out all users with that flag.


0

[SOLVED] It seems this entry only in /etc/postfix/main.cf applies to Ubuntu/Debian systems. virtual_transport = lmtp:unix:private/dovecot-lmtp change in virtual_transport = dovecot


1

If you're sending almost identical mails to more than 1 recipient, the single 2 most important headers to have, when dealing with GMail are: Precedence: bulk And List-Unsubscribe: http://your-site.com/unsubscribe.php?email=thisguy@gmail.com of course pointing to a real and working unsubscribe page, where google's unsubscribe bot can easily get to click ...


2

[SOLVED] This fixed the issue for me in Ubuntu 14.04: sudo apt-get install postfix-mysql


1

I have seen this to happen in other ocasions, when the received from is reported as localhost, with 127.0.0.1 as IP address. The fact that this does not match with your DNS records is certainly getting your email marked as spam. You should review your DNS records (A and MX) and the headers that you send in your SMTP server. Your server is sending what it ...


0

I've seen this before on systems running enforced SELinux.. Check using $ sestatus to see if SELinux is enabled and enfored. Then disable it and see if that helped.


0

In addition: Postfix states that adding import_environment = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY DISPLAY LANG=C RESOLV_MULTI=on to your /etc/postfix/main.cf solves this too. It worked for me only this way.


2

You can use the folder option. Just put it in the fetchmail config file (Default is .fetchmailrc). poll mail.server.com protocol IMAP user 'xxx@xxx,com' password 'xxxxxx' folder 'mailinglist' See man page or search for "fetchmail folder option" if you need more examples.


1

Are you using traditional the mbox format? You should consider converting all mailboxes to Maildir format to avoid such locking errors (and much better performance). The logs for Dovecot don't seem particularly troublesome, they just indicate an user was disconnected due to inactivity, which is OK.


0

Can you use IMAP instead of POP3? POP3 is designed for single-user use. It's from the times when you exclusively used a single computer for everything and when the mailboxes offered by ISPs were very small. Back then we did fetch all the e-mails from the server to a personal computer. Due that most POP3 clients/servers do lock the mailbox when they are ...


2

That's means that postfix have try to deliver four messages to the user's mailbox at the same time. As far as you have used mbox as mailbox format, each delivery should be performed as sequence of operations. Message should be stored, indices should be updated and so on. To prevent simultaneous deliveries that can broke mbox structures, each delivery first ...


1

Of course the GMX server blocks your requests because they are not an open relay. It's not 1995 anymore (sadly, as far as SMTP is concerned). You have three possible approaches: Deliver mail directly, without an relay (this has a lot of requirements to work reliable). Authenticate with your GMX account to identify yourself. It might still be that ...


1

I don't believe it's necessary to add aliases from your virtual mailboxes to themselves, and in fact this might be preventing mailbox lookup. Also, since you're using hash: to specify the virtual mailboxes (and domains), you need to use postalias or postmap to create the hashmap versions of the files (the files actually used end in .db in this case and are ...


0

I found an answer to my own question. The problem was that the domain name was in mydestination, which made the emails sent through the domain to go through local_recipients_maps. Removing the domain solved the problem. I don't know if that's the best practice or overriding local_recipients_maps to use mysql is. If anyone has an answer to that please write ...


3

I know this is not really answering your question, but: Don't. Use your mail client with STARTTLS instead, which, as you say, works fine with your server. It is not a good idea to send credentials over an unencrypted connection. You don't state the reason why you want to do unencrypted SMTP authentication at all, so I can only guess — if you have a mail ...


-1

The point of my question (maybe I haven't stated it clearly enough) has been: how to combine Postfix and Spamassassin on CentOS with minimal efforts. Here is my solution in only 5 steps: yum install spamassassin chkconfig spamassassin on useradd spam (you can't omit this step!) Add /^Subject: \[SPAM\]/ DISCARD to /etc/postfix/header_checks (consult ...


0

Ok, so basically, you are piping the email into spamc, and then having spamc email the output to the recipient (well,actually remailing to the sender, but I think the intent was to remail to the recip).. No offense, but that is nuts. If you want mail to be rejected based on the SA score, you're going to need a milter or policy deamon to do that. ...


2

You can configure specific ip-adresses to use your postfix or sendmail installation as an outgoing SMTP server or relay host without SMTP authentication, which is much better idea. In sendmail that is configured with the access map, typically /etc/mail/access: Connect:127.0.0.1 RELAY Connect:10.9.8.7 RELAY Connect:192.168.1 RELAY ...


3

Don't open postfix for everyone. You can allow relay access to one address (or network) with the following line in your main.cf mynetworks = 127.0.0.0/8, xxx.xxx.xxx.xxx/yy xxx.xxx.xxx.xxx => the address you want to permit yy => the netmask of your host (or network)


3

Holy Cow... No offence meant but the ONLY suitable solution for this is finding an IT-service-provider to help you out there because as you said, you are no mail expert and your server really seems to be compromised. As a start you should disable the root password from SSH (root shouldn't be allowed to log in via SSH by password). I don't know the exact ...


1

If you have access to the mail storage at file system level, you could just move the files over to the other inbox with mv. works best with maildir as storage layout/system.


1

If you are prepared to go to the trouble of setting up ALPINE as a mail client, to talk to your existing dovecot IMAP server and postfix SMTP server, you can perform mail redelivery by selecting the email then using the B command ("Bounce"; I don't know why they call it that). You will be asked for the address to which you wish to bounce the message; enter ...


0

You are trying you relay email to gmail but your configuration does not accept relaying mails to gmail so it returns 554 reject code. in postconf relay_domains_reject_code (default: 554) The numerical Postfix SMTP server response code when a client request is rejected by the reject_unauth_destination recipient restriction. to fix relaying ...


0

Yes, you could use sa_username_maps to split it up.


0

What about this? smtpd_recipient_restrictions = permit_sasl_authenticated, reject Not tested, but should work AFAIK. You should get the REJECT error after sending the receiving address.


0

After playing with the demo for about five seconds, I found the menu point "Settings -> Identities". Add another identity with the required mail address and select it for sending.


0

Check your php mail() sent emails for Proper SMTP From aka Envelope From headers. If they don't have something like sender@mysubdomain.domain.tld as SMTP From address, opendkim won't sign them as you have Domain mysubdomain.domain.tld in your /etc/opendkim file.


1

Check /etc/dovecot/conf.d/10-master.conf for line unix_listener private/auth change it to unix_listener /var/spool/postfix/private/auth Restart dovecot and try again. If still doesn't work, post output of dovecot -n and postfix -n


0

You could set an additional header via Postfix: create a /etc/postfix/appendheader.regexp: /(.+)/ PREPEND X-Original-To: $1 in /etc/postfix/main.cf: smtpd_data_restrictions = pcre:/etc/postfix/append_header.regexp This will add an X-Original-To:-header with the original mail address before it's getting rewritten. Have your PHP-Script parse this header ...


1

Since the sole difference here is the domain, focus on that: It is newly registered, and has not had time to build up a good reputation. It is newly registered, and that in and of itself is often an indicator of spam. Spammers often register domains with stolen credit cards, start spamming immediately, and then several days later the domain gets canceled ...


0

Every user gets a different dose of Spam. Since you are using Spamassassin you might want consider adding some additional rule repositories, which are being updated frequently, to catch more spam (e.g. like being described here: http://khopis.com/wiki/Anti-spam). Your spam trigger level is also a little bit high, most people use there 5.0 normally instead. ...


0

In short - you can't. Dovecot allow only global and per-user sieves. before/default/after sieves are global and applied to each message. If you are sure that you want to process all messages in the same way you have to set up the sieve_before filter, not the default. But there is a not well explained trap here. sieve_before may consist of number of ...


2

Required additional package cyrus-sasl-plain.


0

I'm posting this as answer as like to keep the monospace formatting with the comments, this is my current setup for my domain. # === Incoming mail restriction ================================================ #smtpd_client_restrictions = # check_client_access hash:/etc/postfix/access smtpd_recipient_restrictions = # ...


0

After another whole day of reading documentation and tampering with settings, I was finally able to resolve the issue. The problem was in mysql_virtual_domains_maps.cf, which had a MySQL query that did not take an argument, and therefore always returned the same result (the list of all available domains). The correct situation is when the query only returns ...


-2

Try setting milter_protocol=2 in postfix/main.cf.


0

On debian, the default Domain that is used it non is given is specified by /etc/mailname. AFAIK this is a Debian specific modification to postfix. So it should be solved by filling /etc/mailname with mydomain.com. And myorigin in postfix defaults to /etc/mailname on debian, which also should be used in my opinion (so jsut delete this line).


-2

I finally managed to make it work. I had to make some changes to the postfix configuration file located at /etc/postfix/main.cf Here is the complete working configuration file and install steps that allows hMailServer use postfix at another machine as an SMTP relayer: I used the minimal version of Ubuntu server 14.04. It runs fine on 2GB hard disk, 64MB ...


0

Sometimes I can be really stupid (or just tired). The error was clear all the time: Sender rejected: Access Denied Yet I was changing the settings for: smtpd_recipient_restrictions Now that I have see the problem I changed the line: smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject To: smtpd_sender_restrictions = ...


1

It sounds like you've installed it correctly, but your verification step is incorrect. OpenSSL doesn't know where to look to find root certificates unless you explicitly tell it. Try openssl s_client -connect mail.example.com:25 -starttls smtp -CApath /etc/ssl/certs instead. That should work.


2

If you're looking to remove/replace specific lines, or parts of lines, it's often better to try and be as specific as possible. In your case you'll want to try and more closely match the text after from and the server name and ip. Something like this should do a better job: ([a-z]{2,25} \(.*\[.*\]\))


0

Are you using a smart relay? There's a parameter for main.cf, called default_destination_concurrency_limit = 10 If you are using a smart relay, that just might do the job. The other option is to set this in the master.cf: smtp unix - - n - 10 smtp Since every smtp process delivers one email, this limits the ...


0

Yes, there are good reasons why Debian does not use uid 8 and gid 8 for Postfix. You could install other binaries, which use those groups and this could theoretically result in security problems, especially if they run suid mail. Postfix should use its own gid and uid for security reasons, period.


2

Since you've already configured Dovecot, the easiest solution to your problem is to use deliver from Dovecot as the mail delivery agent (MDA). This could be done by adding this line to main.cf (paths may vary according to your distribution, on Debian it's /usr/lib/dovecot/dovecot-lda): mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a ...


4

Assuming that's your real domain (for which, many thanks), you have a problem with your MX record: [me@lory ~]$ dig mx fish-thecompany.com [...] ;; ANSWER SECTION: fish-thecompany.com. 86313 IN MX 20 mail.fish-thecompany.com. [me@lory ~]$ dig mail.fish-thecompany.com [...] ;; ANSWER SECTION: mail.fish-thecompany.com. 86300 IN CNAME ...



Top 50 recent answers are included