Tag Info

Hot answers tagged

5

Mails are coming from the following mail addresses. biryukova@dak-cat-stroitelnye-materialy-kirpich-kamen-bloki viktor.golubev@consulfrance-stanbul.org adelaida.egorova@mail.starce.net akim.makarov@quake.com.ua ilarion.korolev@judwin.demon.co.uk & Mails are being delivered to the following addresses ...


4

The problem is that you are not authenticating via SASL. You have this set on submission: -o smtpd_client_restrictions=permit_mynetworks,permit_sasl_authenticated,reject The first allows mynetworks (which seems to be only localhost), the second allows ony authenticated users. Your log shows you establishing an anonymous TLS connection, but no SASL auth. ...


4

I would suggest that you to remove all the virtual_mailbox_* parameter and use only transport_maps and relay_domains. Set up a "dovecot:" transport in master.cf which delivers your mails via the dovecot LDA or the dovecot LMTP. E.g.: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail ...


4

Never shutdown the old server until you know that the TTL of the MX record pointing to the old server has expired. If the TTL is/was 1 week then leave the old server running for 1 week to catch any emails from clients that may have that MX record cached. When implementing an email cutover always check the MX record during your planning phase and adjust it ...


3

Port 465 is for SMTPS, it uses SSL immediately when establishing the connection and then uses the same SMTP protocol as normally found on port 25 after the secure connection is established. You test from the commandline with: openssl s_client -connect smtp.example.com:465 Using telnet to connect to port 465 will result in an error message in the log ...


3

Looks like, your virtual_alias_maps and virtual_mailbox_domains was swapped. Try to rename them mv /etc/postfix/virtual_alias_maps.cf /tmp/virtual_mailbox_domains.tmp mv /etc/postfix/virtual_mailbox_domains.cf /etc/postfix/virtual_alias_maps.cf mv /tmp/virtual_mailbox_domains.tmp /etc/postfix/virtual_mailbox_domains.cf Don't forget to run postfix reload. ...


3

First of all, if you can, use a mass mailing service. There are plenty of them out there with various features and prices. Most don't cost very much. They will deal with things like managing people unsubscribing from lists, ensuring you are compliant with various anti spam legislation around the world, getting their servers off of blacklists, and give you ...


2

Your scenario is most plausible. Remember that DNS does not "propagate"; rather, records are cached by other DNS servers for the duration of the TTL. So some sites may be caching that old record for as long as a week. (And broken DNS servers may cache it even longer, but those are fortunately few and far between.)


2

Empty from(sender) address usually means that your server is sending MAILER-DAEMON messages such as: "Undelivered Mail Returned to Sender" sometimes it may be backscatter. Nov 17 09:47:18 localhost postfix/qmgr[21748]: C16D772BB5: from=<ilarion.korolev@judwin.demon.co.uk>, size=34250, nrcpt=1 (queue active) Nov 17 09:47:19 localhost ...


2

To answer your questions: Normally you should not encounter limitations on a dedicated server, but this is dependent to the provider from which you buy the server. You should see their terms of service and contact support prior to purchase. For safety you should consider having at least Raid1 as storage configuration (size of HDD depends on your knowledge ...


2

As NickW said, your configuration only allow you to send mail anonymously from host in mynetworks and authenticated from other locations. So you have two solutions : enabling SASL authentication adding your public IP to Postfix mynetworks parameter to allow you sending mail without being authenticated (I don't recommend this solution if you send mails ...


2

Your configuration looks correct and i have checked your Forward and Reverse entries. That look ok. The problem is that you don't know which SPAM-System and RBL the recipient use. So its possible that they use a special RBL-List and you are blocked on that list for example. There are a lot of possibilities but i think your configuration is ok. Perhaps ...


2

As far as I know the support for subject alternative names is primarily a client side issue. There the SAN entries have to be checked when the request hostname doesn't match the Common Name in the certificate. Sendmail simply loads and presents the certificate and doesn't even need to interpret the SAN entries encoded in there, I think. But even if some ...


2

You have two distinct errors in your configuration: The MX record should be for your domain, not for a subdomain. An MX record should not point to a CNAME. Point it to a record with an IP address. An example of a working domain:


1

The receiving mail servers just want to see a valid PTR record when they query. It doesn't have to match the domain in the email. For example: Let's say you host emails for domain1.com and domain2.com at 1.1.1.1 When the receiving server does a query on 1.1.1.1, they just want to see a domain come back. It doesn't matter if it is domain1.com, ...


1

The PTR reverse record is supposed to point to the canonical hostname of the server, it's not directly tied to any email addresses. Ie, the PTR record should probably point to something like zeus.example.com. This has no actual implication regarding which domains the server is expected to deliver mail for, it's just a sign of a correctly set up ...


1

If /var/qmail/control/notlshosts/host.dom.ain is present, no TLS is tried on this host. add a file with the name of the domain you're sending to to /var/qmail/control/notlshosts/ to disable TLS only for that domain. (if notlshosts does not exists): mkdir /var/qmail/control/notlshosts then, create file: touch ...


1

It dynamically links to the version of openssl you have installed # ldd `which sendmail` | grep ssl libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f1ffec11000) libssl3.so => /usr/lib64/libssl3.so (0x00007f1ffdab5000) If you were to say install a source version over the rpm version and it didn't install those two libraries sendmail would not work ...


1

You can decide which and generally it's better to do for your sender domain as test.org. But it's possible for mailers domain as well. It can depend on which is technically possible. The receiving part going to check sender reputation depending on which domain you choose. So your sender reputation management going to be different. Otherwise the DKIM signing ...


1

I'm sure Dovecot is the one that creates the auth file, as postfix talks to dovecot and dovecot does the authentication so in your 'dovecot.conf' add: path = /var/run/dovecot/auth-client into the client block like so: service auth { unix_listener auth-client { path = /var/run/dovecot/auth-client group = postfix mode = 0660 ...



Only top voted, non community-wiki answers of a minimum length are eligible