-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange emails in postfix logs #1
Comments
So which ones are strange? First and fourth row are just info. Warning means you have that setting defined twice. You should check what Postfix does if it is defined twice: ignore the first one, or second one? Probably you can comment one of those out so that you get rid of the warning. When alias changes, it reloads, that is OK. |
The large number of messages going from the non-existent account
[email protected] to .pl and .ru MX servers is the strange part. Other
lines are immediate context of a representative example. Thanks for the
context for the warnings.
…On Thu, Oct 24, 2019 at 10:25 AM Mitar ***@***.***> wrote:
So which ones are strange? First and fourth row are just info.
Warning means you have that setting defined twice. You should check what
Postfix does if it is defined twice: ignore the first one, or second one?
Probably you can comment one of those out so that you get rid of the
warning.
When alias changes, it reloads, that is OK.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=ABRQFJ6DSZM7PGNDKNHYZBDQQHLB5A5CNFSM4JD3UFEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECFZU2Y#issuecomment-546019947>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRQFJZHSRSWBTZK4C23CITQQHLB5ANCNFSM4JD3UFEA>
.
--
Network support request form: https://goo.gl/forms/avS3v6VQWt4zVjtk1
This semester's Cloyne Facebook group:
https://www.facebook.com/groups/cloyne.2019fa
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: