#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #email #microsoft-outlook #microsoft-outlook-2013 #contacts Outlook 2013: add contact from mail but all fields remain empty

Bounty: 50

I’ve got a Windows 10 machine with Office 2013. When I open an e-mail, click one of the contacts in an address field and choose ‘add to contacts’ this opens the new contact card but leaves all fields empty.

If I do the same on a Windows 7 machine with Office 2013 all fields are populated in advance.


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!

#StackBounty: #email #pgp #enigmail #thunderbird How to workaround Thunderbird 78's lack of support for encrypted mailing lists?

Bounty: 50

As of Thunderbird 78, the support for PGP plugins such as Enigmail has been dropped in favour of a native implementation of pgp in Thunderbird’s core. But some features of Enigmail are still missing. One of those features is to create something akin to Enigmail’s per-recipent rules.[1]

This makes it impossible for people to use encrypted mailing lists, where subscribers encrypt messages with everybody else’s public key.

Although people seem to be working on creating a patch for this, it seems unclear when this will be available in mainline given that it is being worked on for over 4 months. Hence, people with an up-to-date Thunderbird will not be able to write to the list, and I read on the Thunderbird blog that the old Thunderbird 68 will not receive further security updates.

So, I’m trying to come up with a workaround.

One idea I have is to create a new key-pair specifically for the mailing list’s address and distribute both private and public keys to all subscribers of the list. Assuming that there are no removals from the mailing list in the near future, are there any security problems with this scheme? Intuitively it seems wrong to give several people access to a private key but I cannot think of a new attack that would be possible compared to the old scheme.

Or is there a better workaround?


[1]: This allows the subscribers of a mailing list to create a rule for the address of the mailing list and instruct Enigmail to encrypt any mail for a specific list of people on the list. It requires all users to maintain a copy of the subscriber list, adding and removing keys if the (managed) subscribers of the list proper change but it works reasonably well for small lists that don’t change too often.


Get this bounty!!!

#StackBounty: #email #pgp #enigmail #thunderbird How to workaround Thunderbird 78's lack of support for encrypted mailing lists?

Bounty: 50

As of Thunderbird 78, the support for PGP plugins such as Enigmail has been dropped in favour of a native implementation of pgp in Thunderbird’s core. But some features of Enigmail are still missing. One of those features is to create something akin to Enigmail’s per-recipent rules.[1]

This makes it impossible for people to use encrypted mailing lists, where subscribers encrypt messages with everybody else’s public key.

Although people seem to be working on creating a patch for this, it seems unclear when this will be available in mainline given that it is being worked on for over 4 months. Hence, people with an up-to-date Thunderbird will not be able to write to the list, and I read on the Thunderbird blog that the old Thunderbird 68 will not receive further security updates.

So, I’m trying to come up with a workaround.

One idea I have is to create a new key-pair specifically for the mailing list’s address and distribute both private and public keys to all subscribers of the list. Assuming that there are no removals from the mailing list in the near future, are there any security problems with this scheme? Intuitively it seems wrong to give several people access to a private key but I cannot think of a new attack that would be possible compared to the old scheme.

Or is there a better workaround?


[1]: This allows the subscribers of a mailing list to create a rule for the address of the mailing list and instruct Enigmail to encrypt any mail for a specific list of people on the list. It requires all users to maintain a copy of the subscriber list, adding and removing keys if the (managed) subscribers of the list proper change but it works reasonably well for small lists that don’t change too often.


Get this bounty!!!

#StackBounty: #debian #email #postfix #dovecot FInding 'server log' referred to in this postfix error

Bounty: 50

This is a bit embarassing, but I’m stuck at the first step of debugging a postfix+dovecot setup on Debian after following this guide.

Sending email from my server works, but receiving doesn’t. I get this line in the /var/log/mail.log (with some redactions):

# /var/log/mail.log
Oct 18 19:17:03 X postfix/lmtp[387]: BB7321F440: to=<A@X.Y>, relay=X.Y[private/dovecot-lmtp], delay=1157, delays=1095/0.02/0.01/62, dsn=4.3.0, status=deferred (host X.Y[private/dovecot-lmtp] said: 451 4.3.0 <A@X.Y> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command))

For convenience and emphasis, the key part is:

Internal error occurred. Refer to server log for more information.

The exact same error message appears in /var/log/syslog but there is no additional information there.

Where can I find the "server log" this refers to, so I can continue debugging?


Get this bounty!!!