Tag Info

New answers tagged

0

I could fix by adding the following in postfix master.conf.. smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination Relay access denied is not only for php mail..its for any client outlook thunderbird etc... Putting localhost is a workaround not a complete fix.. for example when phpmailer/web server is a ...


0

The culprit is Plesk. See: Does/etc/postfix/main.cf get overwitten at all How to configure the IP address for outgoing mail in Postfix Snippet from both page: The default settings in /etc/postfix/master.cf will be restored after mail reconfiguration on any domain. Consider creating a scheduled task to replace /etc/postfix/master.cf with a custom ...


1

FYI: The line --__INSERTSOMERANDOCHARHERE000MAILmynetwok isn't part of email headers. And maybe you don't wanna to alter/remove it. Anyway, here to do it. You should use both header_checks and body_checks to replace those line. Content of main.cf body_checks = pcre:/etc/postfix/mimereplace header_checks = pcre:/etc/postfix/mimereplace Content of ...


1

I'm sorry: mea culpa. Postfix ALSO still had an SPF policy in place, and since ASSP added a new address it failed. The policy has been removed and everything is working fine.


1

If you set up your secondary machine as a backup server, you'll need a few settings. relay_domains= myemployersdomain.com You will also be using your transport_maps like this: myemployersdomain.com relay:[the.actual.server] Then you would (as Falcon says) need the relay_recipient_maps with either a wildcard entry, or an entry for you, and your boss. ...


2

The whole point of the domain part of the email address is that it indicates which set of SMTP servers is responsible for delivery of mail for the whole domain. Put another way: you cannot subdivide domains like that. However, it sounds like what you really want to do (besides circumventing policy, but this is an interesting question theoretically so I'm ...


1

If you set up the servers like it was described in the ispconfig documentation then all the emails are in the folder /var/vmail/. You only have to backup this folder along with all subfolders. A restore can be done by doing a copy of the old mailbox folder content in there again. The structure is like this: /var/vmail/domain.com/before_at_sign


0

I think you'll want to use something like /MAILmynetworkloca_$/m REPLACE maildomaincom_ . The dollar sign means at the end of the string, the m should put it in multiline mode (according to the PCRE pages) Why you'd want to replace that header I don't know, but it's your mail server :)


2

One solution is increased monitoring e.g. raise alerts when the number of messages from individual ip-address/user account suddenly increases. That may be followed by rate limiting. The other is egress filtering on the SMTP servers you provide to your customers, similar to how you do spam filtering on incoming e-mail.


0

If you are able to send email from command line using: mail customerservice@site.co.uk subject: subject your text . you should be able to send emails from magento to. Check if apache user is able to send emails from /etc/postfix/generic Try to rewrite your web user (apache or nginx) for sending emails in /etc/postfix/generic, example: apache@hostname ...


0

The SMTP port rule in our group policy on AWS was missing.


0

I took a hint from this post Use different relay in postfix And used header_checks to assign the proper transport for emails that I had inserted an X-Foo header into: # cat /etc/postfix/main.cf ... header_checks = regexp:/etc/postfix/header_checks # cat /etc/postfix/header_checks ... /^X-Foo: 1/ FILTER relay:otherhost.com:25 relayhost was commented out ...


1

There's actually a pretty straightforward walkthrough for this. The nomenclature here is "SMTP namespace sharing" and Exchange Online (Office 365) can do this. Typically the idea is to "test out" Office 365, but it will still work long term as well if you so desire. The full walkthrough can be found here: Simple Domain Sharing for SMTP Email Addresses ...


0

The only way you can achieve that is to have a local account or alias a1@xyz.com and forward it to a second account a1@xyz-ext.com handled by Office365/GApps. This only works if you can set up these services to send mails as coming from xyz.com even if they only receive for xyz-ext.com, and I don't know if they offer this. All in all, this is a kind of ...


1

First, pardon me for misdirection here because I misunderstanding your intention in the past. Now, as far as I understand, your intention is aliasing 104.131.98.138 to lists.freedomlayer.org - so when you browse through either 104.131.98.138 and lists.freedomlayer.org you get same result - YES? Unfortunately, it isn't possible with mailman. Mailman expect ...


4

You should be configuring phpmailer to connect to localhost, not to the hostname of the machine (which will then use its external IP address to connect). Localhost is allowed to relay mail through postfix by mynetworks, but when you connect with the hostname it's via the public IP address, which is not allowed to relay.


1

Note: smtp != smtpd smtp act as smtp client used to sending email smtpd act as smtp server used to receiving email Parameter smtp_sasl_type with dovecot was unsupported. Maybe you mean smtpd_sasl_type = dovecot instead.


1

Looks like you have mismatch between where postfix stores the emails and where courier search the emails. Looking on your postfix configuration, it pretty clear that you let postfix store the email in default format and default places, /var/spool/mail/$user with mbox format. In courier, you use authpam as authentication module. So it's expected that ...


1

I changed main.cf to bind to 127.0.0.1 instead of localhost inet_interfaces = 127.0.0.1 Restarted postfix $ sudo launchctl stop org.postfix.master $ sudo launchctl start org.postfix.master


4

In order for mail to be delivered, postfix must be able to enter the user's home directory, and that directory must contain a complete Maildir tree containing the subfolders tmp, cur and new, all with the correct permissions. Since you've already checked that the Maildir exists, has the correct folders, and has the right permissions, what remains is ...


5

I have good and bad news for you regarding this question. The good news is Postfix indeed have mechanism to disconnect when client misbehaving. It documented on this page. Three parameters control the behavior: smtpd_soft_error_limit, smtpd_hard_error_limit, smtpd_error_sleep_time. This pseudocode will illustrate how it works. While smtpd get connection ...


3

Despite what I configure or do. I get always the same result with dig (like if the data comes from other place bit not my zone file): In your output I notice you have 2 dns servers. ;; AUTHORITY SECTION: mydomain.com. 63046 IN NS dns1.kontent.com. mydomain.com. 63046 IN NS dns2.kontent.com. Your domain server is ...


1

+1 for @tmpl7 has a great idea about how to implement your scenario with sqlite Now, the problem is you haven't implemented sql query for ifnull in virtual_alias_maps parameter. First define the virtual_alias_maps in main.cf virtual_alias_maps = mysql:/etc/postfix/redirect2spamlearning The content of /etc/postfix/redirect2spamlearning user = postfix ...


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 ...


1

add permit_sasl_authenticated to smtpd_client_restrictions – by Reinaldo Gil Oct 23 at 18:59


1

you can use luser_relay, in this way, you setup an email address for emails users that doesn't exist in your system http://www.postfix.org/ADDRESS_REWRITING_README.html#luser_relay


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 ...


0

My doubt is, does Postfix consider an email of such characteristics (300 recipients) as only one "delivery requests"? Yes. In fact, the default limit of recipient per delivery request is 1000. See postconf smtpd_recipient_limit and the man page If you want limit recipient, use smtpd_client_recipient_rate_limit. A little note from this page ...


3

TLDR: Your case is abnormal behavior mail client in proper SMTP transaction. Maybe something wrong in your PHP code. See this thread on postfix mailing list. A quote from Postfix author in that thread You are mistaken. You have no evidence whatsoever that Postfix rejects the entire message. It is known that SOME SMTP CLIENT programs will give up ...


2

Change smtpd_banner. Note that per protocol, $myhostname must be the first argument. smtpd_banner = $myhostname ESMTP random mail server bent over and ready.


2

You can change how long messages stay in the postfix queue before being dropped by setting maximal_queue_lifetime = Xd in /etc/postfix/main.cf You might want to check also minimal_backoff_time and maximal_backoff_time which are the minimum and maximal amount of time a message won't be looked at after a delivery failure. For other values that might ...


1

Try this, which is how my server is configured (if your domain is not "virtual", find the correspond options) : Keep existing options as they were on your initial question, I don't think they are the problem. Add this in main.cf : virtual_alias_maps = hash:/etc/postfix/virtual virtual_mailbox_domains = hash:/etc/postfix/virtual-mailbox-domains ...


0

That's not really the way mail servers work. They're designed to either send the mail through, or return the error/reason for failure to the end user if something does not work. Changing that behavior changes the way SMTP functions. As the Wiki page on NDRs says: NDRs are a basic SMTP function. As soon as an MTA has accepted a mail for forwarding or ...


1

Either you have bad RAM on your server (hopefully unlikely, but with DO, you never know...), or there is a bug in the version you are using, or it is corrupt, or your distribution has shipped binary-incompatible libraries. Consider updating everything with apt. If you have a reason to suspect it might be a hardware problem, bother DO's support.


4

The easiest manner to restrict people from outside sending to your server is to allow only SASL authenticated people to send, then define smtpd_sender_restrictions as reject_sender_login_mismatch, reject which will only allow SASL authenticated users, and only when their FROM address matches their login name. Creating an SQL query which selects the user's ...


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 ...


2

Postfix does not support directly this feature, but you can fiddle with transport maps in order to achieve your goal. You can add many transports in master.cf, each for every domain, with a -o directive that adds a remap rule In the transport file you set up the transport rule to use the transports specified in master.cf accordinf to the domain name This ...


2

These are mailed from a cronjob. They will be sent to root@yourhostname. To correct your hostname you gave to edit the /etc/mailname file with your correct hostname.


5

Some background Postfix inherited some features from older sendmail like milter and aliases. The file /etc/aliases is part of aliases inheritance and implemented by alias_maps. On the other side, postfix has virtual_maps/virtual_alias_maps for handle email aliasing. So what's the difference between them? Parameter alias_maps Used only for local(8) ...


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 ...


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. ...


1

/etc/aliases is there primarily for local delivery, for example, mail to root from cron, etc, it's nice to keep your local aliases separate, virtual_alias_maps can also be used with SQL DBs, and so on. virtual_alias_maps is for when you have virtual users (and virtual domains), often that do not map to system users, but if you don't have virtual domains, ...


2

As expected, the problematic line comes from master.cf. Here your culprit bounce unix - - n - 0 discard And this is the default master.cf content bounce unix - - n - 0 bounce This change has caused the bounce of failed delivery will be silently discarded. The solution: Replace that ...


2

... if an account is compromised (a virus uses stolen credentials -from Outlook configuration files, for example- to send SPAM), and authenticated clients can send email without further restriction, your last opportunity is your milters correctly reject SPAM messages from compromised accounts; but, isn't it less efficient? I think postfix is more ...


5

Based on our discussion in the comments I can think of another way to approach the problem. This used to happen to me all the time in the hosting business- you have to let anybody with basically any client connect to your smtp server, and if their workstation is compromised, they can do what they want. Again, my approach was defense in depth, with a little ...


1

I agree that using outbound spam filtering as a front line defense against sending spam is inefficient, but it is still important. The alternative is that spam gets through and lands you on a blacklist, then your whole domain is in trouble. So, I think a defense in depth approach is really the only approach here, including frequent password rotations, 2FA, ...


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 ...


0

This will work, but you may have to set parameter append_at_myorigin=no in main.cf in case myorigin is set. Otherwise if you are sending locally to "root" postfix by default will append myorigin value to the domain part of the recipient.


3

You misspelled parameter non_smtpd_milters. Your config says non_smptd_milters not non_smtpd_milters. How I spot it: Googling for keyword non_smptd_milters would yield 5 results, but for keyword non_smtpd_milters would yield thousands result.


1

The mailed-by header is the usually used to persist the content of the envelope from or MAIL FROM through forwarding. Amazon do not allow the MAIL FROM to be customised. The following quote is from an Amazon employee in a comment on an blog post about SPF & DKIM: The headers you mentioned [mailed-by] seem to be something appended by an ISP after the ...



Top 50 recent answers are included